You are not logged in.

#1 2020-07-21 16:56:43

DFOwl
Member
Registered: 2020-07-21
Posts: 52

KDE on Arch crashes after second suspension

Hello everyone. A few weeks ago, after an Arch and KDE update (I didn't write down which, sorry), my system began crashing after the second time it wakes up from suspension. The deal is this: after going to sleep the second time, instead of getting a password prompt, I get a black screen with a mouse on it. I can move the mouse, but I cannot start any application. I should probably mention that this problem also occurs after logging in and out of KDE.

I am able to fully interact with all of the TTY's (Ctrl + Alt + F2/F3/F...). I have attempted to killall plasmashell and then kstart5 plasmashell, only to get an error:

qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem
...
[1] 1-368 abort (core dumped) plasmashell

Afterwards I attempted to killall Xorg, which reset all of my graphics and somehow was able to put me back into KDE, although my session was completely wiped. I should note that this does not always work, as sometimes I just get a spinning KDE logo spinning there forever.

These are the few last lines in my dmesg log:

[  220.636825] PM: suspend entry (deep)
[  220.685158] Filesystems sync: 0.048 seconds
[  220.987028] snd_hdac_bus_update_rirb: 168 callbacks suppressed
[  220.987032] snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x1f0500
[  220.987067] snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x4f0015
[  220.987109] snd_hda_intel 0000:01:00.1: spurious response 0x3:0x0, last cmd=0x473500
[  220.987151] snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x470700
[  220.987191] snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x4f0015
[  220.987233] snd_hda_intel 0000:01:00.1: spurious response 0x3:0x0, last cmd=0x473501
[  220.987275] snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x470700
[  220.987316] snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x4f0015
[  220.987358] snd_hda_intel 0000:01:00.1: spurious response 0x3:0x0, last cmd=0x473502
[  220.987401] snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x470700
[  221.110493] Freezing user space processes ... (elapsed 0.002 seconds) done.
[  221.112513] OOM killer disabled.
[  221.112514] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[  221.113796] printk: Suspending console(s) (use no_console_suspend to debug)
[  221.148447] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  221.148542] sd 0:0:0:0: [sda] Stopping disk
[  221.357709] ACPI: Preparing to enter system sleep state S3
[  221.771028] PM: Saving platform NVS memory
[  221.771045] Disabling non-boot CPUs ...
[  221.772732] smpboot: CPU 1 is now offline
[  221.777073] smpboot: CPU 2 is now offline
[  221.780380] smpboot: CPU 3 is now offline
[  221.783077] ACPI: Low-level resume complete
[  221.783122] PM: Restoring platform NVS memory
[  221.785257] Enabling non-boot CPUs ...
[  221.785301] x86: Booting SMP configuration:
[  221.785302] smpboot: Booting Node 0 Processor 1 APIC 0x2
[  221.786912] CPU1 is up
[  221.786942] smpboot: Booting Node 0 Processor 2 APIC 0x1
[  221.787472] CPU2 is up
[  221.787498] smpboot: Booting Node 0 Processor 3 APIC 0x3
[  221.788075] CPU3 is up
[  221.790321] ACPI: Waking up from system sleep state S3
[  221.832009] sd 0:0:0:0: [sda] Starting disk
[  222.139630] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  222.139916] ata1.00: supports DRM functions and may not be fully accessible
[  222.140917] ata1.00: NCQ Send/Recv Log not supported
[  222.142067] ata1.00: supports DRM functions and may not be fully accessible
[  222.142434] ata1.00: NCQ Send/Recv Log not supported
[  222.143326] ata1.00: configured for UDMA/133
[  222.248752] MAC Address = 34:e8:94:e2:c2:72
[  222.250310] OOM killer enabled.
[  222.250311] Restarting tasks ... 
[  222.250496] pci_bus 0000:04: Allocating resources
[  222.250508] pci 0000:03:00.0: PCI bridge to [bus 04]
[  222.250514] pci 0000:03:00.0:   bridge window [io  0x3000-0x3fff]
[  222.250525] pci 0000:03:00.0:   bridge window [mem 0xf3700000-0xf38fffff]
[  222.250532] pci 0000:03:00.0:   bridge window [mem 0xf3900000-0xf3afffff 64bit pref]
[  222.262790] done.
[  222.262831] PM: suspend exit
[  223.406510] R8188EU: indicate disassoc
[  227.218097] R8188EU: assoc success
[  227.270752] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  229.008524] kauditd_printk_skb: 76 callbacks suppressed
[  229.008526] audit: type=1131 audit(1595341484.223:109): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  230.411792] snd_hdac_bus_update_rirb: 212 callbacks suppressed
[  230.411796] snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x1f0500
[  230.411832] snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x4f0015
[  230.411874] snd_hda_intel 0000:01:00.1: spurious response 0x3:0x0, last cmd=0x473500
[  230.411914] snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x470700
[  230.411957] snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x4f0015
[  230.411998] snd_hda_intel 0000:01:00.1: spurious response 0x3:0x0, last cmd=0x473501
[  230.412040] snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x470700
[  230.412081] snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x4f0015
[  230.412123] snd_hda_intel 0000:01:00.1: spurious response 0x3:0x0, last cmd=0x473502
[  230.412166] snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x470700
[  230.536335] audit: type=1130 audit(1595341485.750:110): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  236.893959] audit: type=1130 audit(1595341492.106:111): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  239.907320] audit: type=1100 audit(1595341495.120:112): pid=1970 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="dfowl" exe="/usr/bin/login" hostname=OwlArchPC addr=? terminal=tty2 res=failed'
[  247.015113] audit: type=1131 audit(1595341502.230:113): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  252.503823] audit: type=1100 audit(1595341507.716:114): pid=1970 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="dfowl" exe="/usr/bin/login" hostname=OwlArchPC addr=? terminal=tty2 res=success'
[  252.507514] audit: type=1101 audit(1595341507.720:115): pid=1970 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix,pam_permit,pam_time acct="dfowl" exe="/usr/bin/login" hostname=OwlArchPC addr=? terminal=tty2 res=success'
[  252.508110] audit: type=1103 audit(1595341507.720:116): pid=1970 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="dfowl" exe="/usr/bin/login" hostname=OwlArchPC addr=? terminal=tty2 res=success'
[  252.508158] audit: type=1006 audit(1595341507.720:117): pid=1970 uid=0 old-auid=4294967295 auid=1000 tty=tty2 old-ses=4294967295 ses=4 res=1
[  252.508160] audit: type=1300 audit(1595341507.720:117): arch=c000003e syscall=1 success=yes exit=4 a0=4 a1=7ffe0165cd90 a2=4 a3=7ffe0165caa4 items=0 ppid=1 pid=1970 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty2 ses=4 comm="login" exe="/usr/bin/login" key=(null)
[  252.508166] audit: type=1327 audit(1595341507.720:117): proctitle=2F62696E2F6C6F67696E002D70002D2D002020202020
[  252.519222] audit: type=1105 audit(1595341507.733:118): pid=1970 uid=0 auid=1000 ses=4 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="dfowl" exe="/usr/bin/login" hostname=OwlArchPC addr=? terminal=tty2 res=success'
[  252.519339] audit: type=1110 audit(1595341507.733:119): pid=1970 uid=0 auid=1000 ses=4 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shells,pam_unix,pam_permit acct="dfowl" exe="/usr/bin/login" hostname=OwlArchPC addr=? terminal=tty2 res=success'

