Failed to open lightdm configuration file

[Cody Garver]

Loki/Wily:

Failed to open configuration file /etc/lightdm/lightdm.conf: No such file or directory
Failed to open configuration directory /etc/lightdm/lightdm.conf.d: Error opening directory '/etc/lightdm/lightdm.conf.d': No such file or directory
Failed to open configuration directory /etc/xdg/xdg-pantheon/lightdm/lightdm.conf.d: Error opening directory '/etc/xdg/xdg-pantheon/lightdm/lightdm.conf.d': No such file or directory
Failed to open configuration directory /etc/xdg/lightdm/lightdm.conf.d: Error opening directory '/etc/xdg/lightdm/lightdm.conf.d': No such file or directory
Failed to open configuration directory /usr/share/pantheon/lightdm/lightdm.conf.d: Error opening directory '/usr/share/pantheon/lightdm/lightdm.conf.d': No such file or directory
Failed to open configuration directory /usr/share/gnome/lightdm/lightdm.conf.d: Error opening directory '/usr/share/gnome/lightdm/lightdm.conf.d': No such file or directory
Failed to open configuration directory /usr/local/share/lightdm/lightdm.conf.d: Error opening directory '/usr/local/share/lightdm/lightdm.conf.d': No such file or directory
'[SeatDefaults] allow-guest' is not set anywhere assuming default 'true'

[Danielle Foré (danrabbit)]

I can confirm that I also get this error message when opening the accounts plug in Wily/Loki

[David Howell (david-dynmeth)]

This is due to the 'set_config_in_file()' not creating the key if it does not exist. The optional param of create is not being used, so defaults to false.

It finds the first /etc/lightdm/lightdm.conf file but doesn't find the key, so returns false to move on to the next conf location.

Two potential solutions:

1. create the key if it doesn't exist
2. put the key in the lightdm.conf file by default

I'm assuming 1 is the better option?

[Cody Garver (codygarver)]

I decided this is a non-issue because it's assuming allow-guest=true, which is what we want. And if the user disables it, it creates the file /usr/share/lightdm/lightdm.conf.d/60-guest-session.conf with that content. And if the user re-enables it, it changes the value to true accordingly.