Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#20987 - [gnome-screensaver] black screen after resume from suspend
Attached to Project:
Arch Linux
Opened by Mateusz (niqmat) - Wednesday, 29 September 2010, 10:29 GMT
Last edited by Ionut Biru (wonder) - Saturday, 19 February 2011, 19:30 GMT
Opened by Mateusz (niqmat) - Wednesday, 29 September 2010, 10:29 GMT
Last edited by Ionut Biru (wonder) - Saturday, 19 February 2011, 19:30 GMT
|
DetailsDescription:
After gnome-screensaver update two days ago, it's impossible to properly resume from suspend - there is only black screen and only poweroff helps (switching to console is also impossible). Working fine on previous version. Additional info: extra/gnome-screensaver 2.30.0-3 (gnome) 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) Steps to reproduce: 1. Choose 'suspend' in Gnome. 2. Turn your computer on after suspend. 3. You'll see only black screen without possibility to log in. |
This task depends upon
Closed by Ionut Biru (wonder)
Saturday, 19 February 2011, 19:30 GMT
Reason for closing: Not a bug
Additional comments about closing: not related to gnome-screensaver.
Saturday, 19 February 2011, 19:30 GMT
Reason for closing: Not a bug
Additional comments about closing: not related to gnome-screensaver.
Comment by Jan de Groot (JGC) -
Thursday, 20 January 2011, 21:36 GMT
This works on my systems. Are you sure this is caused by gnome-screensaver? gnome-screensaver has nothing to do with suspend/resume, so the bug is somewhere else. Can you provide logs (dmesg output, /var/log/pm-*.log files) when this fails? Please use the latest version of pm-utils to generate the logfiles, as older versions overwrite the log on each action.