"Exit Game" hangs

[benb]

Whenever I do "Exit Game" (e.g. in main menu), the game freezes - it does not react anymore, but not not close either. The window (if in windowed mode) is still there, and clicking the X of the window has no effect. Not even a kill <pid> or killall widelands helps, I have to kill -9, which works.

Similarly, when in fullscreen mode, the game does not resume the screen, it stays the in old resolution. Even when I killed the game. (I have no xrandr, so I can't easily switch back). Also, the screen seemed frozen, and the mouse pointer was gone, i.e. no mouse. I had to kill X11, which costs quite some time to reopen all SSH connections, apps, files etc.. I'll file another bug about that Widelands should not change the physical screen resolution, but as long as it does, the freeze at Exit in fullscreen garbles my machine.

[benb (benb-users-sf)]

Build: Widelands b13 (from Nov 2008 IIRC) package from SuSE 10.3 packman.

[benb (benb-users-sf)]

Filed bug 2793082 about not changing physical screen resolution.

[dwarik (dwarik)]

i talked to benb on irc. he has a dual screen with nvidia proprietary drivers.

[Timowi (timo-wingender)]

@benbucksch:
please provide some more information
which version(s) exactly
which system,
add the last lines from console output
and if possible run in a debugger and post a backtrace
Thanks

[Ben Bucksch (benbucksch)]

Timo, please do not just close bugs without comment and reason, thank you. This is a serious bug.

> which version(s) exactly
> which system,

Stated above.

> add the last lines from console output
> and if possible run in a debugger and post a backtrace

I'm not running Widelands at the moment.
I only report the bug. That doesn't mean I'm obliged to help debugging it.

[Ben Bucksch (benbucksch)]

FYI, running a debugger is definitely the developer's job, not the user's.
And IIRC there was no console output, because I started it from the start menu. It was just hanging. I explained the behavior in quite detail in the initial description.

[Timowi (timo-wingender)]

I am not able to reproduce any graphics related crash and this bugreport concerns a quit old release. So someone who can reproduce this bug (with a recent release) have to provide more information.

I didn't close this bug. I set it incomplete. And I would still set it to incomplete because is does not contain enough information to work on it.

[Ben Bucksch (benbucksch)]

It has a reproduction. That's enough. If you can't reproduce it (e.g. due to other graphics setup), you can't fix it anyways - with or without more information.

[SirVer (sirver)]

I support Timos action. Build13 is old. Without backtrace this won't be easily found or solved. It is absolutely reasonable to set this bug to incomplete for as long as not enough information is available to start fixing it.

That said: widelands is project driven by people who contribute their free time to work on it. Technically it is not their job either to provide a debug backtrace or satisfy "customers". You want this bug fixed Ben, you will need to offer support. If you choose not to do so this bug will expire someday because it is set to incomplete.

I set this back to incomplete. Please provide more information about how to reproduce this with at least build14 or even better an actual branch build.

[Ben Bucksch (benbucksch)]

SirVer, I understand that this is a community project. If you can't or don't want to work on it, then leave it for somebody else.

This bug forced me to killed my desktop, which is close to crashing the machine. It's important to be known and recorded.

A bug is complete when it has a reproduction. This one has.
"Complete" does not mean that the user ran a debugger. That's ridiculous to demand.

For clarity, here again the reproduction:

Setup:
- nvidia graphics card
- 2 monitors, configured as Xinerama (no TwinView, no xrandr)
- nvidia binary driver
- SuSE 10.3
- Widelands b13 package for SuSE from packman (biggest package source for SuSE)

Reproduction:
- Start widelands, either in windowed or fullscreen mode
- Exit game

Actual result:
As described in initial description.

You may understand that I have a job and can't trash my machine by starting games which tend to do that. And that *after every release*, just to test whether they still trash machines, just in case this happens to have been fixed. If I have a chance and easy to install build, I'll test it again, but at the moment, I can't spare my machine, sorry.

[Raul Ferriz (raul.ferriz)]

Ben, just a note, latest official release was build 14.

So build 13 is not supported anymore.
We now will want to release a new version, so please test this bug on latest official release or even better, on bzr trunk version to test if the bug is also on current repo.

Thanks

[Timowi (timo-wingender)]

I currently use the nvidia binary driver with a ubuntu system. Can't reproduce the bug with build14 and newer.

Last year I used build14 at a debian and a ubuntu system with nvidia binary driver and 2 monitor. I did not had any problem with that too.

So the problem is very specific too your setup. That you can reproduce it does not mean it is useful in any sense for a bug report. This bug is complete if the problem is reproduceable on an other system.

[SirVer (sirver)]

Ben, thanks for your persistence. But please also accept that we can't do anything to fix this bug because we can't reproduce it. It can sit around here forever or it can expire. our choice for it is to do the later.

You are right, Widelands is community driven. But this is our community. 3 developers think this bug is incomplete. Please accept that.

[Samith Sandanayake (samithdisal)]

i experienced this bug when i stayed for a long time in the game, i noted that it happens only if i let the screen to go black for inactivity.

[SirVer (sirver)]

Samith, could you state the widelands version, your system and a precise way to reproduce the bug?

[Samith Sandanayake (samithdisal)]

I experienced it on build14,
Graphic Driver is fglrx

how to reproduce:
when the game is played for about an hour and if you were away from
keyboard and let the screen to turn off(as I remember this happened all
the time), the game is unable to close from the menu.

as I played it in full-screen the only way to come out it to goto
another tty and reboot.

but i found that without going to the main menu while the game is
running i can press f and goto the window mode then close the terminal
window i used to open the will not effect to the X. (disabled the input
grab).

and another thing. before installing the graphic driver there were no
such problems, only the sound is not there. :)

