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#24382 - [xdg-utils] xdg-screensaver erroneously detects gnome screensaver
Attached to Project:
Arch Linux
Opened by Norbert Zeh (nzeh) - Saturday, 21 May 2011, 21:37 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 25 May 2012, 16:07 GMT
Opened by Norbert Zeh (nzeh) - Saturday, 21 May 2011, 21:37 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 25 May 2012, 16:07 GMT
|
DetailsDescription: With xscreensaver running, xdg-screensaver sets DE="gnome-screensaver" and, consequently, fails to talk to xscreensaver, trying to talk to gnome-screensaver instead. This leads to a number of problems, including xscreensaver kicking while watching a movie in xine because "xdg-screensaver suspend <win>" does not deactivate xscreensaver.
The problem seems to be that the xdg-screensaver script relies on gnome-screensaver-command returning a non-zero exit code if gnome-screensaver isn't running. This is the strategy it also uses for xscreensaver, and there it works: xscreensaver-command -version returns 255 if xscreensaver isn't running. gnome-screensaver-command, on the other hand, returns 0 no matter what, overriding the previously detected xscreensaver. Additional info: * package version(s) xdg-utils 1.1.0rc1-2 gnome-screensaver 3.0.0-1 Steps to reproduce: 1. Fire up xscreensaver as the screensaver 2. Try "xdg-screensaver activate". This should start the screensaver, but nothing happens. |
This task depends upon
Comment by Andreas Radke (AndyRTR) -
Sunday, 20 May 2012, 09:29 GMT
Please check xdg-utils-1.1.0-0.20120520-any.pkg.tar.xz in testing if this has been solved or file an upstream issue.