Last night, I did an emerge update @world, which included an upgrade of sddm I think it's this package x11-misc/sddm, but I'm not sure. Installed versions: 0.14.0-r2(12:07:07 30/01/17)(consolekit pam -systemd) In any case, when I logged in this morning, I was greeted by the sddm session manager with the message: "The current theme cannot be loaded due to the errors below. please select another theme." "file:///usr/share/sddm/themes/maui/Main.qml: file not found." I know where and how to configure the sddm theme. The problems are: 1) Where is the error log file for sddm? I grepped /var/log/ but couldn't find any mention of the error above. Luckily I had taken a picture of my monitor before starting the session, so I could copy the error message. Also, in /etc/sddm.conf, I don't see any setting related to error log files. Can errors be logged at all? 2) As of this morning, I have: # ls /usr/share/sddm/themes/maui/ theme.conf.user Why was the maui theme removed? I am posting this here because I am not sure if it is a packaging/ebuild problem, or new requirements from sddm which the older (??) theme does not satisfy.
From the upstream ChangeLog: * REMOVED the "maui" theme as a standalone theme as it is now embedded in the greeter. Remember to change the theme to empty if you had it set to "maui".
As for logging, I have /var/log/sddm.log but I don't know if theme errors are logged there or not.
Thank you Michael. I did look at /var/log/sddm.log and looked again right now, but there is nothing related to the error above. I will file reports upstream and report back here.
Error did not get logged #770 https://github.com/sddm/sddm/issues/770 I have various issues with the logs themselves.
The theme maui is gone #771 https://github.com/sddm/sddm/issues/771 In my report upstream, I give the context then give a list of 4 problems I have with this disappearance, the fourth of which concerns package managers (the gentoo ebuild). I quote: "4) What procedures or policies do you have in place in such cases where user configurations are affected? To what extent is it the package managers' duty to migrate and deal with deprecated configuration, like the one described here?"
Reply in the ticket in #4 seem to indicate that sddm requires systemd to be fully functional. I installed my whole gentoo system with -systemd use flag. They mention the CMake variable ENABLE_JOURNAL which I do not see used in the sddm.ebuild.
Unfortunately many components in the desktop ecosystem these days either require systemd to be fully functional, or the developers don't test non-systemd configurations. I'm not sure why the logging doesn't happen properly or the theme doesn't fall back correctly as per the referenced commits in the upstream ticket.(In reply to augustin from comment #6) > Reply in the ticket in #4 seem to indicate that sddm requires systemd to be > fully functional. I installed my whole gentoo system with -systemd use flag. > > They mention the CMake variable ENABLE_JOURNAL which I do not see used in > the sddm.ebuild. While indeed we don't set that variable directly, it only comes into play if systemd support is enabled which we do control (-DNO_SYSTEMD=$(usex '!systemd')).
