Follow-up Comment #4, bug #12683 (project wesnoth):
I just attached the stderr.txt (stdout.txt is generally blank, and deleted
when the program is closed). Forgot about logging in.
The game froze on autosave.
The user must have permission to modify or create the autosave
(AToTB-Guarded_Castle-Auto-Save12.gz in this case).
On my computer, the creator of a file owns it by default, and otherwise only
admins can write to them. When one user plays the campaign and leaves a few
autosaves behind, another user plays it and no problem occurs until you catch
up with the earliest remaining autosave.
I have been able to repeat and remedy the problem at will, setting
permissions on the file in question, and have no doubt that this is the sole
reason for the game to hang at that point.
My solution: Add permissions for the local user group to modify files and
subfolders of the USERDATA folder. (This option is available to me because I
run Win XP Pro with full share & NTFS-administration, which is not
necessarily the case for all Windows-users).
Other solutions:
Verify access before save / time-out save and move on
Implement optional or standard userdata-location for Windows users
("%appdata%\Wesnoth" should do for root folder, although you might have to
resolve the environment variable %appdata% before applying it)
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?12683>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
