KDE Plasma w/ LightDM - system freezes completely after update

Operating System: EndeavourOS
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.16-zen1-1-zen
OS Type: 64-bit
Graphics Platform: X11
Processors: 8 × AMD FX™-8350 Eight-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: GeForce GT 630/PCIe/SSE2
using KDE Plasma with LightDM

after today’s update my system freezes completely, for the first time after the uddate reboot I was not able to login (keyboard & mouse hungs) then always after about 5 minutes the system freezes.
I had to perform a hard reset, the keyboard and mouse could no longer be moved there was no error screen system just froze, tested w/ both new kernels zen & default

so I have restored the previous system (from above) via timeshift

any idea?

What is the reason you are using lightdm instead of sddm? I have no issues with EndeavourOS Kde Plasma. What drivers are you using for the GT 630?

inxi -Ga

That is a problem I’ve noted with the combo of lightdm and wayland WMs (like sway and plasma_wayland). Just not a good combo (imo), though I like lightdm itself.
And yes, my problem is also keyboard/mouse under those circumstances.
Solution: use SDDM or simply invoke from shell (without a display manager)

I switched to light-dm because of sddm errors (reboot freezes, core dump error)
3 screen setup

inxi -Ga
Graphics:  Device-1: NVIDIA GK208 [GeForce GT 630 Rev. 2] vendor: Palit Microsystems driver: nvidia v: 460.39 
           alternate: nouveau,nvidia_drm bus ID: 01:00.0 chip ID: 10de:1284 class ID: 0300 
           Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: loaded: nvidia display ID: :0 screens: 1 
           Screen-1: 0 s-res: 2881x1668 s-dpi: 84 s-size: 870x504mm (34.3x19.8") s-diag: 1005mm (39.6") 
           Monitor-1: VGA-0 res: 1360x768 hz: 60 dpi: 84 size: 410x230mm (16.1x9.1") diag: 470mm (18.5") 
           Monitor-2: DVI-D-0 res: 1440x900 hz: 60 dpi: 69 size: 530x300mm (20.9x11.8") diag: 609mm (24") 
           Monitor-3: HDMI-0 res: 1440x900 hz: 60 dpi: 69 size: 530x300mm (20.9x11.8") diag: 609mm (24") 
           OpenGL: renderer: GeForce GT 630/PCIe/SSE2 v: 4.6.0 NVIDIA 460.39 direct render: Yes 

it seems to be caused by a kernel issue or the plasma update, I can’t find anything relevant in the log files

Rollback and only update your kernels, if issue doesn’t occur then Plasma is most likely the culprit.

Nvidia driver was updated on 23 Feb, could be that also, depending on when you updated.

With an nvidia driver I presume you are using X11 and not Wayland?

1 Like

yes, I use X11 wayland does not work well with multi screens yet …

For multiple monitors don’t you need an X11 setup script referenced in sddm.conf?

EDIT :

Something like this …

my X11 nvidia.conf is working well for years …

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-0"
    Option  "metamodes" "DVI-D-0: 1440x900 +0+768 {ForceCompositionPipeline=On}, VGA-0: nvidia-auto-select +81+0 {ForceCompositionPipeline=On}, HDMI-0: 1440x900 +1440+768 {ForceCompositionPipeline=On}"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
    Depth       24
    EndSubSection
EndSection

kscreen and grub is also shown in my update list
I will try an update w/o the kernels now

yeah, there seems to be an issue with the new kernel linux-5.11.1 arch and the same with linux-zen-5.11.1 …
I use nvidia-dkms and virtualbox-dkms, when I skip the kernel updates the system does not freeze

1 Like

I do use the nvidia-dkms and never had issues with it but i don’t use dkms on virtualbox.

1 Like

thank you guys, so I will stay w/ linux-5.10.16 and wait for the next release for kernel or v-box

Would be better to additionally install linux-lts kernel alongside your exisiting kernel(s) and boot into that.

linux-lts is already up to 5.10.18, you are already two point releases behind.

Update normally and periodically check future 5.11 point releases.

2 Likes

could it be related to that?

I use CpuPower & TLP (performance / no sleep)

Operating System: EndeavourOS
KDE Plasma Version: 5.21.1
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.19-1-lts
OS Type: 64-bit
Graphics Platform: X11
Processors: 8 × AMD FX™-8350 Eight-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: GeForce GT 630/PCIe/SSE2

The freezing problem persists, it seems the 5.11.1 kernel is not yet stable, so I installed LTS a few days ago and it worked.
after yesterday’s update another kernel problem apparently occurred with 5.10.19-1 and light-dm

