[SOLVED] Machine Stuck at Black Background and Mouse Pointer

varolbora5 · 2024-04-26 10:21:38

Hi,
My arch machine is stuck at boot(?), I get this on tty1, tty2 where sddm is supposed to spawn is a black background with a still _ on the left top corner and a mouse pointer I can move around. I can not use any tty either, they all just have a blinking _ cursor on the top left corner with nothing else. I followed advice from another post saying replace dbus-broker-units with dbus-daemon-units and another that said to reinstall packages with altered files with "--dbonly", but those only added the last 4 lines to the picture I linked. Here is the journal from last boot I took from a live usb. http://0x0.st/XHju.txt

Last edited by varolbora5 (2024-05-01 21:03:19)

seth · 2024-04-26 14:41:42

Apr 25 16:50:45 ihateeduroam dbus-daemon[817]: dbus[817]: Unknown username "pulse" in message bus configuration file
Apr 25 16:52:15 ihateeduroam systemd[1]: dbus.service: start operation timed out. Terminating.
Apr 25 16:52:15 ihateeduroam systemd[1]: dbus.service: Failed with result 'timeout'.
…
Apr 25 16:53:47 ihateeduroam sddm-helper[1207]: pam_systemd(sddm-greeter:session): Failed to create session: The name org.freedesktop.login1 was not provided by any .service files

dbus is the problem, but I don't think it's the missing "pulse" user and you're not crashing for dbus-broker as you've replaced that.

sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files'

varolbora5 · 2024-04-26 15:39:09

https://0x0.st/XH_K.txt

seth · 2024-04-26 15:49:18

python-pylspci aside, this looks unsuspicious.

ps aux | grep dbus
systemctl status dbus.service # this might fail
/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only # try to run this as root, do you get any error messages?

varolbora5 · 2024-04-26 16:08:42

https://0x0.st/XH_u.txt
I'm running in chroot so I can't get status and the last commnad doesnt let me upload to 0x0 for some reason so here it is

dbus[32]: Unknown username "pulse" in message bus configuration file

seth · 2024-04-26 16:19:15

I'm running in chroot

Ie. the dbus process there is likely the one from the host, before the chroot.

You're likely able to boot the multi-user.target (2nd link below), log in there and check what's going on.

varolbora5 · 2024-04-26 16:43:46

I can only get a terminal in rescue and can't get internet connection with it, how should I post the outputs?

seth · 2024-04-26 16:45:55

You can't get to the multi-user.target?? (That's still a console)
You'd have to redirect the output into files and upload them later from either a chroot or because you put them on a usb key and moved them to a system w/ internet access.

varolbora5 · 2024-04-26 16:58:35

https://0x0.st/XH_G.txt
https://0x0.st/XH_D.txt
https://0x0.st/XH_k.txt

seth · 2024-04-26 20:02:17

1. no dbus process running
2. still just

Apr 26 18:47:00 ihateeduroam systemd[1]: Starting D-Bus System Message Bus...
Apr 26 18:47:00 ihateeduroam dbus-daemon[823]: dbus[823]: Unknown username "pulse" in message bus configuration file
Apr 26 18:48:30 ihateeduroam systemd[1]: dbus.service: start operation timed out. Terminating.
Apr 26 18:48:30 ihateeduroam systemd[1]: dbus.service: Failed with result 'timeout'.
Apr 26 18:48:30 ihateeduroam systemd[1]: Failed to start D-Bus System Message Bus.

but also

Main PID: 823 (code=exited, status=0/SUCCESS)

3. does the command return immediately (after that message) or do you end up w/ a running dbus process?
4.

pacman -Qikk dbus

varolbora5 · 2024-04-28 08:35:20

No, the command just returns, I don't get a running dbus
https://0x0.st/XHYb.txt

seth · 2024-04-28 15:41:47

So the dbus package is fine, but dbus doesn't start.

Revisiting the journal, there's more amiss.

Apr 25 16:50:42 ihateeduroam systemd-fstab-generator[278]: Failed to create unit file '/run/systemd/generator/-.mount', as it already exists. Duplicate entry in '/etc/fstab'?
Apr 25 16:50:42 ihateeduroam systemd-fstab-generator[278]: Failed to create unit file '/run/systemd/generator/home.mount', as it already exists. Duplicate entry in '/etc/fstab'?
…
Apr 25 16:50:43 ihateeduroam (imesyncd)[513]: systemd-timesyncd.service: Failed to connect stdout to the journal socket, ignoring: Permission denied
…
Apr 25 16:50:45 ihateeduroam systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Apr 25 16:50:45 ihateeduroam systemd[1]: Failed to start Network Time Synchronization.
…
Apr 25 16:50:45 ihateeduroam (imesyncd)[810]: systemd-timesyncd.service: Failed to connect stdout to the journal socket, ignoring: Permission denied
Apr 25 16:50:45 ihateeduroam systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=200/CHDIR
Apr 25 16:50:45 ihateeduroam systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Apr 25 16:50:45 ihateeduroam systemd[1]: Failed to start Network Time Synchronization.
Apr 25 16:50:45 ihateeduroam systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 5.
Apr 25 16:50:45 ihateeduroam systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Apr 25 16:50:45 ihateeduroam systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Apr 25 16:50:45 ihateeduroam systemd[1]: Failed to start Network Time Synchronization.

