You are not logged in.
Pages: 1
It seems to happen when I try and scroll. Sometimes I can play a couple turns, but most of the time the first or second time I try to do something it freezes and I need to go to a console to kill it.
Anyone else having this problem?
Offline
launch it from a terminal and check if it gives any specific errors
Offline
ALSA lib pcm.c:7236:(snd_pcm_recover) underrun occured
I'll get that error two or three times each session. Sorry, I forgot to put that in my original post.
It also seems to still be "working" but not displaying anything, as if it dies in the middle of an enemy turn it finishes it out, gives me the bell, etc, and I can click on the menu but not see anything happen.
Offline
Has this been occurring since the recent Boost/Wesnoth update two days ago or even before that? Have you tried the new versions? Have you tried building from AUR?
Offline
Has this been occurring since the recent Boost/Wesnoth update two days ago or even before that? Have you tried the new versions? Have you tried building from AUR?
I'm pretty sure that this has been going on for at least three versions (counting this one, 1.6.5-4). I did build it from the AUR, but it's still just as bad.
The last update, from 1.6.5-3 to -4 has seemed to make it at least technically playable, as I can get in a full round or two before it crashes.
Here's the full terminal output:
me@arch:~$ wesnoth
Battle for Wesnoth v1.6.5
Started on Sat Mar 6 15:47:11 2010
Data directory: /usr/share/wesnoth
User configuration directory: /home/me/.wesnoth1.6
Checking video mode: 1280x800x32...
setting mode to 1280x800x32
20100306 15:47:13 error general: no location found for 'data/campaigns/Flight_Freedom_1_5/translations', not adding textdomain
20100306 15:47:13 error general: no location found for 'data/campaigns/Sceptre_Of_Life/translations', not adding textdomainLast edited by JohnnyRogers (2010-03-06 20:55:14)
Offline
Installing wesnoth-devel from the AUR has fixed the problem, and I actually managed to play through a few levels today. ![]()
Not sure if I should mark this as solved, since the original problem with 1.6.5 still persists, even after today's update. ![]()
Offline
Pages: 1