FS#26489 - Running community/warzone2100-2.3.8-1 kill gnome session

Attached to Project: Arch Linux
Opened by Alessandro (MaybeDrunk) - Monday, 17 October 2011, 17:14 GMT
Last edited by Allan McRae (Allan) - Saturday, 28 April 2012, 11:14 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
after start warzone2100 gnome is killed (and logout) and return me to gdm screen:

$ warzone2100
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 38 requests (38 known processed) with 0 events remaining.

Additional info:
community/warzone2100-2.3.8-1
extra/intel-dri 7.11-2
extra/xf86-video-intel 2.16.0-1
core/linux 3.0.6-2
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 28 April 2012, 11:14 GMT
Reason for closing:  Fixed
Additional comments about closing:  Submitter reports as fixed (somehow...)
Comment by Jan de Groot (JGC) - Thursday, 20 October 2011, 10:44 GMT
Please provide logs, this isn't helpful.
Comment by Alessandro (MaybeDrunk) - Sunday, 30 October 2011, 17:48 GMT
Xorg.0.log have no errors on it (EE).
.xsession-errors have a lot of errors, but all related with gnome, no one is related to warzone || X crash.
The only related log i found is the one i paste, that is the output of $ warzone2100 >log 2>&1 and it's also in /var/log/errors

Please, tell me where can i find a more specific log file. Thanks
Comment by Laurent Carlier (lordheavy) - Sunday, 30 October 2011, 18:52 GMT
Running dmesg or in file /var/log/kernel.log
Comment by Alessandro (MaybeDrunk) - Sunday, 30 October 2011, 19:49 GMT
no error reported by dmesg (and also no messages after loading of gdm)
Comment by Alessandro (MaybeDrunk) - Friday, 11 November 2011, 16:38 GMT
diff between files after and before crash. Files are named with incremental number, for example dmesg.log1 (before crash) and dmesg.log2 (after crash). I hope this help (i still don't see specific error in log, so i paste everything)
   erlog (96.3 KiB)
Comment by Alessandro (MaybeDrunk) - Friday, 11 November 2011, 16:47 GMT
this problem occurr also with warzone2100-2.3.9-1 but only when running gnome. In fact, if i stop gdm and start x-base session with startx, and then run warzone, everything works well
Comment by Anthony (netman74501) - Friday, 11 November 2011, 18:40 GMT
I would like to add that I am also experiencing this on Ubuntu 11.10 with Gnome 3. I realize I am on a different system but, wanted to offer a workaround as this is the first and only thing on Google about this problem.

The logout appears to happen only in fullscreen mode (for me). If you run the game from a terminal with "warzone2100 --window" it will run in window mode. The game remembers the window mode so you don't have to run it from the terminal after you have ran it once this way.

I could not figure out how to use the debug switch (tells me the file I specify doesn't exist even if it does) but, there is one. If anyone knows how to use it, that might be more helpful.
Comment by Alessandro (MaybeDrunk) - Saturday, 12 November 2011, 17:49 GMT
uh yeah! This trick works well. I think this may be a problem related to the intel low power graphics card (i have this problem on a netbook) because i have another (more powerfull) archlinux pc where this problem does not exist.
Comment by Anthony (netman74501) - Saturday, 12 November 2011, 18:07 GMT
Good! I'm glad it worked. However, based on what you previously stated, I believe this to be something between the game itself and Gnome. Not hardware related.
Comment by Alessandro (MaybeDrunk) - Friday, 18 November 2011, 20:10 GMT
Don't know, with another pc (same configuration but more powerful hardware: GeForce 9600 GT && AMD X4) it works very well, without any problems. I already tried to reset user configuration and reinstall warzone too, but nothing change.
Comment by Jelle van der Waa (jelly) - Monday, 30 January 2012, 13:22 GMT
So this issue is resolved?
Comment by Alessandro (MaybeDrunk) - Wednesday, 01 February 2012, 16:54 GMT
yes, still happen, these are related logs (if you think it can help)
Comment by Matthias Dienstbier (fs4000) - Wednesday, 11 April 2012, 11:20 GMT
Just tried to reproduce this but warzone2100 was killed by SIGSEGV. If it still crashes your X the logs should be in Xorg.0.log.old as X restarts instantly and moves the old log away.
Comment by Alessandro (MaybeDrunk) - Monday, 16 April 2012, 15:03 GMT
as always i don't know what's going on, but this problem seems to be solved (don't know what update fixed it)

Loading...