Description of problem: On a Lenovo T520 with the integrated Intel SandyBridge GPU, when the OpenGL screen savers are used they crash the x session when they are deactivated returning to the desktop. This behavior applies to KDE's native screen saver as well as Xscreensaver. It also occurs while testing the screen saver. Version-Release number of selected component (if applicable): Mageia Live 1 How reproducible: Steps to Reproduce: 1. Select OpenGL screen saver in either KDE module or Xscreensaver. 2. Test screen saver, or allow it to activate normally. 3. Attempt to return to desktop with mouse or button event. Session crashes and user is returned to the login screen.
For reference, this was originally reported here: https://forums.mageia.org/en/viewtopic.php?f=7&t=1347 Here is also a log showing a crash, but currently without relevant -debug packages. https://forums.mageia.org/en/download/file.php?id=124
CC: (none) => doktor5000, thierry.vignaud
@ Michael * If you managed to get the backtrace, please attach it to this bug report. Upstream the following is interesting: http://www.jwz.org/xscreensaver/faq.html#server-crash In spite of what is said in the link above, please also do what is suggested here: http://www.jwz.org/xscreensaver/bugs.html and give the following commands (in a konsole): xscreensaver-command -exit xscreensaver -verbose -log log.txt * and then, after the crash was reproduced, attach the log.txt to this report (too). * Also, please give the version of xscreensaver en x11-server you use
Keywords: (none) => NEEDINFOCC: (none) => marja11Source RPM: (none) => xscreensaver, x11-server
@ Michael Please reply to the question above within two weeks from now, to avoid this bug being closed as OLD.
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD