Kubuntu - SDDM not loading (lemmy.sdf.org)

submitted 20 hours ago* (last edited 20 hours ago) by RubberDuckyDJ@lemmy.sdf.org to c/linux@programming.dev

5 comments fedilink hide all child comments

At first Instead of my SDDM I would just see an after image of what was last displayed on screen. But if I typed in my password and pressed enter, it would let me in just fine. Then after following some suggestions from users in r/Kubuntu I’ve made a bit of progress. Now when I boot up my computer instead of the SDDM being invisible, it now doesn’t load at all, from there I switch to tty3 then back to tty2 and then log in through the terminal. After that I run startplasma-wayland and then I have access to my desktop. The post where all this went down - https://www.reddit.com/r/Kubuntu/comments/1nvreuo/sddm_not_rendering/

Does anyone know a fix? I would like to be able to see my login screen.

Here’s my specs in case that would help - https://i.imgur.com/XtC43zw.png

And here’s my journalctl output after booting and launching plasma - https://pastebin.com/nnGsWebd

you are viewing a single comment's thread
view the rest of the comments

[-] A_norny_mousse@feddit.org 3 points 14 hours ago

Your journal output might be too curated, I don't see anything that would keep the display manager from starting up.

Then after following some suggestions from users in r/Kubuntu I’ve made a bit of progress.

We'd need more info on this, like what exactly did you change and what was that progress and how/when did it turn into regress.

Journal output for SDDM and related services, and for the relevant timeframe, would be better.

I suppose SDDM is the default for Kubuntu, and if you had done other possibly relevant things to your setup you'd have told us.

FWIW, it could be GPU related, but that really just is a wild guess.

PS: identical post here: https://lemmy.sdf.org/post/43982607

[-] Successful_Try543@feddit.org 2 points 14 hours ago* (last edited 13 hours ago)

Your journal output might be too curated, I don't see anything that would keep the display manager from starting up.

The only suspicious entry I've found was #185:

sddm[1596]: Failed to read display number from pipe

FWIW, it could be GPU related, but that really just is a wild guess.

Skimming search results onto the above error message seems to second your idea.

[-] A_norny_mousse@feddit.org 1 points 7 hours ago

👍 I missed that one. Yeah, OP should at least look what else is happening around that.

[-] RubberDuckyDJ@lemmy.sdf.org 1 points 6 hours ago

The issue is I have no idea what any of these errors mean. I'm pretty new to desktop Linux so I've just been researching the errors one by one but so far, no dice.

[-] A_norny_mousse@feddit.org 1 points 3 hours ago

Show us! The journalctl output was too restricted, we need to see all of it - at least for the significant timeframe.

this post was submitted on 13 Oct 2025

12 points (87.5% liked)

Linux

9720 readers

113 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev