Post by Iris » April 11th, 2015, 6:20 pm

Wesnoth 1.12.2 is out!

we urge users of all previous versions to upgrade immediately

Security vulnerability fix (CVE-2015-0844) » A severe bug was found in the game client that could allow a malicious user to obtain personal files and information from players in networked MP games through the WML/Lua API (bug #23440). This issue affects all platforms.



Users of all existing Wesnoth releases are urged to upgrade immediately.



CVE-2015-0844 has been assigned to this vulnerability and may provide further information.

Multiplayer campaign gold carryover fix »



This bug was client-side, and old clients (1.12.0, 1.12.1) cannot be fixed! All clients in a multiplayer campaign must have version 1.12.2 or later, or OOS errors will occur.



If you are producing an MP campaign, you can help mitigate the problem by warning users against playing older versions with it, using WML code like the following in your scenario:

Code: Select all #ifver WESNOTH_VERSION < 1.12.2 [message] speaker=narrator message= _ "You have an outdated Wesnoth version which is affected by a gold carryover bug — you will get OOS errors when the campaign transitions between scenarios, and you will have to save and reload each time to proceed. Please consider upgrading Wesnoth to version 1.12.2 or later." [/message] #endif Bug #22936 [Gna.org] has now been fixed, meaning that clients should get the correct gold carryover when they play multiplayer campaigns together.All clients in a multiplayer campaign must have version 1.12.2 or later, orerrors will occur.If you are producing an MP campaign, you can help mitigate the problem by warning users against playing older versions with it, using WML code like the following in your scenario:Refer to PreprocessorRef on the wiki for further information on using the #ifver directive.

Multiplayer event synchronization fix » time over events were previously not synchronized (bug

Using [set_variable] rand=

Creating units ( [unit] , [unstore_unit] , wesnoth.put_unit , etc.)

, , , etc.) Displaying a [message] requiring user input ( [option] , [text_input] )

requiring user input ( , ) Using [get_global_variable]

Calling wesnoth.synchronize_choice WMLevents were previously not synchronized (bug #23331 [Gna.org] ). This means if you do any of the following things in such an event handler in a game with at least one client with a version earlier than 1.12.2, you will get OOS errors:

Miscellaneous fixes and improvements » The campaigns A Tale of Two Brothers, Delfador’s Memoirs, The Hammer of Thursagan, Northern Rebirth, and the epilogue of Legend of Wesmere now make use of the new story maps introduced in 1.11.x.

Enemy reinforcements are now summoned as intended in Under the Burning Suns scenario 5 “A Subterranean Struggle”.

Undoing player actions after deactivating Delayed Shroud Updates should no longer generate OOS errors.

Clicking during the execution of [delay] actions in prestart no longer results in a segmentation fault (bug #23243 [Gna.org]).

actions in prestart no longer results in a segmentation fault (bug #23243 [Gna.org]). The Terrain Description context menu option can no longer be used to reveal shrouded terrain (bug #23426 [Gna.org]).

Sliders in certain parts of the game interface (using the GUI1 framework) now process input focus correctly, allowing to adjust them using arrow keys (#22984 [Gna.org]).

Several issues with specific Micro AI engines have been fixed. See this post for details.

Known bugs » General bugs:

HP/XP bars of allied units are drawn over shroud with some side configurations (bug #23460 [Gna.org]).

Wesnoth may occasionally crash to desktop when/while music is enabled. Thus far, this has been observed on Windows XP SP3 (bugs #23203 [Gna.org] and #23026 [Gna.org]) and Debian GNU/Linux 8 “jessie” (report pending).

More information is needed to help us determine the cause of this issue — in particular, your Wesnoth build configuration (if compiling from source), and OS and library versions, as well as any customizations you may have made to your install. Backtraces and semi-reliable steps to reproduce are highly desirable due to the nature of this bug.

— in particular, your Wesnoth build configuration (if compiling from source), and OS and library versions, as well as any customizations you may have made to your install. Backtraces and semi-reliable steps to reproduce are highly desirable due to the nature of this bug. It’s not possible to clear some default hotkeys with the Clear Hotkey option (bug #21983 [Gna.org]). This will not be fixed in 1.12.x.

Attempting to assign hotkeys including both the Ctrl and Alt modifiers does not work (bug #22219 [Gna.org]). Bugs specific to Microsoft Windows:

ClearType font rendering is disabled as it causes glitches (bug #21648 [Gna.org]).

This is likely caused by outdated libraries in the packaging process.

This is likely caused by outdated libraries in the packaging process. Consecutive line breaks (paragraph breaks) are not rendered as expected (bug #21649 [Gna.org]).

This is likely caused by outdated libraries in the packaging process. There is no built-in workaround available yet. Bugs specific to Apple OS X:



The following issues affecting Wesnoth on Apple OS X are known and they are pending fixes. However, many of them are beyond the scope of the 1.12.x series and require significant re-engineering that can only be done in 1.13.x development releases later, or cannot be properly addressed due to a lack of experienced OS X coders in our team. Thus, unless someone can contribute patches to address them, it is unlikely that these bugs will be fixed during the 1.12.x series.

Color cursors are forcibly disabled on this platform due to severe performance issues (bug #18112 [Gna.org]).

Fullscreen mode does not fill the entire screen when maximum resolution is selected in Preferences → Display, and user interface elements are scaled and distorted.

System commands do not work while Wesnoth is running in fullscreen mode (bug #21943 [Gna.org]).

The mouse cursor is not mapped correctly to the game screen contents on Retina displays due to problems with detected vs. real screen resolution mismatches (bug #20332 [Gna.org]).

A workaround is in place making Wesnoth default to 800x600 on OS X regardless of the incorrectly-detected maximum resolution.

A workaround is in place making Wesnoth default to 800x600 on OS X regardless of the incorrectly-detected maximum resolution. Trackpad tap clicking is sometimes not recognized (forum post).

Unofficial builds with OpenMP support enabled randomly freeze (bug #18144 [Gna.org]).

Consecutive line breaks (paragraph breaks) are not rendered as expected (bug #21649 [Gna.org]).

This is likely caused by outdated libraries in the packaging process. There is no built-in workaround available yet. The following issues affecting Wesnoth on Apple OS X are known and they are pending fixes. However, many of them are beyond the scope of the 1.12.x series and require significant re-engineering that can only be done in 1.13.x development releases later, or cannot be properly addressed due to a lack of experienced OS X coders in our team. Thus, unless someone can contribute patches to address them, it is unlikely that these bugs will be fixed during the 1.12.x series.

Contributors

irc.freenode.net

Downloads

⁂

This is a maintenance release for the stable 1.12.x series, and it is fully compatible with version 1.12.0. This version includes a critical security fix, as well as an assortment of other bug fixes, minor improvements in various areas, and translation updates.Because this release solves a known security vulnerability affecting the game client,Read on for more details about the most notable fixes in this release, as well as a few known bugs we hope will be fixed in future releases. Players coming from 1.10.x or previous stable versions should check our official release notes for Wesnoth 1.12 to learn about the new features and general improvements from this series.There are a few more changes in addition to the aforementioned, including translation updates and minor bug fixes. Most of these items are listed in the full changelog for enthusiasts and content creators. An alternative players changelog is also available, including only items deemed relevant for regular players.Do you want to help shape the future of Wesnoth? You are always free to join us in the IRC channel onto ask for help with getting started!Packages for, andare already available:All knownpackagers have been contacted, and binaries for your distribution may have already been created. Information about where to get the respective binaries or how to install them can be found on the Linux binaries page in the wiki.Downloads formay be found on the Download page in the wiki as they become available.The multiplayer server for 1.12.x is up and running. This server can be used to play with other players running1.12.x version, as well as release candidates.The add-ons server for 1.12.x is already running. It was started for 1.11.10 and it servesstable, RC, and beta releases from this series.If you find any bugs, do not hesitate to report them, but please read the instructions on how to report bugs first! As bug reports in the forums tend to be forgotten, you will get better results using our bug tracker . We require your help for finding and fixing issues, no matter how obvious, trivial or complicated they seem!Have fun!