My system specs are the following:

OS: Arch Linux x86_64
Kernel: 5.7.9-arch1-1
Shell: zsh 5.8
DE: Plasma
WM: Kwin
CPU: Intel i3-4160 (4) @ 3.600GHz
GPU: NVIDIA GeForce GTX 960
Memory 16 Gb

KDE Plasma Version: 5.19.3
KDE Frameworks Version: 5.72.0
Qt Version: 5.15.0

On the wiki I have also looked at the KDE troubleshooting page, and have tried several options which seemed similar, such as resetting cache and settings. Nothing helped. So please, tell me of any solution that you may have, this is getting seriously annoying and is hindering my workflow.

Offline

#2 2020-07-21 20:56:24

d_fajardo
Member
Registered: 2017-07-28
Posts: 1,563

Re: KDE on Arch crashes after second suspension

I had the same problem. As I said in that post, I had a reinstall (because of other issues as well besides KDE and nvidia).
Upon reinstall, I tried to monitor my system. I thought the problems are solved but actually not. The same issues as you're having, the same sort of log messages. Computer wakes and the compositor crashes. It seems this is an issued with the new nvidia driver and KDE. For now, I uninstalled powerdevil and put my computer to sleep. On wakeup, I don't get a crash but just a message the graphics has been reset. I also get freezes when I leave my PC idle. This time I think kscreenlocker is the problem so my temporary solution to it is just disable auto screen lock.

I'm going to reopen my other post. It seems there are more people having the same problem to warrant a bug report.

Offline

Board footer

Powered by FluxBB