r/NobaraProject • u/Key-Cat-8744 • 17h ago

Support User Desktop does not start

My desktop does not wanna start after login. I did following troubleshooting: https://wiki.nobaraproject.org/general-usage/troubleshooting/black-screen

Everything described works except the last step. When I run startplasma-wayland the command stucks without any error. However when I login as root I can start and switch to desktop with the described workflow. If I would have to make a wild guess I would say its the recent AI wallpapers. I used one and maybe they were not removed carefully enough?

Anyway, since the desktop is working the issue seems to be not that big and I wonder what the script actually runs and how do I debug further from this point?

edit1: I made some progress. I created a new standard user and I could login without any problems. It seems that only the desktop of my original user is broken and not any desktop besides the superuser :)

edit2: Ok, users desktop is accessable again. Not 100% sure what went wrong but seems like a flatpak file xdg-desktop-portal was corrupted.

2 Upvotes

100% Upvoted

17 comments sorted by

2

u/RX1542 15h ago

check if this one does anything

dbus-run-session startplasma-wayland

2

u/Key-Cat-8744 15h ago

It does something. It brings me back to the loading screen which switches to the black screen with the cursor after sone seconds. So same behaviour like the login screen 🤔

Edit: i cannot switch with ctrl+alt+f3 after it tho

1

u/RX1542 15h ago

hmmm its weird i've seen this before but it was caused by a full disk, there was no space for the graphic session so the thing just went back to the login, but can't find the post to check

but since you say if you login with the root credentials it works then maybe its something else

1

u/Key-Cat-8744 14h ago

I create and logged into a new user too. seems that somehow only my old user desktop is broken which are kind of good news for me :)

1

u/RX1542 14h ago

yeah but its weird, i wonder if it was really caused by the AI wallpapers, if u wanna recover the user you could probably get more help on r/linux4noobs or r/linux_gaming since the movement on the sub is kinda low

you could also try the official nobara discord its very active

1

u/Key-Cat-8744 13h ago

looks like a corrupted flatpak was blocking the plasma start. Maaan, I am a passionate Windows hater but sometimes Linux life is difficult xD

1

u/RX1542 13h ago

oh how did you find out it was a flatpack?

yeah linux is uncharted territory for us so its a whole new experience hahaha, but once you get to know around the stuff it becomes quite cozy, like i've grown so accustomed to nobara over a year that i don't really see myself going back to win

2

u/Key-Cat-8744 12h ago

I tried a bunch of stuff. Reinstalling kde enviroment (before I had the new user), deleting caches, run dnf autoremove, resetting and replacing the background wallpaper (that was a completly wrong guess btw),... the thing which got me there was: logged in via terminal from my new user and threw the journalctl output into a LLM. 😅

it said KDE failed to register to the portal and so it will block everything from starting. I am not a complete Linux newbie, but I probably wouldn’t have figured that out on my own for a long time. I had no idea that plasma has to connect to flatpak in order to start.

1

u/RX1542 12h ago

its amazing how LLM can close the gap for us that are not as knowledgeable on this area, and yeah that plasma connection thing was unknown to me as well

ima save this post in case i come across someone with the same issue, always say i can just remember when it was and end up losing them 😅

anyway its great that you could fix it mate, hope you don't come across another hiccup any time soon

1

u/WayEmbarrassed9525 17h ago

Try this:

https://wiki.nobaraproject.org/general-usage/troubleshooting/diagnose-and-resolve-duplicates

1

u/Key-Cat-8744 17h ago

But I dont have incomplete updates or package conflicts 🤷‍♂️

1

u/WayEmbarrassed9525 17h ago

Try ithoit

1

u/Key-Cat-8744 17h ago

<dnf check --duplicates> does not print out anything 🤷‍♂️🤷‍♂️

1

u/WayEmbarrassed9525 17h ago

Thats Wrong.

Try this command:

sudo dnf rei $(dnf rq --duplicates --latest-limit=1 -q)

1

u/Key-Cat-8744 16h ago

Fails with missing argument for "rei". Probably because no duplicates are found.

And sudo dnf4 rm --duplicates: "No duplicated packages found for removal. Dependencies resolved. Nothing to do."

So I really dont get your idea behind all that? 🤷‍♂️

2

u/WayEmbarrassed9525 16h ago

Then you probably have more serious errors, or you described the error incorrectly. The command must display something 100% of the time: Mesa.

But since it isn't working for you, there could be deep-seated problems. Have you tried nobara-sync repair yet?

1

u/Key-Cat-8744 16h ago edited 16h ago

Yes i have. It does not indicate any issue. Like the usual sync it prints only INFOs.

I try to explain my problem again: the issue is that after login my desktop doesnt start and keeps black. So i switch to the grub: when i login with my normal user the startplasma-wayland script stucks without any error. nothing happens. (but not when i am logged in as root. Then it switches to the default superuser desktop).

So since the wallpapers I used were recently removed, I would like to try things like e.g.

downgrade or repair kde-nobara

Take a look into the desktop config (or whereever the background is set)

Reset some desktop settings

But I am to stupid to do figure out myelf how to do all this. So i asked here :)