Arch Linux

aditya12398

Member

From: India

Registered: 2020-02-25

Posts: 13

[SOLVED] Freezes at splash screen, cannot log into the system from GUI

After I boot up the machine and reach the SDDM screen, I enter my password to log in, it proceeds to the splash screen and then gets stuck there. Whenever I try to move my mouse or keyboard the system completely freezes and I am not able to do anything. I am not even able to switch to the TTY screen after that.

I tried not logging from SDDM and switched to the TTY screen but all it has is a blinking cursor. I booted into a live usb and disabled the display manager with `systemctl disable sddm.service` and rebooted the system. I was able to log in perfectly fine after that via the tty screen. No freezes no crashes. I got the journalctl -b-1 output for the failed boot.

There are a few red and orange lines in the journalctl output but I do not think they are responsible for the issue. I am isolating them below anyway. Sorry for the long code section; I just thought I would highlight them.

Here are those lines:

Jun 06 17:14:09 slimshady-desktop kernel: tpm tpm0: AMD fTPM version 0x3005400000005 causes system stutter; hwrng disabled

Jun 06 17:14:09 slimshady-desktop kernel: nvme nvme0: missing or invalid SUBNQN field.

Jun 06 17:14:09 slimshady-desktop kernel: memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL, pid=1 'systemd'

Jun 06 17:14:10 slimshady-desktop (udev-worker)[322]: controlC0: Process '/usr/bin/alsactl restore 0' failed with exit code 2.

Jun 06 17:14:10 slimshady-desktop kernel: kvm_amd: SVM disabled (by BIOS) in MSR_VM_CR on CPU 6

Jun 06 17:14:10 slimshady-desktop (udev-worker)[310]: controlC1: Process '/usr/bin/alsactl restore 1' failed with exit code 2.

Jun 06 17:14:10 slimshady-desktop kernel: nvidia: loading out-of-tree module taints kernel.
Jun 06 17:14:10 slimshady-desktop kernel: nvidia: module license 'NVIDIA' taints kernel.
Jun 06 17:14:10 slimshady-desktop kernel: Disabling lock debugging due to kernel taint

