[SOLVED]Having several (seemingly) driver-related issues, cant load DE

V1del · 2023-05-18 18:11:19

Because your systemd user bus is broken, how exactly are you starting plasma now? A "proper" terminal based start uses startx and a properly configured .xinitrc https://wiki.archlinux.org/title/Xinit#xinitrc
https://wiki.archlinux.org/title/KDE#From_the_console

Also regarding starting sddm manually, how? You should be using

systemctl start sddm

so systemd/logind integration is set up correctly

Edit: Sorry, seth

Last edited by V1del (2023-05-18 18:15:30)

seth · 2023-05-18 18:12:27

while it required me to start a dbus session first
…
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-sarah'

There's something wrong w/ the session status.

(echo $DBUS_SESSION_BUS_ADDRESS; $loginctl session-status) > /tmp/session_status.txt
cat /tmp/session_status.txt | curl -F 'file=@-' 0x0.st
cat /tmp/session_status.txt | curl -F 'f:1=<-' ix.io # alternatively

And post your current ~/.xinitrc

Edit: curses. Lots of curses.

Last edited by seth (2023-05-18 18:12:43)

queenbiscuit311 · 2023-05-18 18:19:42

Just to see if I could get anything to load at all, I loaded plasma by using the default xinitrc to start xterm, then running plasmashell, then kwin. That's definitely not how you're supposed to do it but it did do something which is what I was trying to achieve.

Also regarding starting sddm manually, how?

I've been starting sddm using systemctl start sddm.

I'll post the .xinitrc I'm using when trying to start plasma directly (not through xterm), as well as the
output of the commands you listed in a bit.

Last edited by queenbiscuit311 (2023-05-18 18:20:33)

queenbiscuit311 · 2023-05-18 19:02:31

Trying to run the command you gave returns the following:

bash: session-status: command not found

I can't find any information on a command with that name, so I must be doing something wrong I imagine. It is typed in correctly, though.

Here's the .xinitrc I was using to try to start plasma properly, although I don't have it active right now: https://pastebin.com/F5CWycYB

I just edited the last portion of the default one to open plasma instead of the stuff the default one opens.

Last edited by queenbiscuit311 (2023-05-18 19:05:02)

seth · 2023-05-18 19:03:52

Sorry, typo

(echo $DBUS_SESSION_BUS_ADDRESS; loginctl session-status) > /tmp/session_status.txt

queenbiscuit311 · 2023-05-18 19:07:47

It's returning

