[Bug 1703690] [NEW] Add support for Budgie Desktop using GNOME Screensaver

[Launchpad Bug Tracker]

You have been subscribed to a public bug by fossfreedom (fossfreedom):

Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock-
screen.

It also uses gnome-control-center to control both the desktop background
and the lock-screen background.

GNOME Screensaver does not support gnome-control-center lock screen
dialog - GNOME has changed to a gsettings path
org.gnome.desktop.screensaver.  GNOME Screensaver is expecting the path
org.gnome.desktop.background.

To resolve this requires patches in two packages - gnome-screensaver and
gnome-desktop3.

1. GNOME Screensaver has been patched to support Budgie Desktop and gnome-control-center.
Note - I've taken the opportunity to reuse the existing "Unity" patchwork which is now defunct (I believe) since Unity uses an alternative locking mechanism.  The lock-screen is styled as per the old "Unity" implementation before Unity 16.04 moved to the new lock screen.

2. The consequence of making the requisite changes to GNOME Screensaver
has unfortunately impacted gnome-desktop3.  gnome-desktop3 has a Ubuntu
specific patch to revert a GNOME upstream decision to remove a key
called draw-background.  GNOME Screensaver calls a public function in
gnome-desktop3 - the gsettings path causes a segmentation fault since
draw-background does not exist in org.gnome.desktop.screensaver.  I have
worked around this to check the path being called before pulling the
draw-background key.

All of this is explained in the dep3 headers of the two debdiff patches
attached

** Affects: gnome-desktop3 (Ubuntu)
     Importance: Undecided
     Assignee: fossfreedom (fossfreedom)
         Status: In Progress

** Affects: gnome-screensaver (Ubuntu)
     Importance: Undecided
     Assignee: fossfreedom (fossfreedom)
         Status: In Progress


** Tags: artful
-- 
Add support for Budgie Desktop using GNOME Screensaver
https://bugs.launchpad.net/bugs/1703690
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.