Hello, I just upgraded to mageia 9 on a 32bit server and I got an error, failed to start lightdm.service. systemctl status lightdm.service × lightdm.service - Light Display Manager Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Mon 2023-06-19 16:33:01 PDT; 2min 48s ago Duration: 390ms Docs: man:lightdm(1) Process: 2118 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE) Main PID: 2118 (code=exited, status=1/FAILURE) CPU: 174ms Jun 19 16:33:01 localhost systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5. Jun 19 16:33:01 localhost systemd[1]: Stopped lightdm.service. Jun 19 16:33:01 localhost systemd[1]: lightdm.service: Start request repeated too quickly. Jun 19 16:33:01 localhost systemd[1]: lightdm.service: Failed with result 'exit-code'. Jun 19 16:33:01 localhost systemd[1]: Failed to start lightdm.service. Regards
It's working for me with ... $ rpm -qa|grep lightdm|sort liblightdm-gobject1_0-1.32.0-1.mga9 lightdm-1.32.0-1.mga9 lightdm-gtk3-greeter-2.0.8-4.mga9 lightdm-gtk-greeter-common-2.0.8-4.mga9 lightdm-gtk-greeter-settings-1.2.2-8.mga9 [dave@i9v ~]$ uname -a Linux i9v.hodgins.homeip.net 6.3.8-desktop-2.mga9 #1 SMP PREEMPT_DYNAMIC Mon Jun 19 19:13:10 UTC 2023 i686 GNU/Linux It's an m9 i586 install under virtualbox. Does xdm work?
CC: (none) => davidwhodgins
To test xdm, ensure xdm is installed and change /etc/sysconfig/desktop to have DISPLAYMANAGER=xdm
(In reply to Dave Hodgins from comment #1) > It's working for me with ... > $ rpm -qa|grep lightdm|sort > liblightdm-gobject1_0-1.32.0-1.mga9 > lightdm-1.32.0-1.mga9 > lightdm-gtk3-greeter-2.0.8-4.mga9 > lightdm-gtk-greeter-common-2.0.8-4.mga9 > lightdm-gtk-greeter-settings-1.2.2-8.mga9 > [dave@i9v ~]$ uname -a > Linux i9v.hodgins.homeip.net 6.3.8-desktop-2.mga9 #1 SMP PREEMPT_DYNAMIC Mon > Jun 19 19:13:10 UTC 2023 i686 GNU/Linux I have same versions, rpm -qa|grep lightdm|sort liblightdm-gobject1_0-1.32.0-1.mga9 lightdm-1.32.0-1.mga9 lightdm-gtk3-greeter-2.0.8-4.mga9 lightdm-gtk-greeter-common-2.0.8-4.mga9 lightdm-gtk-greeter-settings-1.2.2-8.mga9 systemctl status lightdm.service × lightdm.service - Light Display Manager Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Mon 2023-06-19 16:33:01 PDT; 18h ago Duration: 390ms Docs: man:lightdm(1) Process: 2118 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE) Main PID: 2118 (code=exited, status=1/FAILURE) CPU: 174ms Jun 19 16:33:01 localhost systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5. Jun 19 16:33:01 localhost systemd[1]: Stopped lightdm.service. Jun 19 16:33:01 localhost systemd[1]: lightdm.service: Start request repeated too quickly. Jun 19 16:33:01 localhost systemd[1]: lightdm.service: Failed with result 'exit-code'. Jun 19 16:33:01 localhost systemd[1]: Failed to start lightdm.service. > It's an m9 i586 install under virtualbox. I installed it on a Dell PowerEdge 750 server, Mageia 8 works fine with latest updates until I upgraded to mageia 9 for testing.. systemctl restart lightdm.service also fails, I get same error onscreen > Does xdm work? No it does´nt, I now get failed to start xdm.service. I tried running and restarting the service via ssh to see it continues to the logins screen but I got the same errors.
journalctl -xb --since "3 minutes ago" Jun 20 11:14:54 localhost systemd[1]: xdm.service: Failed with result 'protocol'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ The unit xdm.service has entered the 'failed' state with result 'protocol'. Jun 20 11:14:54 localhost systemd[1]: Failed to start xdm.service. ░░ Subject: A start job for unit xdm.service has failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit xdm.service has finished with a failure. ░░ ░░ The job identifier is 1886 and the job result is failed. Jun 20 11:14:54 localhost systemd[1]: xdm.service: Scheduled restart job, restart counter is at 14. ░░ Subject: Automatic restarting of a unit has been scheduled ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ Automatic restarting of the unit xdm.service has been scheduled, as the result for ░░ the configured Restart= setting for the unit. Jun 20 11:14:54 localhost systemd[1]: Stopped xdm.service. ░░ Subject: A stop job for unit xdm.service has finished ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A stop job for unit xdm.service has finished. ░░ ░░ The job identifier is 1987 and the job result is done. Jun 20 11:14:54 localhost systemd[1]: Starting xdm.service... ░░ Subject: A start job for unit xdm.service has begun execution ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
More info. Host: PowerEdge 750 CPU: Intel Celeron 2.40GHz (1) @ 2.400GHz GPU: AMD ATI Rage XL PCI Kernel: 6.3.8-desktop-2.mga9
Can you Ezequiel please say how you did the upgrade? This looks like a systemd issue, since the same thing happens with 2 display managers. The log lines above are very few: systemd[1]: xdm.service: Failed with result 'protocol'. systemd[1]: Failed to start xdm.service. systemd[1]: xdm.service: Scheduled restart job, restart counter is at 14. systemd[1]: Stopped xdm.service systemd[1]: Starting xdm.service... and I wonder whether the journal before the first failure would help. Since this happens at boot, it should be OK to attach the entire compressed journal for the session once the failure is hit: $ journalctl -b --no-hostname > journal.txt $ xz journal.txt and attach the result journal.txt.xz to this bug.
CC: (none) => lewyssmith
Created attachment 13884 [details] journalctl results Here is my journalctl text.
(In reply to Lewis Smith from comment #6) > Can you Ezequiel please say how you did the upgrade? I upgraded using the next commands: urpmi.removemedia -a urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.9.$ARCH.list' urpmi --auto-update --auto --force
BTW Lewis, Can you please check my response on https://bugs.mageia.org/show_bug.cgi?id=30090 Please.. It think I found a solution on that and probably 30984, I will install gnome and test too. Regards
(In reply to Ezequiel Partida from comment #9) > Can you please check my response on > https://bugs.mageia.org/show_bug.cgi?id=30090 Just did, thank you. But unrelated to this bug. > I think I found a solution on that (c5) and probably 30984, I will > install gnome and test too. Are you saying that the fix you found for bug 30090 might also fix bug 30984? Please comment on that one if so. --------------------------------- Back to this bug, & the journal (thanks for same). I cannot see anything particular in it before the failures. This is the first mention of XDM: Jun 21 12:29:39 systemd[1]: Starting xdm.service... Jun 21 12:29:55 systemd[1]: xdm.service: Failed with result 'protocol'. Jun 21 12:29:55 systemd[1]: Failed to start xdm.service Jun 21 12:29:55 systemd[1]: xdm.service: Scheduled restart job, restart counter is at 1. Jun 21 12:29:55 systemd[1]: Stopped xdm.service. then Jun 21 12:29:55 systemd[1]: Starting xdm.service... and the same sequence ad infinitum. Cannot see better than to assign this globally.
CC: lewyssmith => (none)Severity: normal => majorHardware: All => i586Assignee: bugsquad => pkg-bugsSummary: Failed to start lightdm.service on 32bit mageia 9 => Following upgrade 8-9, Failed to start lightdm.service or XDM on 32bit mageia 9