bash: syntax error near unexpected token `echo'

now.

Last edited by queenbiscuit311 (2023-05-18 19:08:33)

seth · 2023-05-18 19:09:45

What?

echo $DBUS_SESSION_BUS_ADDRESS
loginctl session-status

Post the output of those two commands - no matter how.

queenbiscuit311 · 2023-05-18 19:14:22

nvm it works when not doing it with sudo. I just kind of reflexively put it on there without thinking, my apologies. It gives me

unix:path=/tmp/dbus-nRzIhbp0x6,guid=80c42875b0cd315d87ab15556466738f

but it also returns

Could not get properties: Transport endpoint is not connected

in the terminal.

seth · 2023-05-18 19:15:55

What else are you sudo'ing?

ps fax | curl -F 'f:1=<-' ix.io

queenbiscuit311 · 2023-05-18 19:20:42

I don't think I've sudo'd anything I don't have to, I just kinda had a brain fail there.

ps fax returns this: https://pastebin.com/wJiAf5A4

seth · 2023-05-18 19:24:39

There's no sd-pam, nor a systemd --user instance (nor a session daemon)
How do you log into the system?

queenbiscuit311 · 2023-05-18 19:28:07

I just login through the tty using my user credentials. As far as I'm aware, I don't think I've done anything that would disable those processes or anything. Let me relook through the wiki and retrace my steps as to what I did here cause it would appear i messed something up at some point.

Last edited by queenbiscuit311 (2023-05-18 19:28:34)

seth · 2023-05-18 19:32:50

sudo pacman -Qkk $(pacman -Qoq /etc/pam.d/* | sort -u)

queenbiscuit311 · 2023-05-18 19:40:01

Ran the command, here's what it returns: https://pastebin.com/VSghxxN2

The mismatches in sddm Xsetup and sudoers seem to be because I've modified those files.

seth · 2023-05-18 19:47:33

That's fine, the files of interest would reside in /etc/pam.d

Revisiting your journal

May 18 11:35:13 GE76-Raider-Arch systemd-logind[543]: Failed to start user service 'user@1000.service', ignoring: Connection timed out
May 18 11:35:33 GE76-Raider-Arch systemd[1]: dbus.service: start operation timed out. Terminating.
May 18 11:35:33 GE76-Raider-Arch systemd-logind[543]: Failed to start session scope session-1.scope: Connection reset by peer
May 18 11:35:33 GE76-Raider-Arch login[825]: pam_systemd(login:session): Failed to create session: Connection reset by peer
May 18 11:35:33 GE76-Raider-Arch systemd[1]: dbus.service: Failed with result 'timeout'.
May 18 11:35:33 GE76-Raider-Arch systemd[1]: Failed to start D-Bus System Message Bus.
May 18 11:35:33 GE76-Raider-Arch systemd[1]: Reached target Multi-User System.
May 18 11:35:33 GE76-Raider-Arch systemd[1]: Reached target Graphical Interface.
May 18 11:35:33 GE76-Raider-Arch login[825]: LOGIN ON tty1 BY sarah
May 18 11:35:33 GE76-Raider-Arch systemd[1]: Startup finished in 21.109s (firmware) + 4.493s (loader) + 3.293s (kernel) + 1min 32.041s (userspace) = 2min 938ms.
May 18 11:35:44 GE76-Raider-Arch systemd-logind[543]: Failed to stop user service 'user@1000.service', ignoring: Transport endpoint is not connected

Likely because

May 18 11:34:02 GE76-Raider-Arch systemd-tmpfiles[392]: Detected unsafe path transition / (owned by sarah) → /var (owned by root) during canonicalization of var/lib/dbus.
May 18 11:34:02 GE76-Raider-Arch systemd-tmpfiles[392]: Detected unsafe path transition / (owned by sarah) → /run (owned by root) during canonicalization of run/dbus.

"/" is owned by an unprivileged user (you) - fix that.

queenbiscuit311 · 2023-05-18 19:50:05

I did notice several messages like that when doing some pacman commands, but I don't believe they gave that specific information so I didn't know what they were referring to. Could I just use chown or something to fix the permissions for /?

Last edited by queenbiscuit311 (2023-05-18 19:50:51)

queenbiscuit311 · 2023-05-18 20:05:41

Alright I think I fixed the permissions for / after some googling.

queenbiscuit311 · 2023-05-18 20:08:12

Yep, ls -ld / is showing the owner as root and owning group as root as well. I'm not too sure how it became owned by my unprivileged user and that user's group, must've been something I did.

Last edited by queenbiscuit311 (2023-05-18 20:08:39)

queenbiscuit311 · 2023-05-18 20:10:46

That appears to have fixed several things just from rebooting and I'm getting no more service start errors on bootup. Let me see if I can start X properly now.

queenbiscuit311 · 2023-05-18 20:11:27

My ttys 2-6 are also working!

seth · 2023-05-18 20:13:14

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

And out of curiosity:

echo ':)' | curl -F 'file=@-' 0x0.st

queenbiscuit311 · 2023-05-18 20:15:51

And will you look at that, everything works perfectly now. It would appear all I needed to do was login as root, run chown root:root /, and then run chmod 0755 /, which I found on another forum post. Absolutely no idea how that previous permission got set, but thank you so much for all of your help! There's no way I would've figured that out on my own. I'll make sure to mark as solved.

Last edited by queenbiscuit311 (2023-05-18 20:22:29)

queenbiscuit311 · 2023-05-18 20:19:04

And out of curiosity:

Unfortunately still returns bad/illegal format, but hey at least everything else works.

queenbiscuit311 · 2023-05-18 20:20:20

Also whenever I'd login there was this weirdly long wait time before it would actually log in after I entered my password which is also gone now, so it would seem that one problem was the cause of all of my woes.

Arch Linux

#26 2023-05-18 18:11:19

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#27 2023-05-18 18:12:27

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#28 2023-05-18 18:19:42

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#29 2023-05-18 19:02:31

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#30 2023-05-18 19:03:52

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#31 2023-05-18 19:07:47

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#32 2023-05-18 19:09:45

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#33 2023-05-18 19:14:22

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#34 2023-05-18 19:15:55

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#35 2023-05-18 19:20:42

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#36 2023-05-18 19:24:39

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#37 2023-05-18 19:28:07

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#38 2023-05-18 19:32:50

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#39 2023-05-18 19:40:01

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#40 2023-05-18 19:47:33

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#41 2023-05-18 19:50:05

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#42 2023-05-18 20:05:41

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#43 2023-05-18 20:08:12

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#44 2023-05-18 20:10:46

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#45 2023-05-18 20:11:27

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#46 2023-05-18 20:13:14

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#47 2023-05-18 20:15:51

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#48 2023-05-18 20:19:04

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

#49 2023-05-18 20:20:20

Re: [SOLVED]Having several (seemingly) driver-related issues, cant load DE

Board footer