I am successfully running the xfce desktop, using lightdm with the lightdm-gtk-greeter for login.
I installed lightdm-gtk-greeter-settings, and I now have a "LightDM GTK+ Greeter Settings" under "System" on the whisker menu. When I click on it, nothing happens.
If I run /usr/local/bin/lightdm-gtk-greeter-settings from an ordinary user, I get a popup warning me that I have to be root to save the configuration, and it comes up in read-only mode.
If I run it as root, I get the following messages, then it come up and works like a champ:
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
I don't know how the xfce whisker menu would know that it needs to run as root, so that might be part of the problem. Since the file is owned by root:wheel, I thought turning on the setuid bit might help. (I am not real familiar with using the setuid bit, so I may misunderstand how it works, if it seems like it should make the program run under the owner's uid.)
Still nothing happens when I select the option from the whisker menu. I looked in all the logs in /var/log/, and did not see any errors reported.
Can someone suggest what my next step should be for troubleshooting the problem?
Thanks!
I installed lightdm-gtk-greeter-settings, and I now have a "LightDM GTK+ Greeter Settings" under "System" on the whisker menu. When I click on it, nothing happens.
If I run /usr/local/bin/lightdm-gtk-greeter-settings from an ordinary user, I get a popup warning me that I have to be root to save the configuration, and it comes up in read-only mode.
If I run it as root, I get the following messages, then it come up and works like a champ:
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
I don't know how the xfce whisker menu would know that it needs to run as root, so that might be part of the problem. Since the file is owned by root:wheel, I thought turning on the setuid bit might help. (I am not real familiar with using the setuid bit, so I may misunderstand how it works, if it seems like it should make the program run under the owner's uid.)
Still nothing happens when I select the option from the whisker menu. I looked in all the logs in /var/log/, and did not see any errors reported.
Can someone suggest what my next step should be for troubleshooting the problem?
Thanks!