Please sign in to comment.
Remove support for GNOME screensaver.
The GNOME developers broke the "legacy" inhibit support (inhibit via gnome-screensaver-command) a couple years ago and seem to have no intention of ever fixing it, instead focusing on forcing every single media player application in the world (or other applications needing to provide hints to the screensaver) to add D-Bus-based inhibit requests using their GNOME-specific D-Bus API (see https://bugzilla.gnome.org/show_bug.cgi?id=579430 ). (Of course, this approach would then mean all of those applications must also implement code to add D-Bus-based inhibit requests using the KDE-specific D-Bus API to support users running KDE screensaver, and ... And, as a point of note, KDE has taken the same approach and has the same expectation of applications.) Therefore, this patch removes the GNOME screensaver legacy inhibit support so that users of GNOME screensaver, like users of KDE screensaver, will fall back to getting DPMS-based screensaver control. If GNOME screensaver, like KDE screensaver, actually takes the hint when the DPMS state is changed, this should allow users to once again run GNOME screensaver (which has been unsupported since GNOME broke gnome-screensaver-command --poke) without the screensaver activating during playback. If GNOME screensaver doesn't take a clue from the DPMS state, GNOME screensaver should be fixed. This change does not purport to provide support for users who run GNOME screensaver. This simply removes the code that calls a broken program that GNOME has said they will not fix.
- Loading branch information...
Showing with 2 additions and 18 deletions.