Description of problem: I upgraded fro mga7 to mga8. Two problems-- nfs did not start up on its own-- I had to start it manually, but the worse problem is that SDDM has stopped working-- the login screen does nothing when I try to log in. If I do alt-ctrl-F2 and open up a text console, I can log in ( with the same passwords I tried in sddm) and run startx -- :1 and a Plasma desktop opens without incident. But sddm does not open a desktop (or do anything at all as far as I can see) I have tried both Plasma and XFCE as the desktop in sddm and neither work Here is the journalctl for an attempt to logon to the sddm Mote that 989 is the sddm user id. 1000 is that of me, unruh Apr 12 15:18:47 info sddm-greeter[613555]: QFont::fromString: Invalid description '(empty)' Apr 12 15:18:47 info sddm-greeter[613555]: Loading file:///usr/share/sddm/themes/mga-coffee/Main.qml... Apr 12 15:22:08 info systemd-logind[848]: New session c32 of user unruh. Apr 12 15:22:08 info systemd[1]: Started Session c32 of user unruh. Apr 12 15:22:08 info systemd[1]: session-c31.scope: Succeeded. Apr 12 15:22:08 info systemd-logind[848]: Session c31 logged out. Waiting for processes to exit. Apr 12 15:22:08 info systemd-logind[848]: Removed session c31. Apr 12 15:22:08 info sddm-helper[622347]: Starting: "/usr/share/sddm/scripts/Xsession \"/usr/bin/startplasma-x11\"" Apr 12 15:22:08 info systemd[1]: Starting Hostname Service... Apr 12 15:22:08 info systemd[1]: Started Hostname Service. Apr 12 15:22:18 info systemd[1]: Stopping User Manager for UID 989... Apr 12 15:22:18 info systemd[613502]: Stopped target Main User Target. Apr 12 15:22:18 info systemd[613502]: Stopping D-Bus User Message Bus... Apr 12 15:22:18 info systemd[613502]: Stopping GnuPG cryptographic agent and passphrase cache... Apr 12 15:22:18 info gpg-agent[613553]: SIGTERM received - shutting down ... Apr 12 15:22:18 info systemd[613502]: dbus.service: Succeeded. Apr 12 15:22:18 info systemd[613502]: Stopped D-Bus User Message Bus. Apr 12 15:22:18 info gpg-agent[613553]: gpg-agent (GnuPG) 2.2.27 stopped Apr 12 15:22:18 info systemd[613502]: gpg-agent.service: Succeeded. Apr 12 15:22:18 info systemd[613502]: Stopped GnuPG cryptographic agent and passphrase cache. Apr 12 15:22:18 info systemd[613502]: Stopped target Basic System. Apr 12 15:22:18 info systemd[613502]: Stopped target Paths. Apr 12 15:22:18 info systemd[613502]: Stopped target Sockets. Apr 12 15:22:18 info systemd[613502]: Stopped target Timers. Apr 12 15:22:18 info systemd[613502]: dbus.socket: Succeeded. Apr 12 15:22:18 info systemd[613502]: Closed D-Bus User Message Bus Socket. Apr 12 15:22:18 info systemd[613502]: gpg-agent.socket: Succeeded. Apr 12 15:22:18 info systemd[613502]: Closed GnuPG cryptographic agent and passphrase cache. Apr 12 15:22:18 info systemd[613502]: pulseaudio.socket: Succeeded. Apr 12 15:22:18 info systemd[613502]: Closed Sound System. Apr 12 15:22:18 info systemd[613502]: Reached target Shutdown. Apr 12 15:22:18 info systemd[613502]: systemd-exit.service: Succeeded. Apr 12 15:22:18 info systemd[613502]: Finished Exit the Session. Apr 12 15:22:18 info systemd[613502]: Reached target Exit the Session. Apr 12 15:22:18 info systemd[1]: user@989.service: Succeeded. Apr 12 15:22:18 info systemd[1]: Stopped User Manager for UID 989. Apr 12 15:22:18 info systemd[1]: Stopping User Runtime Directory /run/user/989... Apr 12 15:22:18 info systemd[8811]: run-user-989.mount: Succeeded. Apr 12 15:22:18 info systemd[107454]: run-user-989.mount: Succeeded. Apr 12 15:22:18 info systemd[8829]: run-user-989.mount: Succeeded. Apr 12 15:22:18 info systemd[1]: run-user-989.mount: Succeeded. Apr 12 15:22:18 info systemd[1]: user-runtime-dir@989.service: Succeeded. Apr 12 15:22:18 info systemd[1]: Stopped User Runtime Directory /run/user/989. Apr 12 15:22:18 info systemd[1]: Removed slice User Slice of UID 989. Apr 12 15:22:38 info systemd[1]: Starting dnf makecache... Apr 12 15:22:38 info systemd[1]: systemd-hostnamed.service: Succeeded. Apr 12 15:22:39 info dnf[623177]: Metadata cache refreshed recently. Apr 12 15:22:39 info systemd[1]: dnf-makecache.service: Succeeded. . Version-Release number of selected component (if applicable):sddm-0.19.0-15.1.mga8 How reproducible:Always Steps to Reproduce: Choose user. Type password into sddm-greeter. Hit return and wait forever while nothing happens.
Is this the same as bug 27601 ? If so, it's in the errata https://wiki.mageia.org/en/Mageia_8_Errata#Desktops
CC: (none) => davidwhodgins
No, it does not seem to be the same bug. In my case nothing whatsoever happens. I still have the sddm-greeting page displayed, with my name, the spots for the password, Plasma or XFCE as the dm. Ie, hitting return is as if I had never done anything Just the same screen as before I hit return. And the machine has a definite hostname all the time (info). I upgraded three other machines as well and all cannot be logged into from the SDDM-greeter. One of them keeps flashing as I move the mouse. The other two also just sit there once I enter the username and password.
Did you try changing the SDDM theme?
No. Any suggestions? Since mga-coffee is based on maldives, that is probably not the best to try first. I presume all I do is change the Current line in /etc/sddm.conf file.
> Plasma or XFCE as the dm You probably meant 'as the [target] desktop'. SDDM & lightDM are display managers, for the login. Although it is not the proper solution, is there any reason not to install & change to (say) lightDM, at least to be able to login (assuming it works!)... You can do this from a virtual console, as root: # urpmi lightdm # drakdm which enables you to swap between them at will; normally requires a reboot to take effect. If this persists, I will try SDDM to compare journals.
CC: (none) => lewyssmith
Not sure if this will help to narrow down the problem but I experienced the same symptoms in cauldron when several plasma packages were inadvertently pushed to core rather than updates_testing recently. I use a common home folder for Mageia8 and Cauldron on my system. When the above packages were installed, sddm stopped working for my regular user in both Mga8 and Cauldron with the same symptoms as in this bug. By using LXDM in Mga8 I was able to log in and use it normally with plasma. When the new packages were finally released for Cauldron plasma and it was fully updated, sddm worked fine and also reverting to sddm in Mga8 also worked as before the problem. So it seems that something broke in the user home settings which caused the sddm issue. You could confirm this by creating a new user and testing sddm to log in as that user.
CC: (none) => zen25000
@Bill Is this still an issue?
No it has gone away By this time I am not even sure which machine this was on (I have at least 4 of them). So sddm does seem to be working now. 2
Thanks.
Status: NEW => RESOLVEDResolution: (none) => FIXED