[Solved] "[OK] Reached target Graphical Interface" after login before getting booted back to the login screen
from lordgoose@lemmy.dbzer0.com to linux@lemmy.ml on 26 Jun 00:43
https://lemmy.dbzer0.com/post/47619883

Hey all, semi-novice Linux user here.

I’m running EndeavourOS with KDE on a Lenovo with an Intel CPU and integrated GPU.

I was attempting to update my system today but kept getting the error referenced in this newsletter that I found after looking for the error online. I ran each command in the newsletter exactly as written and then rebooted my system.

After rebooting, I’m able to successfully get to the login screen and input my username/password but, instead of my desktop, logging in takes me to a command interface for about a second before reverting to the same login screen. The line in the title is the last entry shown in that command interface.

I’ve looked online for solutions but it doesn’t seem like anyone with my same error is getting stuck on the login screen (most people seem to be stuck on Grub and are able to use e, ctrl+alt-F2, etc) and I’m just sorta lost on what to do at this point.

Any help is appreciated. Thanks!

Edit: Thank you to MyNameIsRichard for your help. It turns out that I needed to install plasma-x11-session as I am still an x11 user and a recent update made it necessary to install this package manually.

#linux

threaded - newest

catloaf@lemm.ee on 26 Jun 00:50 next collapse

You’ll need to check the logs for your display manager, probably kdm if you’re using KDE.

unperson@hexbear.net on 26 Jun 00:53 next collapse

The problem is probably unrelated to the firmware, and caused by some other upgrade.

After experiencing the issue, you should be able to switch to a different tty with ctrl-alt-f6 (or any other f key), log in, and check journalctl -b for an error message. Edit: Use the End key or shift-G to scroll to the end of the journal.

lordgoose@lemmy.dbzer0.com on 26 Jun 01:29 collapse

Successfully made it to a different tty with ctrl-alt-F5 and was able to run journalctl -b

I’m not entirely sure what error I’m looking for here in particular so I’m taking a guess that “Activation request for ‘org.freedesktop.XYZ’ failed: The systemd unit ‘dbus-org.freedesktop.XYZ.service’ could not be found.” is the one I’m looking for (XYZ because there are a few of these such errors with just the XYZ changing between them).

Is this the same error you got?

Mordikan@kbin.earth on 26 Jun 02:06 collapse

Are you sure linux-firmware was the only thing uninstalled? What are those XYZ's? you might just need to reinstall those items.

lordgoose@lemmy.dbzer0.com on 26 Jun 02:16 collapse

Looks like those XYZs ended up being irrelevant to my situation (figured as much seeing as looking online didn’t give me much information).

I needed to reinstall plasma-x11-session per a recent update since I still use x11.

just_another_person@lemmy.world on 26 Jun 01:25 next collapse

Probably a permissions issue somewhere. Logs will be needed.

MyNameIsRichard@lemmy.ml on 26 Jun 01:38 collapse

What does pacman -Qs linux-firmware show?

lordgoose@lemmy.dbzer0.com on 26 Jun 01:47 collapse

(Sorry for image quality) this is what I’ve got: <img alt="" src="https://lemmy.dbzer0.com/pictrs/image/c267833e-357a-43f4-bb21-078af6189b4d.webp">

MyNameIsRichard@lemmy.ml on 26 Jun 02:00 collapse

I was hoping you had f-6 which was causing all sorts of problems for amd and intel users but you have f-9 which purports to fix them all. The next question is are you using Plasma with X11? If you are, the have a look at archlinux.org/…/plasma-640-will-need-manual-inter…

lordgoose@lemmy.dbzer0.com on 26 Jun 02:03 collapse

I am indeed using X11. I tried using Wayland ~a few months ago (on one or both of my setups, wish I could remember) and it did not work very nicely for me so I just stuck with X11, which so far has worked perfectly for what I do.

MyNameIsRichard@lemmy.ml on 26 Jun 02:06 collapse

Yeah, you will need to install the X11 session as detailed in the news page I linked. To summarise sudo pacman -Syu plasma-x11-session

lordgoose@lemmy.dbzer0.com on 26 Jun 02:14 collapse

It’s fixed!! Thank you so much!

Side note: also going to subscribe to the Arch newsletter to avoid mishaps like this in the future.

MyNameIsRichard@lemmy.ml on 26 Jun 02:16 collapse

No Probs. I’m happy to help.