SDDM is Failing to Launch [Journal Logs Attached]

General system Newbie
1

So I’ll get right to my problem.

I followed the Official EndeavourOS guide on setting up a “LUKSonBTRFS” install of EndeavourOS from the Wiki, the installation process was long but went without any issues.

I booted into the system, setup TimeShift accordingly to what the Wiki suggested and made a MANUAL TimeShift Snapshot.

I then shutdown my system.
I then waited approximately 3 Minutes and then proceeded to switch the laptop back on and boot into EndeavourOS as per normal, the drive was successfully decrypted but that is as far as I got.

Once the wording saying; “Starting version 249.3-1-arch” appeared the system waits about 5 seconds then displays a message saying;
“[FAILED] Failed to start Simple Desktop Display Manager.”

Following this the system does nothing else and just sits waiting for input or output of some kind (I guess), the cursor flashes but nothing else happens.

Why is SDDM failing to launch on a brand new install?

NOTE:
I have also asked this question in the Matrix Chat but decided to post my question here as that is what they advised me to do.

UPDATE:
Journal Logs are attached below -
Here is the output of the following commands;
cat /tmp/journal | eos-sendlog — https://clbin.com/2Gpsr
cat /tmp/journal.last | eos-sendlog — https://clbin.com/wspCx
cat /tmp/journal.2last | eos-sendlog — https://clbin.com/77KyB

2

Did you do

journalctl -b -0 > /tmp/journal

first?

3

No, I’ll try that now.

4

Hey again by the way!

Anyway,

Here is the output of the following commands;
cat /tmp/journal | eos-sendlog — https://clbin.com/2Gpsr
cat /tmp/journal.last | eos-sendlog — https://clbin.com/wspCx
cat /tmp/journal.2last | eos-sendlog — https://clbin.com/77KyB

I hope they prove to be useful in helping me to solve this issue,

Thanks once again!

UPDATE:
Logs are now also available in the original post further up/earlier on in this thread.

1 Like
5

Thanks! Please wait for the boys with big guns to arrive to trouble-shoot!
Good luck!

6

Thanks Dude/Dudet!

1 Like
7

how about reinstalling sddm and enabling sddm service ?

8

@TOGLK

Looks like an update issue with sddm.
Did you / can you do

sudo pacman -Syyu

?

And could you show your latest updates:

tac /var/log/pacman.log | head -n50 | eos-sendlog
9

Need to check if sddm is actually installed. If not it needs to be installed and then enabled.

10

pacman -Q sddm

11

There seems to be an issue with this GLIBCXX_3.4.29 in the logs

 sddm[614]: /usr/bin/sddm: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /usr/lib/libQt5Qml.so.5)
Aug 11 10:00:58 GS63VR-GMNG-LPTP-EOSKDE sddm[614]: /usr/bin/sddm: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /usr/lib/libQt5Network.so.5)
Aug 11 10:00:58 GS63VR-GMNG-LPTP-EOSKDE sddm[614]: /usr/bin/sddm: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /usr/lib/libQt5Core.so.5)
Aug 11 10:00:58 GS63VR-GMNG-LPTP-EOSKDE sddm[614]: /usr/bin/sddm: /usr/lib/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /usr/lib/libQt5Core.so.5)
Aug 11 10:00:58 GS63VR-GMNG-LPTP-EOSKDE systemd[1]: sddm.service: Main process exited, code=exited, status=1/FAILURE
Aug 11 10:00:58 GS63VR-GMNG-LPTP-EOSKDE systemd[1]: sddm.service: Failed with result 'exit-code'.
1 Like
12

This seems to be a repeating thing, loads of applications need this GLIBCXX_3.4.29 package/file but I don’t know where it comes from or how to fix it.

13

I’ve given it a go at updating SDDM using sudo pacman -S sddm & yay -S sddm
On both occasions it simply reinstalled SDDM, but upon rebooting the laptop SDDM would still fail to boot.

I’ll grab those logs following that command you’ve just posted and I’ll add the link to this thread lower down as a separate message.

The system is fully up-to-date, in fact when I run sudo pacman -Syyuu or yay -Syyuu from a separate TTY session I get a bunch of warnings (over 30) saying that many of my packages are “too new”… No idea what that even means or how that is possible.

14

Here is the link to the output of the following command;

Command;
tac /var/log/pacman.log | head -n50 | eos-sendlog

Output;
https://clbin.com/rzed1

15

The output of that command is aa follows;
sddm 0.19.0-4

16

I’ll come back to this tomorrow, but seeing as I’m less than 1 day into a fresh install and it’s already broken I think I may reinstall again using a fresh ISO just to be sure that nothing has gone wrong during installation.

I’ve been following the LUKSonBTRFS guide on the Official Wiki.
But… I moved my home directory to a different drive and it is using EXT4 instead of BTRFS, this shouldn’t be the cause of any issues but I’m mentioning it anyway just in case it could be.

17

Seems that you have version mismatches on some packages.
That might be caused by a not-so-good mirror list.

Reinstall may help to get the initial state right. But after that, you probably want to run reflector-simple to re-create the Arch mirror list.

Also, some AUR packages may cause library mismatches, so it is better to avoid AUR packages when similar official packages are available.

18

Sorry for the late reply.

In the end I just did a fresh re-install with a freshly re-downloaded ISO image of EndeavourOS, that seemed to resolve the issues that I was having.

I will mark this as solved.

Solution to the problem - Re-install the system using a fresh ISO image.

19

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.