Did you chown/chmod -R anything?

strace -f -tt -o /tmp/dbus.strace /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only # try to run this as root
cat /tmp/dbus.strace | curl -F 'file=@-' 0x0.st # or upload it by any other means necessary

varolbora5 · 2024-04-28 16:31:03

There was a problem after all this happened where it said /root/ is 700 in filesystem but was supposed to be 750 according to a package, I did a cmod 750 on /root/ but not recursively
the first command also prints out the message about unknown username "pulse"
https://0x0.st/XH6I.txt

Last edited by varolbora5 (2024-04-28 16:35:47)

seth · 2024-04-28 16:43:52

11    18:29:35.906833 close(3)          = 0
11    18:29:35.906864 socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 3
11    18:29:35.906896 connect(3, {sa_family=AF_UNIX, sun_path="/dev/log"}, 110) = -1 ENOENT (No such file or directory)
11    18:29:35.906929 close(3)          = 0
11    18:29:35.907203 exit_group(1)     = ?
11    18:29:35.907358 +++ exited with 1 +++

Exits w/ failure after not able to connect to the journald socket.

pacman -Qikk systemd systemd-libs

varolbora5 · 2024-04-28 16:58:22

https://0x0.st/XH6F.txt

seth · 2024-04-28 17:03:11

packages are intact as well - are you trying this from the rescue or the multi-user.target?

ls -la /dev /run/systemd /run/systemd/journal
mount

varolbora5 · 2024-04-28 17:10:58

its from rescue
https://0x0.st/XHIP.txt
https://0x0.st/XHIZ.txt

seth · 2024-04-28 20:47:35

lrwxrwxrwx  1 root root           28 Apr 28 19:05 log -> /run/systemd/journal/dev-log
srw-rw-rw-  1 root root   0 Apr 28 19:05 dev-log

So how did we arrive at

11    18:29:35.906896 connect(3, {sa_family=AF_UNIX, sun_path="/dev/log"}, 110) = -1 ENOENT (No such file or directory)

Did you run that while being logged in as root?
Same when testing from the multi-user.target?

varolbora5 · 2024-04-29 08:57:01

I can't get any interactivity from multi-user, only from rescue, and it logs in as root on rescue so yeah

seth · 2024-04-30 08:38:18

So, hail-mary.
Re-install systemd and systemd-libs and dbus.
Remove optimus-manager and slimbookbattery (the latter fails in udev, I wonder whether it runs some broken, blocking scripts from a udev rule)
Disable timesyncd, tor and libvirt.

I'd also suggest to enable sshd but there's no ethernet device? Can you utilize https://wiki.archlinux.org/title/Tethering ?

varolbora5 · 2024-04-30 10:10:09

Ok, now I get to a login on multi-user after waiting a couple minutes (time out for dbus to start but it fails twice) I get a login, but when I login it goes black and back to the login

Also I get text next to the login saying device disconnected when I unplug the live usb

Last edited by varolbora5 (2024-04-30 10:11:21)

seth · 2024-04-30 14:37:42

"Live usb"?
You're not booting the installed system??

when I login it goes black and back to the login

There's probably some bad stuff in your shell rc?
Can you login as root?

varolbora5 · 2024-04-30 15:00:08

I can login as root
I'm booting the installed system, but I keep the live usb on hand/plugged in since I need it to do anything with an internet connection.
Also I use zsh with oh-my-zsh and tmux just fyi

seth · 2024-04-30 15:12:08

I can login as root

profit.

Also I use zsh with oh-my-zsh and tmux just fyi

Oh my… zshell.
Please move away all custom shell configs (don't delete them, so we can inspect them afterwards) and see whether
a) you can login again
b) you can maybe properly boot again…

varolbora5 · 2024-04-30 15:29:26

I believe I moved my zsh files away, at least the ones I know of (zshrc, zshenv) but I still can not login to my user

Also there was a text that would appear slightly before screen goes dark after login, so I filmed and caught it, it says

/home/<user>: change directory failed: Permission denied

Last edited by varolbora5 (2024-04-30 15:32:56)

Arch Linux

#1 2024-04-26 10:21:38

[SOLVED] Machine Stuck at Black Background and Mouse Pointer

#2 2024-04-26 14:41:42

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#3 2024-04-26 15:39:09

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#4 2024-04-26 15:49:18

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#5 2024-04-26 16:08:42

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#6 2024-04-26 16:19:15

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#7 2024-04-26 16:43:46

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#8 2024-04-26 16:45:55

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#9 2024-04-26 16:58:35

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#10 2024-04-26 20:02:17

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#11 2024-04-28 08:35:20

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#12 2024-04-28 15:41:47

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#13 2024-04-28 16:31:03

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#14 2024-04-28 16:43:52

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#15 2024-04-28 16:58:22

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#16 2024-04-28 17:03:11

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#17 2024-04-28 17:10:58

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#18 2024-04-28 20:47:35

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#19 2024-04-29 08:57:01

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#20 2024-04-30 08:38:18

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#21 2024-04-30 10:10:09

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#22 2024-04-30 14:37:42

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#23 2024-04-30 15:00:08

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#24 2024-04-30 15:12:08

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

#25 2024-04-30 15:29:26

Re: [SOLVED] Machine Stuck at Black Background and Mouse Pointer

Board footer