[2021-02-28T16:00:57+0100] [ALPM] upgraded vala (0.50.3-1 -> 0.50.4-1)
[2021-02-28T16:00:57+0100] [ALPM] upgraded lvm2 (2.03.11-4 -> 2.03.11-5)
[2021-02-28T16:00:57+0100] [ALPM] upgraded eos-update-notifier (1.13-3 -> 1.13.1-3)
[2021-02-28T16:00:57+0100] [ALPM] upgraded device-mapper (2.03.11-4 -> 2.03.11-5)

if i start the system and the idle state is triggered (after long wait) then the system no longer wakes up
so I switched from light-dm to sddm, so far it works … with sddm it shows following in journal:

Mär 01 09:03:24 mycomputer systemd-coredump[588]: Process 541 (ModemManager) of user 0 dumped core.
                                                 
                                                 Stack trace of thread 541:
                                                 #0  0x00007f7b887c4ef5 raise (libc.so.6 + 0x3cef5)
                                                 #1  0x00007f7b887ae862 abort (libc.so.6 + 0x26862)
                                                 #2  0x00007f7b88a55084 n/a (libglib-2.0.so.0 + 0x1d084)
                                                 #3  0x00007f7b88aafbad g_assertion_message_expr (libglib-2.0.so.0 + 0x77bad)
                                                 #4  0x0000561d96ee3cd2 n/a (ModemManager + 0x48cd2)
                                                 #5  0x0000561d96ee3ec7 n/a (ModemManager + 0x48ec7)
                                                 #6  0x0000561d96ee4248 n/a (ModemManager + 0x49248)
                                                 #7  0x00007f7b88a8bb84 g_main_context_dispatch (libglib-2.0.so.0 + 0x53b84)
                                                 #8  0x00007f7b88adfc21 n/a (libglib-2.0.so.0 + 0xa7c21)
                                                 #9  0x00007f7b88a8b0d3 g_main_loop_run (libglib-2.0.so.0 + 0x530d3)
                                                 #10 0x0000561d96ee032b main (ModemManager + 0x4532b)
                                                 #11 0x00007f7b887afb25 __libc_start_main (libc.so.6 + 0x27b25)
                                                 #12 0x0000561d96ee050e _start (ModemManager + 0x4550e)
                                                 
                                                 Stack trace of thread 546:
                                                 #0  0x00007f7b8887c37f __poll (libc.so.6 + 0xf437f)
                                                 #1  0x00007f7b88adfbaf n/a (libglib-2.0.so.0 + 0xa7baf)
                                                 #2  0x00007f7b88a8a3b1 g_main_context_iteration (libglib-2.0.so.0 + 0x523b1)
                                                 #3  0x00007f7b88a8a402 n/a (libglib-2.0.so.0 + 0x52402)
                                                 #4  0x00007f7b88ab8fc1 n/a (libglib-2.0.so.0 + 0x80fc1)
                                                 #5  0x00007f7b88961299 start_thread (libpthread.so.0 + 0x9299)
                                                 #6  0x00007f7b88887053 __clone (libc.so.6 + 0xff053)
                                                 
                                                 Stack trace of thread 547:
                                                 #0  0x00007f7b88881a9d syscall (libc.so.6 + 0xf9a9d)
                                                 #1  0x00007f7b88ad8c5b g_cond_wait_until (libglib-2.0.so.0 + 0xa0c5b)
                                                 #2  0x00007f7b88a5b923 n/a (libglib-2.0.so.0 + 0x23923)
                                                 #3  0x00007f7b88abbfcb n/a (libglib-2.0.so.0 + 0x83fcb)
                                                 #4  0x00007f7b88ab8fc1 n/a (libglib-2.0.so.0 + 0x80fc1)
                                                 #5  0x00007f7b88961299 start_thread (libpthread.so.0 + 0x9299)
                                                 #6  0x00007f7b88887053 __clone (libc.so.6 + 0xff053)
                                                 
                                                 Stack trace of thread 548:
                                                 #0  0x00007f7b8887c37f __poll (libc.so.6 + 0xf437f)
                                                 #1  0x00007f7b88adfbaf n/a (libglib-2.0.so.0 + 0xa7baf)
                                                 #2  0x00007f7b88a8b0d3 g_main_loop_run (libglib-2.0.so.0 + 0x530d3)
                                                 #3  0x00007f7b88cc9d18 n/a (libgio-2.0.so.0 + 0x101d18)
                                                 #4  0x00007f7b88ab8fc1 n/a (libglib-2.0.so.0 + 0x80fc1)
                                                 #5  0x00007f7b88961299 start_thread (libpthread.so.0 + 0x9299)
                                                 #6  0x00007f7b88887053 __clone (libc.so.6 + 0xff053)

ouh, works again w/ linux-5.11.10 :wink:

1 Like