system76panp9
August 14th, 2013, 05:38 AM
on my Ubuntu 13.04 system I am trying to change some of the login screen
settings which can only be affected apparently by updating the dconf db that
the lightdm process reads when managing the login
I have tried different variations of this basic command:
sudo sudo -u lightdm dbus-launch --exit-with-session gsettings set ...
in each case I get error messages which make it clear that an attempt is
being made to update MY dconf database, that is, the one stored in my
OWN home directory and which would not have any impact on what
lightdm does (for instance, errors saying that the "user" file in the
dconf subdirectory under my home directory cannot be modified)
if I type
sudo sudo -u lightdm whoami
I get back "lightdm" so I have no clue why it still wants to try to
change the dconf settings of my user
I guess I could try to run this as a setup script on greeter launch?
then at least it would not have any reason to look in my home
directory presumably, but where would gsettings then try to look?
what directory is used to store the dconf db for "lightdm"? is it
looking at like the HOME env variable which is somehow copied
over despite the sudo -u to the context in which gsettings is run?
any help would be very much appreciated as I am completely
mystified
settings which can only be affected apparently by updating the dconf db that
the lightdm process reads when managing the login
I have tried different variations of this basic command:
sudo sudo -u lightdm dbus-launch --exit-with-session gsettings set ...
in each case I get error messages which make it clear that an attempt is
being made to update MY dconf database, that is, the one stored in my
OWN home directory and which would not have any impact on what
lightdm does (for instance, errors saying that the "user" file in the
dconf subdirectory under my home directory cannot be modified)
if I type
sudo sudo -u lightdm whoami
I get back "lightdm" so I have no clue why it still wants to try to
change the dconf settings of my user
I guess I could try to run this as a setup script on greeter launch?
then at least it would not have any reason to look in my home
directory presumably, but where would gsettings then try to look?
what directory is used to store the dconf db for "lightdm"? is it
looking at like the HOME env variable which is somehow copied
over despite the sudo -u to the context in which gsettings is run?
any help would be very much appreciated as I am completely
mystified