You are not logged in.

#1 2024-05-30 15:03:54

adrit1234
Member
Registered: 2023-06-21
Posts: 18

[SOLVED]GUI non functional after failed system update

After yet another kernel panic during a system update today, my GUI has stopped working entirely. First, the system gets stuck in the kernel boot screen and lightdm wouldn't appear, although I could still login via tty.
I fixed this by removing all of the corrupted lightdm files and reinstalling them. So now my lightdm works as normal, but whenever I login to my cinnamon DE, all that shows up is a black screen(no panel, no background, plank and conky are frozen, etc) although the cursor still does work. Checking the logs from previous boot do appear to show a coredump of caribou and some kernel taint related to nvidia:

May 30 21:15:58 archlinux kernel: Linux version 6.9.2-arch1-1 (linux@archlinux) (gcc (GCC) 14.1.1 20240522, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Sun, 26 May 2024 01:30:29 +0000
May 30 21:15:58 archlinux kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=c871e94e-0199-4439-be0f-e0daa1eee2b4 rw rootfstype=ext4 loglevel=3 quiet
May 30 21:15:58 archlinux kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
...
May 30 21:15:59 archlinux kernel: nvidia: loading out-of-tree module taints kernel.
May 30 21:15:59 archlinux kernel: nvidia: module license 'NVIDIA' taints kernel.
May 30 21:15:59 archlinux kernel: Disabling lock debugging due to kernel taint
May 30 21:15:59 archlinux kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
May 30 21:15:59 archlinux kernel: nvidia: module license taints kernel.
...
May 30 21:15:58 archlinux kernel: sgx: There are zero EPC sections.
May 30 21:15:59 archlinux kernel: 
May 30 21:16:01 archlinux libvirtd[758]: Cannot find 'dmidecode' in path: No such file or directory
May 30 21:16:01 archlinux libvirtd[758]: Cannot find 'dmidecode' in path: No such file or directory
May 30 21:16:16 archlinux lightdm[1119]: gkr-pam: unable to locate daemon control file
May 30 21:16:18 archlinux systemd-coredump[1481]: [?] Process 1392 (caribou) of user 1000 dumped core.
                                                  
                                                  Stack trace of thread 1392:
                                                  #0  0x0000749a395afad8 g_log_structured_array (libglib-2.0.so.0 + 0x61ad8)
                                                  #1  0x0000749a395afdd7 g_log_default_handler (libglib-2.0.so.0 + 0x61dd7)
                                                  #2  0x0000749a395b005c g_logv (libglib-2.0.so.0 + 0x6205c)
                                                  #3  0x0000749a395b03d4 g_log (libglib-2.0.so.0 + 0x623d4)
                                                  #4  0x00005c67430393ba n/a (caribou + 0x53ba)
                                                  #5  0x0000749a3987a0ec n/a (libgio-2.0.so.0 + 0xa60ec)
                                                  #6  0x0000749a3987e385 n/a (libgio-2.0.so.0 + 0xaa385)
                                                  #7  0x0000749a398ec48d n/a (libgio-2.0.so.0 + 0x11848d)
                                                  #8  0x0000749a3987a0ec n/a (libgio-2.0.so.0 + 0xa60ec)
                                                  #9  0x0000749a3987e385 n/a (libgio-2.0.so.0 + 0xaa385)
                                                  #10 0x0000749a398ebf27 n/a (libgio-2.0.so.0 + 0x117f27)
                                                  #11 0x0000749a3987a0ec n/a (libgio-2.0.so.0 + 0xa60ec)
                                                  #12 0x0000749a3987e385 n/a (libgio-2.0.so.0 + 0xaa385)
                                                  #13 0x0000749a398db948 n/a (libgio-2.0.so.0 + 0x107948)
                                                  #14 0x0000749a3987a0ec n/a (libgio-2.0.so.0 + 0xa60ec)
                                                  #15 0x0000749a3987a135 n/a (libgio-2.0.so.0 + 0xa6135)
                                                  #16 0x0000749a395aaa89 n/a (libglib-2.0.so.0 + 0x5ca89)
                                                  #17 0x0000749a3960c9b7 n/a (libglib-2.0.so.0 + 0xbe9b7)
                                                  #18 0x0000749a395ab787 g_main_loop_run (libglib-2.0.so.0 + 0x5d787)
                                                  #19 0x0000749a396ad3d2 atspi_event_main (libatspi.so.0 + 0x113d2)
                                                  #20 0x00005c674303721a n/a (caribou + 0x321a)
                                                  #21 0x0000749a39385c88 n/a (libc.so.6 + 0x25c88)
                                                  #22 0x0000749a39385d4c __libc_start_main (libc.so.6 + 0x25d4c)
                                                  #23 0x00005c6743037335 n/a (caribou + 0x3335)
                                                  
                                                  Stack trace of thread 1395:
                                                  #0  0x0000749a39473e9d syscall (libc.so.6 + 0x113e9d)
                                                  #1  0x0000749a396059e0 g_cond_wait (libglib-2.0.so.0 + 0xb79e0)
                                                  #2  0x0000749a395738dc n/a (libglib-2.0.so.0 + 0x258dc)
                                                  #3  0x0000749a395df687 n/a (libglib-2.0.so.0 + 0x91687)
                                                  #4  0x0000749a395da236 n/a (libglib-2.0.so.0 + 0x8c236)
                                                  #5  0x0000749a393f2ded n/a (libc.so.6 + 0x92ded)
                                                  #6  0x0000749a394760dc n/a (libc.so.6 + 0x1160dc)
                                                  
                                                  Stack trace of thread 1400:
                                                  #0  0x0000749a3946839d __poll (libc.so.6 + 0x10839d)
                                                  #1  0x0000749a3960c8fd n/a (libglib-2.0.so.0 + 0xbe8fd)
                                                  #2  0x0000749a395ab787 g_main_loop_run (libglib-2.0.so.0 + 0x5d787)
                                                  #3  0x0000749a398e64b4 n/a (libgio-2.0.so.0 + 0x1124b4)
                                                  #4  0x0000749a395da236 n/a (libglib-2.0.so.0 + 0x8c236)
                                                  #5  0x0000749a393f2ded n/a (libc.so.6 + 0x92ded)
                                                  #6  0x0000749a394760dc n/a (libc.so.6 + 0x1160dc)
                                                  
                                                  Stack trace of thread 1398:
                                                  #0  0x0000749a39473e9d syscall (libc.so.6 + 0x113e9d)
                                                  #1  0x0000749a39606337 g_cond_wait_until (libglib-2.0.so.0 + 0xb8337)
                                                  #2  0x0000749a395738a5 n/a (libglib-2.0.so.0 + 0x258a5)
                                                  #3  0x0000749a395e024b n/a (libglib-2.0.so.0 + 0x9224b)
                                                  #4  0x0000749a395da236 n/a (libglib-2.0.so.0 + 0x8c236)
                                                  #5  0x0000749a393f2ded n/a (libc.so.6 + 0x92ded)
                                                  #6  0x0000749a394760dc n/a (libc.so.6 + 0x1160dc)
                                                  
                                                  Stack trace of thread 1396:
                                                  #0  0x0000749a3946839d __poll (libc.so.6 + 0x10839d)
                                                  #1  0x0000749a3960c8fd n/a (libglib-2.0.so.0 + 0xbe8fd)
                                                  #2  0x0000749a395a9f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
                                                  #3  0x0000749a395a9fea n/a (libglib-2.0.so.0 + 0x5bfea)
                                                  #4  0x0000749a395da236 n/a (libglib-2.0.so.0 + 0x8c236)
                                                  #5  0x0000749a393f2ded n/a (libc.so.6 + 0x92ded)
                                                  #6  0x0000749a394760dc n/a (libc.so.6 + 0x1160dc)
                                                  
                                                  Stack trace of thread 1397:
                                                  #0  0x0000749a39473e9d syscall (libc.so.6 + 0x113e9d)
                                                  #1  0x0000749a39606337 g_cond_wait_until (libglib-2.0.so.0 + 0xb8337)
                                                  #2  0x0000749a395738a5 n/a (libglib-2.0.so.0 + 0x258a5)
                                                  #3  0x0000749a395e024b n/a (libglib-2.0.so.0 + 0x9224b)
                                                  #4  0x0000749a395da236 n/a (libglib-2.0.so.0 + 0x8c236)
                                                  #5  0x0000749a393f2ded n/a (libc.so.6 + 0x92ded)
                                                  #6  0x0000749a394760dc n/a (libc.so.6 + 0x1160dc)
                                                  ELF object binary architecture: AMD x86-64

I couldn't find much information about my issues so I'm not sure what's happening or which log messages are useful here. Any help would be greatly appreciated.

Last edited by adrit1234 (2024-05-31 15:01:11)

Offline

#2 2024-05-30 16:47:57

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 22,169

Re: [SOLVED]GUI non functional after failed system update

You need to check whether the update hasn't left your system in a borked state

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

reinstall everything comming up here as lacking mtree information with pacmans --dbonly flag followed by a reinstall of all of them without that flag (as well as things comming up with corrupted or changed files, though some can be normal here). Post the output you get from that command in doubt.

The current nvidia drivers have come up with some issues in the current version where they leave the kernel memory in a corrupted state that can trigger a panic when systemd tries to reinit on update. Consider installing https://aur.archlinux.org/packages/nvidia-535xx-dkms instead for the interim.

Last edited by V1del (2024-05-30 16:48:46)

Offline

#3 2024-05-30 17:27:30

adrit1234
Member
Registered: 2023-06-21
Posts: 18

Re: [SOLVED]GUI non functional after failed system update

I found and reinstalled all the packages missing mtree files with the --dbonly flag and then without like you said and got everything back to normal now. And yes, I've been noticing my system having lots of kernel panics lately(sometimes during updates, like today and other times when I'm shutting down, especially if I have the system on for a long time). I didn't know it was due to the nvidia driver. Do I uninstall it for now and download the one from the AUR? The kernel panics are getting quite bothersome now and I want to avoid them to prevent headaches like this.

Last edited by adrit1234 (2024-05-30 17:43:17)

Offline

#4 2024-05-30 19:25:36

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 22,169

Re: [SOLVED]GUI non functional after failed system update

adrit1234 wrote:

Do I uninstall it for now and download the one from the AUR?

You don't need to explicitly uninstall (and doing so might take some other deps with it unless you use the -Rdd flag) you can just "install" the replacement packages in one go that should prompt for the appropriate replacements getting done. Note that for DKMS based packages to work properly you need to install the linux-headers package of the kernel you're using.

Offline

#5 2024-05-31 15:00:55

adrit1234
Member
Registered: 2023-06-21
Posts: 18

Re: [SOLVED]GUI non functional after failed system update

Ahh I see. I'll try that maybe and see if the kernel panics finally stop. Thank you!

Offline

Board footer

Powered by FluxBB