LightDM can't use the user background on Mate

Bug #1660121 reported by Brice Terzaghi on 2017-01-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-mate
Undecided
Unassigned

Bug Description

Using Ubuntu Mate 16.10 (the issue appears too on 16.04 and 17.04 alpha 2).

On Mate, the LightDM Gtk Greeter can't use the user background. It works fine on other DEs like Xfce.

From what I understand, LightDM and/or the Gkt greeter (not sure which one handles the background) gets the background path from Gsettings, so I assume it can't find the one from Mate, which stores it in "org.mate.background picture-filename".

Brice Terzaghi (terzag) on 2017-02-17
affects: lightdm-gtk-greeter → ubuntu-mate
Brice Terzaghi (terzag) wrote :

I've found additional info in a Cinnamon bug report (https://github.com/linuxmint/Cinnamon/issues/2379). The issue is in fact with mate-settings-daemon (I've updated the current report to ubuntu-mate, not sure it's the right project).

On environments like Gnome 3 / Unity (and presumably Xfce), the settings daemon checks for the use background changes and updates the /var/lib/AccountsSerice/users/username (where "username" is the current user) to add/update the Background option in the [User] section (Background=/path/to/the/background/picture).

It seems to be made through gsettings with a command like this (on Gnome 3):
gsettings set org.gnome.settings-daemon.plugins.background active true

Mate-settings-daemon doesn't seem to have an equivalent to this org.gnome.settings-daemon.plugins.background as I can't find a similar key in org.mate.

Not sure of the proper way to integrate mate-settings-daemon to AccountsService so that it updates the /var/lib/AccountsService/users/username file but I guess it has to work the same way as gnome-settings-daemon and unity-settings-daemon.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.