Jun 06 17:14:11 slimshady-desktop kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  530.41.03  Thu Mar 16 19:48:20 UTC 2023
Jun 06 17:14:11 slimshady-desktop (udev-worker)[327]: nvidia: Process '/usr/bin/bash -c '/usr/bin/mknod -Z -m 666 /dev/nvidiactl c $(grep nvidia-frontend /proc/devices | cut -d \  -f 1) 255'' failed with exit code 1.
Jun 06 17:14:11 slimshady-desktop (udev-worker)[327]: nvidia: Process '/usr/bin/bash -c 'for i in $(cat /proc/driver/nvidia/gpus/*/information | grep Minor | cut -d \  -f 4); do /usr/bin/mknod -Z -m 666 /dev/nvidia${i} c $(grep nvidia-frontend /proc/devices | cut -d \  -f 1) ${i}; done'' failed with exit code 1.
Jun 06 17:14:11 slimshady-desktop kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.

Jun 06 17:14:11 slimshady-desktop kernel: nvidia-gpu 0000:07:00.3: i2c timeout error e0000000
Jun 06 17:14:11 slimshady-desktop kernel: ucsi_ccg 3-0008: i2c_transfer failed -110
Jun 06 17:14:11 slimshady-desktop kernel: ucsi_ccg 3-0008: ucsi_ccg_init failed - -110
Jun 06 17:14:11 slimshady-desktop kernel: ucsi_ccg: probe of 3-0008 failed with error -110

Jun 06 17:14:11 slimshady-desktop systemd-sysctl[471]: Couldn't write '0' | sudo tee -a /etc/sysctl.d/99-sysctl.conf' to 'echo 'kernel/dmesg_restrict', ignoring: No such file or directory

Jun 06 17:14:14 slimshady-desktop sddm-greeter[538]: QFont::fromString: Invalid description '(empty)'
Jun 06 17:14:14 slimshady-desktop sddm[509]: Message received from greeter: Connect
Jun 06 17:14:14 slimshady-desktop sddm-greeter[538]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
Jun 06 17:14:14 slimshady-desktop sddm-greeter[538]: QObject: Cannot create children for a parent that is in a different thread.
                                                     (Parent is QGuiApplication(0x7ffc4dff75c0), parent's thread is QThread(0x559419737a30), current thread is QThread(0x5594198055a0)
Jun 06 17:14:14 slimshady-desktop sddm-greeter[538]: QObject: Cannot create children for a parent that is in a different thread.
                                                     (Parent is QGuiApplication(0x7ffc4dff75c0), parent's thread is QThread(0x559419737a30), current thread is QThread(0x5594198055a0)
Jun 06 17:14:14 slimshady-desktop sddm-greeter[538]: QObject: Cannot create children for a parent that is in a different thread.
                                                     (Parent is QGuiApplication(0x7ffc4dff75c0), parent's thread is QThread(0x559419737a30), current thread is QThread(0x5594198055a0)
Jun 06 17:14:14 slimshady-desktop sddm-greeter[538]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.

Jun 06 17:14:14 slimshady-desktop sddm-greeter[538]: Failed to find a Kirigami platform plugin
Jun 06 17:14:14 slimshady-desktop sddm-greeter[538]: file:///usr/share/sddm/themes/breeze/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed
Jun 06 17:14:14 slimshady-desktop sddm-greeter[538]: Adding view for "HDMI-0" QRect(0,0 1920x1080)
Jun 06 17:14:14 slimshady-desktop udisksd[546]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Jun 06 17:14:14 slimshady-desktop sddm-greeter[538]: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.17'
Jun 06 17:14:14 slimshady-desktop sddm-greeter[538]: QDBusConnection: name 'org.freedesktop.UPower' had owner '' but we thought it was ':1.18'
Jun 06 17:14:14 slimshady-desktop sddm-greeter[538]: Message received from daemon: Capabilities

What could be wrong and how can I resolve this?

System information:

Kernel: 6.3.6.arch1-1
Nvidia Driver Version: 530.41.03-16
CPU: AMD Ryzen 5 3600
DE/WM: KDE Plasma/SDDM

Please let me know if any information is missing and what else I can provide to help.

Last edited by aditya12398 (2023-06-12 07:57:18)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,379

Re: [SOLVED] Freezes at splash screen, cannot log into the system from GUI

The journal you posted seems to only cover the system services, please post one that also contains the user session because it sounds like you are crashing/freezing in plasma somewhere. Can you reproduce this on a fresh user profile? If that however is the complete journal reads like PAM issues with unmerged pacnews and an issue with the homed service, see e.g.: https://bbs.archlinux.org/viewtopic.php?id=285634 and check for  (and merge) pacnew files in /etc/pam.d

Last edited by V1del (2023-06-07 11:13:37)

aditya12398

Member

From: India

Registered: 2020-02-25

Posts: 13

Re: [SOLVED] Freezes at splash screen, cannot log into the system from GUI

Hi V1del, thanks a ton for your reply!

I tried a few things and it seems like this problem does not occur on a fresh user. I just logged into the tty screen and added a new guest user to check. Rebooted, logged in with the new user and it started right away.

I also tried to get the user-journal by doing a `journalctl -b-1 --user` but somehow it has no entries for the user for the failed login, only for the tty login before that. I only get the journal output I posted last time. I know almost nothing about how this works so this may sound stupid: Could it be because I hard-shutdown the machine from the button that the journal does not get saved?

I had also ssh'ed into the machine from my phone while I was trying to login to see if I can shut it down from my another machine's terminal but as soon as I logged in even the ssh'ed terminal stopped responding. My keyboard and mouse were running and responding but the same problem with the tty screen (blinking cursor, no login prompt) and getting stuck at splash screen problem occured.

I have a few packages auto-starting at the beginning of a user-session, could they be causing this as well?

Lastly, a conceptual question: If it was a PAM issue wouldn't it occur also for the new user?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,379

Re: [SOLVED] Freezes at splash screen, cannot log into the system from GUI

It should occur for the new user as well if it was PAM, unless it's e.g. the kwallet service failing because you changed your password or similar and the PAM config being set to fail when unlocking the keyring fails. Which exact packages/tools are you autostarting and how exactly? If something fails early in the session startup and is wired in a way that it will prevent the rest of the session coming up that could explain this.

Last edited by V1del (2023-06-07 20:03:18)

aditya12398

Member

From: India

Registered: 2020-02-25

Posts: 13

Re: [SOLVED] Freezes at splash screen, cannot log into the system from GUI

Mailspring, dropbox, and discord. That's about it I think except the default ones that the system starts.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,379

Re: [SOLVED] Freezes at splash screen, cannot log into the system from GUI

broken custom shell configs or so? If you run into an invalid state/constellation with your login shell rc files or similar that can have quite far reaching effects.

Last edited by V1del (2023-06-08 10:54:43)

aditya12398

Member

From: India

Registered: 2020-02-25

Posts: 13

Re: [SOLVED] Freezes at splash screen, cannot log into the system from GUI

I don't think I have any custom login shell files other than a couple of files I source in bashrc (they only edit the PATH and similar such variables). But nothing has changed thus far so I am assuming that is not an issue.

Buuuutttt I found something and that is progress I guess...

I removed all three startup *.desktop files from ~/.config/autostart and the system logged in immediately. But then as soon as I started dolphin it froze again and I was not able to access the TTY screen either. I then tried to start dolphin from terminal at the next boot with the same problem, again, to no avail.

I thought something got messed up in some config file somewhere so I moved the entire .config and .cache over to a backup folder and tried it again. Same issue. Shall I regenerate the .Xauthority file? If yes how do I do it? What else could be the problem? This is making me crazy!

Edit: Oh btw none of this is happening in the guest user. I am comfortably using that user account to give updates on this post

Last edited by aditya12398 (2023-06-08 15:57:57)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,379

Re: [SOLVED] Freezes at splash screen, cannot log into the system from GUI

From the working/logged in state post

printenv
loginctl session-status

Last edited by V1del (2023-06-08 16:02:56)

aditya12398

Member

From: India

Registered: 2020-02-25

Posts: 13

Re: [SOLVED] Freezes at splash screen, cannot log into the system from GUI

printenv:

[guest@slimshady-desktop ~]$ printenv
SHELL=/bin/bash
WINDOWID=50331658
COLORTERM=truecolor
XDG_CONFIG_DIRS=/home/guest/.config/kdedefaults:/etc/xdg
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session2
LANGUAGE=
SHELL_SESSION_ID=b4ad4beec4ae4122be82de787a6105a6
DESKTOP_SESSION=plasma
GTK_RC_FILES=/etc/gtk/gtkrc:/home/guest/.gtkrc:/home/guest/.config/gtkrc
XCURSOR_SIZE=24
GTK_MODULES=canberra-gtk-module
XDG_SEAT=seat0
PWD=/home/guest
XDG_SESSION_DESKTOP=KDE
LOGNAME=guest
XDG_SESSION_TYPE=x11
SYSTEMD_EXEC_PID=865
XAUTHORITY=/home/guest/.Xauthority
MOTD_SHOWN=pam
GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/guest/.gtkrc-2.0:/home/guest/.config/gtkrc-2.0
HOME=/home/guest
LANG=en_US.UTF-8
XDG_CURRENT_DESKTOP=KDE
KONSOLE_DBUS_SERVICE=:1.52
KONSOLE_DBUS_SESSION=/Sessions/1
PROFILEHOME=
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
INVOCATION_ID=0947187d2a7c40eda620e2fe8ed6d8b5
KONSOLE_VERSION=230401
MANAGERPID=785
KDE_SESSION_UID=1001
XDG_SESSION_CLASS=user
TERM=xterm-256color
USER=guest
COLORFGBG=15;0
KDE_SESSION_VERSION=5
PAM_KWALLET5_LOGIN=/run/user/1001/kwallet5.socket
DISPLAY=:0
SHLVL=1
XDG_VTNR=1
XDG_SESSION_ID=2
XDG_RUNTIME_DIR=/run/user/1001
DEBUGINFOD_URLS=https://debuginfod.archlinux.org
QT_AUTO_SCREEN_SCALE_FACTOR=0
JOURNAL_STREAM=8:20615
XCURSOR_THEME=breeze_cursors
KDE_FULL_SESSION=true
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus
KDE_APPLICATIONS_AS_SCOPE=1
MAIL=/var/spool/mail/guest
KONSOLE_DBUS_WINDOW=/Windows/1
_=/usr/bin/printenv

loginctl session-status:

[guest@slimshady-desktop ~]$ loginctl session-status
2 - guest (1001)
           Since: Thu 2023-06-08 21:17:57 IST; 21min ago
          Leader: 783 (sddm-helper)
            Seat: seat0; vc1
         Display: :0
         Service: sddm; type x11; class user
         Desktop: KDE
           State: active
            Unit: session-2.scope
                  ├─783 /usr/lib/sddm/sddm-helper --socket /tmp/sddm-auth521e8be0-6746-45b1-a32f-3bd738128a5b --id 1 --start /usr/bin/startplasma-x11 --user guest
                  ├─798 /usr/bin/kwalletd5 --pam-login 6 8
                  └─799 /usr/bin/startplasma-x11

Jun 08 21:17:57 slimshady-desktop sddm-helper[797]: pam_kwallet5: final socket path: /run/user/1001/kwallet5.socket
Jun 08 21:17:57 slimshady-desktop sddm-helper[799]: Adding cookie to "/home/guest/.Xauthority"

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,379

Re: [SOLVED] Freezes at splash screen, cannot log into the system from GUI

Is that the new, working user? These are more interesting from the user that's failing. I interpreted the message so that you're able to login but then it crashes when trying to open dolphin, can you open a terminal there? Does the journal contain more telling information now?

sudo journalctl -b

?

aditya12398

Member

From: India

Registered: 2020-02-25

Posts: 13

Re: [SOLVED] Freezes at splash screen, cannot log into the system from GUI

Okay I somehow got the journalctl output. And now this problem is happening even in the guest user so I am starting to think maybe has my drive crashed or something?

How can I check? I am in a Garuda Linux Live USB at the moment...

Here is the journalctl output

Edit: I forgot to mention, there is a powercut issue that happened a few days ago. Could that and the hard-reboot thing have caused the drive damage?

Last edited by aditya12398 (2023-06-08 16:48:59)

aditya12398

Member

From: India

Registered: 2020-02-25

Posts: 13

Re: [SOLVED] Freezes at splash screen, cannot log into the system from GUI

So I solved the problem. It was a hardware issue, related to the drive, that I found out about only after I was trying to reinstall the OS and overwrite the entire drive with zeros. Probably triggered by the powercut. I took apart the system and reconnected it after checking all hardware and reinstalled arch from scratch. It is now working flawlessly.

Thanks a lot for your help, I am now marking this post as solved.