[Nicolai Hähnle (nha)]

Jeez, Ben, lighten up. Your sense of entitlement is astounding.

Anyway, I managed to reproduced the bug, and, as expected, it has nothing at all to do with the graphics driver, but is audio related. The hang is in SDL_AudioQuit, to be precise, while apparently the audio thread is stuck in an infinite loop. Perhaps we're using some of the SDL audio libraries incorrectly. Is there anybody here who is familiar with that code?

[Nicolai Hähnle (nha)]

As another point of reference for the library versions involved, I'm using Ubuntu 9.10.

[Timowi (timo-wingender)]

I have mentioned the sound problem some times. I'm sure who is doing it wrong. But it seems not to be widelands. This happes for me too under ubuntu 9.10. The problem is the sound server 'pulseaudio' under ubuntu. Sometimes it crashes and have some nasty effects. One of it is the thing with SDL_mixer. Sometimes most movieplayers get problems with jumping forward/backward. And Volume control behaves differently.
The only thing which helps form is restarting the pulseaudio process. Sometimes I have even to force a unload/load of my alsa module (hd_intel) and kill all aplication which use sound to get pulseaudio completely working again.

I always consider Ubuntu highly unstable.

[SirVer (sirver)]

Pulseaudio is also tracked in launchpad. We can someone inform them of this bug and send it over to them. I have no idea how this is done, though ;).

[Ben Bucksch (benbucksch)]

(I had not suspected audio, nor had anybody on IRC when I asked about the bug, see comment 3.)

Yes, I also use PulseAudio, with .asoundrc having pcm.!default { type pulse} (same for ctl).

I saw the bug immediately, without having to wait, IIRC. However, I IIRC also had sound in menu turned off.

[SirVer (sirver)]

can someone try this with the --nosound option? This should not bother the sound daemon at all (in latest trunk).

[Jari Hautio (jarih)]

As this is sound related, I just filed a bug and patch for a bug related to callbacks from SDL_mixer. There was a threading related issue, which could potentially crash callback thread in SDL_mixer. See bug 542163.

[SirVer (sirver)]

Jari, are you positive this is related to bug 542163? If so, we can mark this one as duplicate. Or do you need someone verify this?

[Jari Hautio (jarih)]

It's a guess, so I need someone to verify it.

Basically threading bug should be much more upredictable, than what's been in the comments. I could not reproduce the bug (without the patch) in my ubuntu 9.04 virtual machine, so I cannot test it myself.

[Victor Pelt (victor-pelt)]

for those that have this bug
do you have libsdl1.2debian-pulseaudio installed?

do you have this error if you run
SDL_AUDIODRIVER=pulse ./widelands

if either one of this fixes it i got a fix for this problem

[Victor Pelt (victor-pelt)]

mark as an ubuntu problem for now. please reopen this if you have this problem with a non-ubuntu system
(and test both the use of SDL_AUDIODRIVER=pulse and SDL_AUDIODRIVER=alsa)

[Almufadado (almufadado)]

This just happened to me too !

Ubuntu 10.04 Maverick (with latest updates)
gnome
nvidia version current 195.36.24
dual screen with twinview
widelands release 14

Screensaver with password is on

Played the game in full screen mode
After a hour or so quit the in-game normally
In the main menu after clicking in the exit button the both the screen and the mouse just froze.

Accessed the TTY
Did a killall -I -i widelands
asks to kill widelands(1983) but to no effect
had to reboot

Dmesg doesn't say much exit by the time it happen I have this message in the "user log" :

bonobo-activation-server (<myuser>): could not associate with desktop session: Failed to connect to socket /tmp/dbus-Hjt9M27ht5: connection refused

at the same time in syslog
gnome-session[1983]: WARNING: Detected that screensaver has left the bus

As a WILD guess, can this be caused by the secure screensaver doesn't restart or widelands fails to give way to it?

[SirVer (sirver)]

As said before, this is a known bug in pulse audio. We can't do anything about this. Use SDL_AUDIODRIVER=alsa and you should be fine.