Description of problem: as in summary Version-Release number of selected component (if applicable): How reproducible: load and start game. play , then quit Steps to Reproduce: 1. 2. 3.
Can you explain a bit more ? Personally I have not understand the problem
Keywords: (none) => NEEDINFOSource RPM: 0 AD => 0ad
I interpret the report as saying the game killed the x server. When I tried it, the game segfaulted shortly after starting single player mode. When I tried to run it under gdb, it locked up my x server, and I had to use ctrl+alt+bs twice, to kill it. On my old i586 system, the game is painfully slow, and the fonts don't display properly, similar to the problem I had in bug 2056. Rob, If I'm correct, can you attach /var/log/Xorg.0.log.old
CC: (none) => davidwhodgins
Created attachment 750 [details] as requested Xorg.0.log.old
Sorry for poor info - bit new and not sure what was needed. Dave thanks for the decipher . as not noob and not sure of the correct terms I write as I see it. have been able to install fine from repos. when starting game ,get screen flicker,which is quite bad. to correct this I have to go into the monitor manager and set refresh to auto instead of the default 60hz. I can then start the game without flicker. game play is fine,redering at start can be slow but once up and going all is well. not the worlds fast game player so haven't had any other problems other than the lack of save function - this is a Oad problem. on exit the game will either , close nice and return me to the desktop or as more often the problem through be back to the log in screen. this happens almost instantly as though it was waiting to ponce.( tigger style)
Attachment 750 mime type: application/octet-stream => text/plain
(assigned to the maintainer)
Assignee: bugsquad => supp
Pinging. because nothing happened to this report since 3 months ago, and it still has the status NEW or REOPENED. @ Thomas Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
Keywords: NEEDINFO => (none)CC: (none) => marja11
3-monthly ping
I'm facing this problem since I moved to Mageia 2, with several other applications such as fgrun (flightgear launcher0 and calibre. Also with closed-source applications like skype 4.0 dynamic (only when I open the configuration window) and skype 2.0.35 as soon as i launched it (I deleted it since version 4 was released). I use the NVIDIA driver: $ rpm -qa | grep nvidia nvidia-current-doc-html-295.49-2.mga2.nonfree nvidia-current-kernel-3.3.6-server-2.mga2-295.49-4.mga2.nonfree dkms-nvidia-current-295.49-2.mga2.nonfree x11-driver-video-nvidia-current-295.49-2.mga2.nonfree nvidia-current-kernel-server-latest-295.49-4.mga2.nonfree $ lsmod | grep nvidia nvidia 10971512 30 i2c_core 29836 4 nvidia,i2c_dev,i2c_i801,videodev I have a similar Xorg log which I attach.
CC: (none) => listas.apl
Created attachment 2490 [details] Crash for fgrun This is the log when I launch fgrun and get the "X I/O error" message.
Version: 1 => 2Whiteboard: (none) => MGA1TOO
Resetting assignee to bugsquad as I no longer maintain this package...
Assignee: supp => bugsquad
I see nothing similar between the 2 X.log beside "[ 15866.333] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]" but I don't understand that The reporter use intel, comment 8 nvidia, so..
Source RPM: 0ad => (none)
CC: (none) => stormiSource RPM: (none) => 0ad
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD