Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Plasma desktop disappears after resume

Graphical Environments, Managers, Multimedia & Desktop questions.
Post Reply
Message
Author
ralphb
Posts: 20
Joined: 2022-05-27 09:09
Has thanked: 1 time

Plasma desktop disappears after resume

#1 Post by ralphb »

I have a pretty new Debian 11 installation on my desktop computer. If I resume my computer from suspension, my plasma desktop has disappeared: no background image, no panel, no widgets, no switching virtual desktops with the mouse wheel, etc. All the windows remain, though, and even the keyboard shortcuts like tabbing through windows or switching virtual desktops continue working.

The only option at this point is logging out, by which I mean killing /usr/bin/startplasma-x11, as there is no logout button or menu.

Before Debian, I used Kubuntu 20.04 LTS for several years. And while I use an Nvidia graphics card with proprietary driver, I've never had this issue on Kubuntu.

Do you have any suggestions on how to analyze this problem? I've checked journalctl, but didn't find anything.

Aki
Global Moderator
Global Moderator
Posts: 2816
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 68 times
Been thanked: 382 times

Re: Plasma desktop disappears after resume

#2 Post by Aki »

Hello,

Are you suspending to ram (suspension) or your are suspending to disk (hibernation) ?

What is the primary nvidia graphic card (exact model) installed in your computer ? You can check it using the following command (the inxi program must be installed):

Code: Select all

inxi -G
Are you using the proprietary nvidia kernel module or the nouveau kernel module with Debian ? You can check it analyzing the output of the command given as root user, looking for nvidia or nouveau module:

Code: Select all

lsmod
Have you checked the system journal ? When the issue occurs, you can try to shutdown the computer using the "reisub" keys sequence (see https://www.kernel.org/doc/html/latest/ ... sysrq.html) and then you can output it using the following command (in respect to the previous boot) given as root user:

Code: Select all

journalctl --no-pager -b -1 > journal.log
The journal output will be in the file named journal.log

You can also check the ~/.xsession-errors file containing errors from the X applications.

Can you share a link to a video recording of the full sequence from start of suspension up to end of resume with the issue ?
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

ralphb
Posts: 20
Joined: 2022-05-27 09:09
Has thanked: 1 time

Re: Plasma desktop disappears after resume

#3 Post by ralphb »

I'm using the nvidia driver, as nouveau (I think) was freezing my machine occasionally. Here's the inxi output:

Code: Select all

Graphics:  Device-1: NVIDIA TU116 [GeForce GTX 1660] driver: nvidia v: 460.91.03 
           Display: x11 server: X.Org 1.20.11 driver: loaded: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa resolution: 3840x2160~60Hz 
           OpenGL: renderer: GeForce GTX 1660/PCIe/SSE2 v: 4.6.0 NVIDIA 460.91.03
I'm using suspend to RAM. Also, I have to add that not all suspend and resumes cause my desktop to vanish. It seems that this happens only overnight, i.e., the machine suspends at night (by being idle for some time, or by me pressing the [Moon] key), and when I resume in the morning, the desktop fails to resume. As I mentioned before, all windows survive, and keyboard and mouse keep working normally.

I'm typing this right now with the desktop, but I did look into the journal when it happened earlier. Since I cannot attach files here, I'm posting the entire file excerpt below my response.

I can check .xsession-errors next time it happens (probably tomorrow). I can also post a photo of my desktop. As for the video, is there anything particular you're looking for?

Here's the journal, there were no more lines at the end:

Code: Select all

Jun 01 13:44:23 cassiopeia systemd[1]: Starting Suspend...
Jun 01 13:44:23 cassiopeia systemd-sleep[65486]: Suspending system...
Jun 01 13:44:23 cassiopeia kernel: Filesystems sync: 0.005 seconds
Jun 01 17:54:01 cassiopeia kernel: Freezing user space processes ... (elapsed 0.023 seconds) done.
Jun 01 17:54:01 cassiopeia kernel: OOM killer disabled.
Jun 01 17:54:01 cassiopeia kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jun 01 17:54:01 cassiopeia kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jun 01 17:54:01 cassiopeia kernel: sd 4:0:0:0: [sda] Synchronizing SCSI cache
Jun 01 17:54:01 cassiopeia kernel: sd 4:0:0:0: [sda] Stopping disk
Jun 01 17:54:01 cassiopeia kernel: ACPI: Preparing to enter system sleep state S3
Jun 01 17:54:01 cassiopeia kernel: PM: Saving platform NVS memory
Jun 01 17:54:01 cassiopeia kernel: Disabling non-boot CPUs ...
Jun 01 17:54:01 cassiopeia kernel: smpboot: CPU 1 is now offline
Jun 01 17:54:01 cassiopeia kernel: smpboot: CPU 2 is now offline
...
Jun 01 17:54:01 cassiopeia kernel: smpboot: CPU 23 is now offline
Jun 01 17:54:01 cassiopeia kernel: ACPI: Low-level resume complete
Jun 01 17:54:01 cassiopeia kernel: PM: Restoring platform NVS memory
Jun 01 17:54:01 cassiopeia kernel: LVT offset 0 assigned for vector 0x400
Jun 01 17:54:01 cassiopeia kernel: Enabling non-boot CPUs ...
Jun 01 17:54:01 cassiopeia kernel: x86: Booting SMP configuration:
Jun 01 17:54:01 cassiopeia kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Jun 01 17:54:01 cassiopeia kernel: microcode: CPU1: patch_level=0x08701013
Jun 01 17:54:01 cassiopeia kernel: ACPI: \_PR_.C002: Found 2 idle states
Jun 01 17:54:01 cassiopeia kernel: CPU1 is up
Jun 01 17:54:01 cassiopeia kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Jun 01 17:54:01 cassiopeia kernel: microcode: CPU2: patch_level=0x08701013
Jun 01 17:54:01 cassiopeia kernel: ACPI: \_PR_.C004: Found 2 idle states
Jun 01 17:54:01 cassiopeia kernel: CPU2 is up
...
Jun 01 17:54:01 cassiopeia kernel: smpboot: Booting Node 0 Processor 22 APIC 0x1b
Jun 01 17:54:01 cassiopeia kernel: microcode: CPU22: patch_level=0x08701013
Jun 01 17:54:01 cassiopeia kernel: ACPI: \_PR_.C015: Found 2 idle states
Jun 01 17:54:01 cassiopeia kernel: CPU22 is up
Jun 01 17:54:01 cassiopeia kernel: smpboot: Booting Node 0 Processor 23 APIC 0x1d
Jun 01 17:54:01 cassiopeia kernel: microcode: CPU23: patch_level=0x08701013
Jun 01 17:54:01 cassiopeia kernel: ACPI: \_PR_.C017: Found 2 idle states
Jun 01 17:54:01 cassiopeia kernel: CPU23 is up
Jun 01 17:54:01 cassiopeia kernel: ACPI: Waking up from system sleep state S3
Jun 01 17:54:01 cassiopeia kernel: sd 4:0:0:0: [sda] Starting disk
Jun 01 17:54:01 cassiopeia kernel: nvme nvme0: Shutdown timeout set to 10 seconds
Jun 01 17:54:01 cassiopeia kernel: nvme nvme0: 32/0/0 default/read/poll queues
Jun 01 17:54:01 cassiopeia kernel: ata9: SATA link down (SStatus 0 SControl 300)
Jun 01 17:54:01 cassiopeia kernel: ata4: SATA link down (SStatus 0 SControl 300)
Jun 01 17:54:01 cassiopeia kernel: ata12: SATA link down (SStatus 0 SControl 300)
Jun 01 17:54:01 cassiopeia kernel: ata11: SATA link down (SStatus 0 SControl 300)
Jun 01 17:54:01 cassiopeia kernel: ata3: SATA link down (SStatus 0 SControl 300)
Jun 01 17:54:01 cassiopeia kernel: ata6: SATA link down (SStatus 0 SControl 300)
Jun 01 17:54:01 cassiopeia kernel: ata10: SATA link down (SStatus 0 SControl 300)
Jun 01 17:54:01 cassiopeia kernel: xhci_hcd 0000:08:00.2: xHC error in resume, USBSTS 0x401, Reinit
Jun 01 17:54:01 cassiopeia kernel: usb usb5: root hub lost power or was reset
Jun 01 17:54:01 cassiopeia kernel: usb usb6: root hub lost power or was reset
Jun 01 17:54:01 cassiopeia kernel: OOM killer enabled.
Jun 01 17:54:01 cassiopeia kernel: Restarting tasks ... done.
Jun 01 17:54:01 cassiopeia kernel: PM: suspend exit
Jun 01 17:54:01 cassiopeia systemd[1]: Started Run anacron jobs.
Jun 01 17:54:01 cassiopeia anacron[65637]: Anacron 2.3 started on 2022-06-01
Jun 01 17:54:01 cassiopeia systemd-sleep[65486]: System resumed.
Jun 01 17:54:01 cassiopeia anacron[65637]: Normal exit (0 jobs run)
Jun 01 17:54:01 cassiopeia kernel: ata9: SATA link down (SStatus 0 SControl 300)
Jun 01 17:54:01 cassiopeia kernel: ata4: SATA link down (SStatus 0 SControl 300)
Jun 01 17:54:01 cassiopeia kernel: ata12: SATA link down (SStatus 0 SControl 300)
Jun 01 17:54:01 cassiopeia kernel: ata11: SATA link down (SStatus 0 SControl 300)
Jun 01 17:54:01 cassiopeia kernel: ata3: SATA link down (SStatus 0 SControl 300)
Jun 01 17:54:01 cassiopeia kernel: ata6: SATA link down (SStatus 0 SControl 300)
Jun 01 17:54:01 cassiopeia kernel: ata10: SATA link down (SStatus 0 SControl 300)
Jun 01 17:54:01 cassiopeia kernel: xhci_hcd 0000:08:00.2: xHC error in resume, USBSTS 0x401, Reinit
Jun 01 17:54:01 cassiopeia kernel: usb usb5: root hub lost power or was reset
Jun 01 17:54:01 cassiopeia kernel: usb usb6: root hub lost power or was reset
Jun 01 17:54:01 cassiopeia kernel: OOM killer enabled.
Jun 01 17:54:01 cassiopeia kernel: Restarting tasks ... done.
Jun 01 17:54:01 cassiopeia kernel: PM: suspend exit
Jun 01 17:54:01 cassiopeia systemd[1]: Started Run anacron jobs.
Jun 01 17:54:01 cassiopeia anacron[65637]: Anacron 2.3 started on 2022-06-01
Jun 01 17:54:01 cassiopeia systemd-sleep[65486]: System resumed.
Jun 01 17:54:01 cassiopeia anacron[65637]: Normal exit (0 jobs run)
Jun 01 17:54:01 cassiopeia systemd[1]: anacron.service: Succeeded.
Jun 01 17:54:01 cassiopeia systemd[1]: systemd-suspend.service: Succeeded.
Jun 01 17:54:01 cassiopeia systemd[1]: Finished Suspend.
Jun 01 17:54:01 cassiopeia systemd[1]: Stopped target Sleep.
Jun 01 17:54:01 cassiopeia systemd[1]: Reached target Suspend.
Jun 01 17:54:01 cassiopeia systemd-logind[1094]: Operation 'sleep' finished.
Jun 01 17:54:01 cassiopeia systemd[1]: Stopped target Suspend.
Jun 01 17:54:01 cassiopeia ModemManager[1145]: <info>  [sleep-monitor] system is resuming
Jun 01 17:54:01 cassiopeia NetworkManager[1082]: <info>  [1654098841.3832] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jun 01 17:54:01 cassiopeia NetworkManager[1082]: <info>  [1654098841.3833] device (enp4s0): state change: activated -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jun 01 17:54:01 cassiopeia avahi-daemon[1078]: Withdrawing address record for 192.168.99.8 on enp4s0.
Jun 01 17:54:01 cassiopeia avahi-daemon[1078]: Leaving mDNS multicast group on interface enp4s0.IPv4 with address 192.168.99.8.
Jun 01 17:54:01 cassiopeia avahi-daemon[1078]: Interface enp4s0.IPv4 no longer relevant for mDNS.
Jun 01 17:54:01 cassiopeia NetworkManager[1082]: <info>  [1654098841.4225] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 01 17:54:01 cassiopeia NetworkManager[1082]: <info>  [1654098841.4523] manager: NetworkManager state is now DISCONNECTED
Jun 01 17:54:01 cassiopeia NetworkManager[1082]: <info>  [1654098841.4536] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jun 01 17:54:01 cassiopeia dbus-daemon[1080]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=1082 comm="/usr/sbin/NetworkManager --no-daemon ")
Jun 01 17:54:01 cassiopeia systemd[1]: Starting Network Manager Script Dispatcher Service...
Jun 01 17:54:01 cassiopeia dbus-daemon[1080]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 01 17:54:01 cassiopeia systemd[1]: Started Network Manager Script Dispatcher Service.
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1126] device (enp4s0): carrier: link connected
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1128] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1139] policy: auto-activating connection 'Wired connection' (3cdcb15d-a49e-44f6-a44e-8ab8e417ddf3)
Jun 01 17:54:03 cassiopeia kernel: igb 0000:04:00.0 enp4s0: igb: enp4s0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Jun 01 17:54:03 cassiopeia kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1143] device (enp4s0): Activation: starting connection 'Wired connection' (3cdcb15d-a49e-44f6-a44e-8ab8e417ddf3)
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1144] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1147] manager: NetworkManager state is now CONNECTING
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1149] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1155] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 01 17:54:03 cassiopeia avahi-daemon[1078]: Joining mDNS multicast group on interface enp4s0.IPv4 with address 192.168.99.8.
Jun 01 17:54:03 cassiopeia avahi-daemon[1078]: New relevant interface enp4s0.IPv4 for mDNS.
Jun 01 17:54:03 cassiopeia avahi-daemon[1078]: Registering new address record for 192.168.99.8 on enp4s0.IPv4.
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1172] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1198] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1199] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1203] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1212] manager: NetworkManager state is now CONNECTED_SITE
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1213] policy: set 'Wired connection' (enp4s0) as default for IPv4 routing and DNS
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1405] device (enp4s0): Activation: successful, device activated.
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1410] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 01 17:54:03 cassiopeia dbus-daemon[1432]: [session uid=1000 pid=1432] Activating service name='org.freedesktop.Notifications' requested by ':1.183' (uid=1000 pid=25658 comm="/bin/kwin_x11 ")
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1139] policy: auto-activating connection 'Wired connection' (3cdcb15d-a49e-44f6-a44e-8ab8e417ddf3)
Jun 01 17:54:03 cassiopeia kernel: igb 0000:04:00.0 enp4s0: igb: enp4s0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Jun 01 17:54:03 cassiopeia kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1143] device (enp4s0): Activation: starting connection 'Wired connection' (3cdcb15d-a49e-44f6-a44e-8ab8e417ddf3)
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1144] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1147] manager: NetworkManager state is now CONNECTING
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1149] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1155] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 01 17:54:03 cassiopeia avahi-daemon[1078]: Joining mDNS multicast group on interface enp4s0.IPv4 with address 192.168.99.8.
Jun 01 17:54:03 cassiopeia avahi-daemon[1078]: New relevant interface enp4s0.IPv4 for mDNS.
Jun 01 17:54:03 cassiopeia avahi-daemon[1078]: Registering new address record for 192.168.99.8 on enp4s0.IPv4.
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1172] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1198] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1199] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1203] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1212] manager: NetworkManager state is now CONNECTED_SITE
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1213] policy: set 'Wired connection' (enp4s0) as default for IPv4 routing and DNS
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1405] device (enp4s0): Activation: successful, device activated.
Jun 01 17:54:03 cassiopeia NetworkManager[1082]: <info>  [1654098843.1410] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 01 17:54:03 cassiopeia dbus-daemon[1432]: [session uid=1000 pid=1432] Activating service name='org.freedesktop.Notifications' requested by ':1.183' (uid=1000 pid=25658 comm="/bin/kwin_x11 ")
Jun 01 17:54:03 cassiopeia PackageKit[1590]: get-updates transaction /452_bbdecede from uid 1000 finished with success after 207ms
Jun 01 17:54:03 cassiopeia ModemManager[1145]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:04.0/0000:04:00.0': not supported by any plugin
Jun 01 17:54:04 cassiopeia PackageKit[1590]: get-updates transaction /453_cabbdacc from uid 1000 finished with success after 198ms
Jun 01 17:54:06 cassiopeia kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jun 01 17:54:06 cassiopeia kernel: ata5.00: configured for UDMA/133
Jun 01 17:54:13 cassiopeia systemd[1]: NetworkManager-dispatcher.service: Succeeded.

Aki
Global Moderator
Global Moderator
Posts: 2816
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 68 times
Been thanked: 382 times

Re: Plasma desktop disappears after resume

#4 Post by Aki »

Hello,
The previous log is from a successful suspend and resume ?
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

ralphb
Posts: 20
Joined: 2022-05-27 09:09
Has thanked: 1 time

Re: Plasma desktop disappears after resume

#5 Post by ralphb »

Hmm, maybe the -b -1 was not quite right. It actually happened right now, so screw my overnight hypothesis.

Here's the current journal

Code: Select all

Jun 04 14:19:29 cassiopeia kernel: microcode: CPU17: patch_level=0x08701013
Jun 04 14:19:29 cassiopeia kernel: ACPI: \_PR_.C00B: Found 2 idle states
Jun 04 14:19:29 cassiopeia kernel: CPU17 is up
Jun 04 14:19:29 cassiopeia kernel: smpboot: Booting Node 0 Processor 18 APIC 0x11
Jun 04 14:19:29 cassiopeia kernel: microcode: CPU18: patch_level=0x08701013
Jun 04 14:19:29 cassiopeia kernel: ACPI: \_PR_.C00D: Found 2 idle states
Jun 04 14:19:29 cassiopeia kernel: CPU18 is up
Jun 04 14:19:29 cassiopeia kernel: smpboot: Booting Node 0 Processor 19 APIC 0x13
Jun 04 14:19:29 cassiopeia kernel: microcode: CPU19: patch_level=0x08701013
Jun 04 14:19:29 cassiopeia kernel: ACPI: \_PR_.C00F: Found 2 idle states
Jun 04 14:19:29 cassiopeia kernel: CPU19 is up
Jun 04 14:19:29 cassiopeia kernel: smpboot: Booting Node 0 Processor 20 APIC 0x15
Jun 04 14:19:29 cassiopeia kernel: microcode: CPU20: patch_level=0x08701013
Jun 04 14:19:29 cassiopeia kernel: ACPI: \_PR_.C011: Found 2 idle states
Jun 04 14:19:29 cassiopeia kernel: CPU20 is up
Jun 04 14:19:29 cassiopeia kernel: smpboot: Booting Node 0 Processor 21 APIC 0x19
Jun 04 14:19:29 cassiopeia kernel: microcode: CPU21: patch_level=0x08701013
Jun 04 14:19:29 cassiopeia kernel: ACPI: \_PR_.C013: Found 2 idle states
Jun 04 14:19:29 cassiopeia kernel: CPU21 is up
Jun 04 14:19:29 cassiopeia kernel: smpboot: Booting Node 0 Processor 22 APIC 0x1b
Jun 04 14:19:29 cassiopeia kernel: microcode: CPU22: patch_level=0x08701013
Jun 04 14:19:29 cassiopeia kernel: ACPI: \_PR_.C015: Found 2 idle states
Jun 04 14:19:29 cassiopeia kernel: CPU22 is up
Jun 04 14:19:29 cassiopeia kernel: smpboot: Booting Node 0 Processor 23 APIC 0x1d
Jun 04 14:19:29 cassiopeia kernel: microcode: CPU23: patch_level=0x08701013
Jun 04 14:19:29 cassiopeia kernel: ACPI: \_PR_.C017: Found 2 idle states
Jun 04 14:19:29 cassiopeia kernel: CPU23 is up
Jun 04 14:19:29 cassiopeia kernel: ACPI: Waking up from system sleep state S3
Jun 04 14:19:29 cassiopeia kernel: sd 4:0:0:0: [sda] Starting disk
Jun 04 14:19:29 cassiopeia kernel: nvme nvme0: Shutdown timeout set to 10 seconds
Jun 04 14:19:29 cassiopeia kernel: nvme nvme0: 32/0/0 default/read/poll queues
Jun 04 14:19:29 cassiopeia kernel: ata12: SATA link down (SStatus 0 SControl 300)
Jun 04 14:19:29 cassiopeia kernel: ata10: SATA link down (SStatus 0 SControl 300)
Jun 04 14:19:29 cassiopeia kernel: ata11: SATA link down (SStatus 0 SControl 300)
Jun 04 14:19:29 cassiopeia kernel: ata4: SATA link down (SStatus 0 SControl 300)
Jun 04 14:19:29 cassiopeia kernel: ata6: SATA link down (SStatus 0 SControl 300)
Jun 04 14:19:29 cassiopeia kernel: ata3: SATA link down (SStatus 0 SControl 300)
Jun 04 14:19:29 cassiopeia kernel: ata9: SATA link down (SStatus 0 SControl 300)
Jun 04 14:19:29 cassiopeia kernel: xhci_hcd 0000:08:00.2: xHC error in resume, USBSTS 0x401, Reinit
Jun 04 14:19:29 cassiopeia kernel: usb usb5: root hub lost power or was reset
Jun 04 14:19:29 cassiopeia kernel: usb usb6: root hub lost power or was reset
Jun 04 14:19:29 cassiopeia kernel: OOM killer enabled.
Jun 04 14:19:29 cassiopeia kernel: Restarting tasks ... done.
Jun 04 14:19:29 cassiopeia kernel: PM: suspend exit
Jun 04 14:19:29 cassiopeia systemd-sleep[249719]: System resumed.
Jun 04 14:19:29 cassiopeia systemd[1]: systemd-suspend.service: Succeeded.
Jun 04 14:19:29 cassiopeia systemd[1]: Finished Suspend.
Jun 04 14:19:29 cassiopeia systemd[1]: Stopped target Sleep.
Jun 04 14:19:29 cassiopeia systemd[1]: Reached target Suspend.
Jun 04 14:19:29 cassiopeia systemd[1]: Stopped target Suspend.
Jun 04 14:19:29 cassiopeia systemd-logind[1094]: Operation 'sleep' finished.
Jun 04 14:19:29 cassiopeia ModemManager[1145]: <info>  [sleep-monitor] system is resuming
Jun 04 14:19:29 cassiopeia NetworkManager[1082]: <info>  [1654345169.3776] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jun 04 14:19:29 cassiopeia NetworkManager[1082]: <info>  [1654345169.3776] device (enp4s0): state change: activated -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jun 04 14:19:29 cassiopeia avahi-daemon[1078]: Withdrawing address record for 192.168.99.8 on enp4s0.
Jun 04 14:19:29 cassiopeia avahi-daemon[1078]: Leaving mDNS multicast group on interface enp4s0.IPv4 with address 192.168.99.8.
Jun 04 14:19:29 cassiopeia avahi-daemon[1078]: Interface enp4s0.IPv4 no longer relevant for mDNS.
Jun 04 14:19:29 cassiopeia NetworkManager[1082]: <info>  [1654345169.4233] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 04 14:19:29 cassiopeia NetworkManager[1082]: <info>  [1654345169.4535] manager: NetworkManager state is now DISCONNECTED
Jun 04 14:19:29 cassiopeia NetworkManager[1082]: <info>  [1654345169.4549] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jun 04 14:19:29 cassiopeia dbus-daemon[1080]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=1082 comm="/usr/sbin/NetworkManager --no-daemon ")
Jun 04 14:19:29 cassiopeia systemd[1]: Starting Network Manager Script Dispatcher Service...
Jun 04 14:19:29 cassiopeia dbus-daemon[1080]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 04 14:19:29 cassiopeia systemd[1]: Started Network Manager Script Dispatcher Service.
Jun 04 14:19:30 cassiopeia dbus-daemon[1432]: [session uid=1000 pid=1432] Activating service name='org.freedesktop.Notifications' requested by ':1.554' (uid=1000 pid=244189 comm="/bin/kwin_x11 ")
Jun 04 14:19:31 cassiopeia PackageKit[1590]: get-updates transaction /527_cecedbcd from uid 1000 finished with success after 231ms
Jun 04 14:19:31 cassiopeia NetworkManager[1082]: <info>  [1654345171.1488] device (enp4s0): carrier: link connected
Jun 04 14:19:31 cassiopeia NetworkManager[1082]: <info>  [1654345171.1490] device (enp4s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jun 04 14:19:31 cassiopeia NetworkManager[1082]: <info>  [1654345171.1501] policy: auto-activating connection 'Wired connection' (3cdcb15d-a49e-44f6-a44e-8ab8e417ddf3)
Jun 04 14:19:31 cassiopeia NetworkManager[1082]: <info>  [1654345171.1505] device (enp4s0): Activation: starting connection 'Wired connection' (3cdcb15d-a49e-44f6-a44e-8ab8e417ddf3)
Jun 04 14:19:31 cassiopeia NetworkManager[1082]: <info>  [1654345171.1506] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 04 14:19:31 cassiopeia NetworkManager[1082]: <info>  [1654345171.1510] manager: NetworkManager state is now CONNECTING
Jun 04 14:19:31 cassiopeia NetworkManager[1082]: <info>  [1654345171.1512] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 04 14:19:31 cassiopeia kernel: igb 0000:04:00.0 enp4s0: igb: enp4s0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Jun 04 14:19:31 cassiopeia kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
Jun 04 14:19:31 cassiopeia NetworkManager[1082]: <info>  [1654345171.1519] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 04 14:19:31 cassiopeia NetworkManager[1082]: <info>  [1654345171.1535] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 04 14:19:31 cassiopeia NetworkManager[1082]: <info>  [1654345171.1553] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 04 14:19:31 cassiopeia NetworkManager[1082]: <info>  [1654345171.1556] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 04 14:19:31 cassiopeia NetworkManager[1082]: <info>  [1654345171.1560] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 04 14:19:31 cassiopeia NetworkManager[1082]: <info>  [1654345171.1569] manager: NetworkManager state is now CONNECTED_SITE
Jun 04 14:19:31 cassiopeia NetworkManager[1082]: <info>  [1654345171.1570] policy: set 'Wired connection' (enp4s0) as default for IPv4 routing and DNS
Jun 04 14:19:31 cassiopeia avahi-daemon[1078]: Joining mDNS multicast group on interface enp4s0.IPv4 with address 192.168.99.8.
Jun 04 14:19:31 cassiopeia avahi-daemon[1078]: New relevant interface enp4s0.IPv4 for mDNS.
Jun 04 14:19:31 cassiopeia avahi-daemon[1078]: Registering new address record for 192.168.99.8 on enp4s0.IPv4.
Jun 04 14:19:31 cassiopeia NetworkManager[1082]: <info>  [1654345171.1725] device (enp4s0): Activation: successful, device activated.
Jun 04 14:19:31 cassiopeia NetworkManager[1082]: <info>  [1654345171.1731] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 04 14:19:31 cassiopeia ModemManager[1145]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:04.0/0000:04:00.0': not supported by any plugin
Jun 04 14:19:32 cassiopeia PackageKit[1590]: get-updates transaction /528_ecebdbcd from uid 1000 finished with success after 177ms
Jun 04 14:19:34 cassiopeia kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jun 04 14:19:34 cassiopeia kernel: ata5.00: configured for UDMA/133
Jun 04 14:19:41 cassiopeia systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jun 04 14:20:32 cassiopeia org.freedesktop.Notifications[249914]: org.kde.knotifications: WaitForName: Service was not registered within timeout
Jun 04 14:20:32 cassiopeia dbus-daemon[1432]: [session uid=1000 pid=1432] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1
Jun 04 14:22:14 cassiopeia smartd[1090]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 117 to 119
Jun 04 14:22:14 cassiopeia kernel: usb 3-4: reset high-speed USB device number 28 using xhci_hcd
Jun 04 14:22:14 cassiopeia kernel: sd 12:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
Jun 04 14:22:14 cassiopeia kernel: sd 12:0:0:0: [sdb] tag#0 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00
and this is the .xsession-errors:

Code: Select all

file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/Highlight.qml:34:5: QML Connect
ions: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: 
function onFoo(<arguments>) { ... }
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/Highlight.qml:34:5: QML Connect
ions: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: 
function onFoo(<arguments>) { ... }
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64159, resource id: 14713974, majo
r code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 64160, resource id: 14713974, ma
jor code: 14 (GetGeometry), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64163, resource id: 14713974, majo
r code: 3 (GetWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 64164, resource id: 14713974, ma
jor code: 14 (GetGeometry), minor code: 0
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/Highlight.qml:34:5: QML Connect
ions: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: 
function onFoo(<arguments>) { ... }
apper.daemon: System is not ready, application should conserve resources
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/Highlight.qml:34:5: QML Connect
ions: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: 
function onFoo(<arguments>) { ... }
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/Highlight.qml:34:5: QML Connect
ions: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: 
function onFoo(<arguments>) { ... }
libkcups: Renew-Subscription last error: 0 successful-ok
Qt: Session management error: networkIdsList argument is NULL
kf.coreaddons: KDirWatch: "/usr/share/desktop-base/homeworld-theme/wallpaper" is a directory. Use 
addDir!
kf.coreaddons: KDirWatch: "/usr/share/desktop-base/futureprototype-theme/wallpaper" is a directory
. Use addDir!
kf.coreaddons: KDirWatch: "/usr/share/desktop-base/futureprototype-theme/wallpaper-withlogo" is a 
directory. Use addDir!
kf.coreaddons: KDirWatch: "/usr/share/desktop-base/joy-theme/wallpaper" is a directory. Use addDir
!
kf.coreaddons: KDirWatch: "/usr/share/desktop-base/joy-inksplat-theme/wallpaper" is a directory. U
se addDir!
kf.coreaddons: KDirWatch: "/usr/share/desktop-base/joy-theme/lockscreen" is a directory. Use addDi
r!
kf.coreaddons: KDirWatch: "/usr/share/desktop-base/lines-theme/wallpaper" is a directory. Use addD
ir!
kf.coreaddons: KDirWatch: "/usr/share/desktop-base/lines-theme/lockscreen" is a directory. Use add
Dir!
kf.coreaddons: KDirWatch: "/usr/share/desktop-base/moonlight-theme/wallpaper" is a directory. Use 
addDir!
kf.coreaddons: KDirWatch: "/usr/share/desktop-base/moonlight-theme/lockscreen" is a directory. Use
 addDir!
kf.coreaddons: KDirWatch: "/usr/share/wallpapers/Next" is a directory. Use addDir!
kf.coreaddons: KDirWatch: "/usr/share/desktop-base/softwaves-theme/wallpaper" is a directory. Use 
addDir!
kf.coreaddons: KDirWatch: "/usr/share/desktop-base/softwaves-theme/lockscreen" is a directory. Use
 addDir!
kf.coreaddons: KDirWatch: "/usr/share/desktop-base/spacefun-theme/wallpaper" is a directory. Use a
ddDir!
plasma-nm: Not emitting connection deactivated notification as we've just woken up from suspend
Service  "org.kde.StatusNotifierHost-247310" unregistered
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 48362, resource id: 81788942, majo
r code: 15 (QueryTree), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 48415, resource id: 81788952, majo
r code: 15 (QueryTree), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 48471, resource id: 81788980, majo
r code: 15 (QueryTree), minor code: 0
failed to acquire GL context to resolve capabilities, using defaults..
OpenGL vendor string:                   NVIDIA Corporation
OpenGL renderer string:                 GeForce GTX 1660/PCIe/SSE2
OpenGL version string:                  4.6.0 NVIDIA 460.91.03
OpenGL shading language version string: 4.60 NVIDIA
Driver:                                 NVIDIA
Driver version:                         460.91.3
GPU class:                              Unknown
OpenGL version:                         4.6
GLSL version:                           4.60
X server version:                       1.20.11
Linux kernel version:                   5.10
Requires strict binding:                no
GLSL shaders:                           yes
Texture NPOT support:                   yes
Virtual Machine:                        no
qt.svg: <input>:406:376: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:407:130: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:408:130: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:408:393: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:409:130: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:410:129: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:411:129: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:412:129: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:413:129: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:413:379: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:413:631: Could not add child element to parent element because the types are incorrect.
BlurConfig::instance called after the first use - ignoring
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:23:1: Type InputPanel unavailable
qrc:/QtQuick/VirtualKeyboard/content/InputPanel.qml:127:5: Type Keyboard unavailable
qrc:/QtQuick/VirtualKeyboard/content/components/Keyboard.qml:38:1: module "QtQuick.VirtualKeyboard.Plugins" is not installed
CubeSlideConfig::instance called after the first use - ignoring
DesktopGridConfig::instance called after the first use - ignoring
KscreenConfig::instance called after the first use - ignoring
PresentWindowsConfig::instance called after the first use - ignoring
SlidingPopupsConfig::instance called after the first use - ignoring
ZoomConfig::instance called after the first use - ignoring
plasma-nm: Not emitting connection activated notification as the connection was active prior to suspend
plasma-nm: Not emitting connection activated notification as the connection was active prior to suspend
Unflushed glGetGraphicsResetStatus: 0x92bb
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50287, resource id: 35651617, major code: 18 (ChangeProperty), minor code: 0
[GFX1-]: GFX: RenderThread detected a device reset in PostUpdate
And once more, for clarification, the resume itself is successful, but my plasma desktop (panel and background and everything involved with it) is gone. Windows survive, so I was still able to type those commands while in the broken state.

ralphb
Posts: 20
Joined: 2022-05-27 09:09
Has thanked: 1 time

Re: Plasma desktop disappears after resume

#6 Post by ralphb »

Unfortunately, .xsession-errors doesn't contain timestamps, so I don't know how far to go up. But there are also entries like this:

Code: Select all

qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 975, resource id: 25165837, major code: 2 (ChangeWindowAttributes), minor code: 0
kdeinit5: PID 247365 terminated.
kdeinit5: PID 247363 terminated.
kdeinit5: PID 247364 terminated.
kdeinit5: PID 247342 terminated.
kdeinit5: PID 247360 terminated.
[GFX1-]: GFX: RenderThread detected a device reset in PostUpdate
Unflushed glGetGraphicsResetStatus: 0x92bb

###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost


###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost


###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 49593, resource id: 75497480, major code: 18 (ChangeProperty), minor code: 0
Service  ":1.602" unregistered

###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

User avatar
canci
Global Moderator
Global Moderator
Posts: 2497
Joined: 2006-09-24 11:28
Has thanked: 135 times
Been thanked: 134 times

Re: Plasma desktop disappears after resume

#7 Post by canci »

ralphb wrote: 2022-06-04 12:36 Unfortunately, .xsession-errors doesn't contain timestamps, so I don't know how far to go up.
But journalctl does.
Image Stable / Asus VivoBook X421DA / AMD Ryzen 7 3700U / Radeon Vega Mobile Gfx (Picasso) / 8 GB RAM / 512GB NVMe

READ THIS:

* How to Post a Thread Here
* Other Tips and Great Resources

ralphb
Posts: 20
Joined: 2022-05-27 09:09
Has thanked: 1 time

Re: Plasma desktop disappears after resume

#8 Post by ralphb »

canci wrote: 2022-06-04 13:10
ralphb wrote: 2022-06-04 12:36 Unfortunately, .xsession-errors doesn't contain timestamps, so I don't know how far to go up.
But journalctl does.
Yes indeed. And? :wink:

User avatar
canci
Global Moderator
Global Moderator
Posts: 2497
Joined: 2006-09-24 11:28
Has thanked: 135 times
Been thanked: 134 times

Re: Plasma desktop disappears after resume

#9 Post by canci »

And you could have a look, since sometimes warning about Xorg stuff also appears in journalctl :lol:
Image Stable / Asus VivoBook X421DA / AMD Ryzen 7 3700U / Radeon Vega Mobile Gfx (Picasso) / 8 GB RAM / 512GB NVMe

READ THIS:

* How to Post a Thread Here
* Other Tips and Great Resources

ralphb
Posts: 20
Joined: 2022-05-27 09:09
Has thanked: 1 time

Re: Plasma desktop disappears after resume

#10 Post by ralphb »

canci wrote: 2022-06-04 16:02 And you could have a look, since sometimes warning about Xorg stuff also appears in journalctl :lol:
I did post the journal, which includes the suspension and the resume.

User avatar
canci
Global Moderator
Global Moderator
Posts: 2497
Joined: 2006-09-24 11:28
Has thanked: 135 times
Been thanked: 134 times

Re: Plasma desktop disappears after resume

#11 Post by canci »

Sorry, I didn't see it immediately.
Image Stable / Asus VivoBook X421DA / AMD Ryzen 7 3700U / Radeon Vega Mobile Gfx (Picasso) / 8 GB RAM / 512GB NVMe

READ THIS:

* How to Post a Thread Here
* Other Tips and Great Resources

Aki
Global Moderator
Global Moderator
Posts: 2816
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 68 times
Been thanked: 382 times

Re: Plasma desktop disappears after resume

#12 Post by Aki »

Hello,
ralphb wrote: 2022-06-04 12:30 And once more, for clarification, the resume itself is successful, but my plasma desktop (panel and background and everything involved with it) is gone. Windows survive, so I was still able to type those commands while in the broken state.
It could be a KDE's plasmashell issue. You can check it manually restarting plasmashell after suspending; you can do it opening a terminal window and using the following command after resume failure:

Code: Select all

plasmashell --replace &
Does the previous command restore the missing desktop elements when the issue appears after resume ?

Have you installed third part plasmoids ? Some of them may fail during resume.

See https://community.kde.org/Plasma/Debugging for more info about plasmashell debugging.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

ralphb
Posts: 20
Joined: 2022-05-27 09:09
Has thanked: 1 time

Re: Plasma desktop disappears after resume

#13 Post by ralphb »

Thanks for that command

Code: Select all

plasmashell --replace &
that does indeed restore the plasma desktop without losing my session.

Unfortunately, I've just restarted plasma using that command, so because of that (I assume) the journal for /usr/bin/plasmashell is empty. I'll check next time it happens.

As for plasmoids, I installed only two standard plasmoids that came with KDE (some monitor and analogue clock). I did experiment with my own plasmoid, but as far as I can tell, no instances remain installed.

Aki
Global Moderator
Global Moderator
Posts: 2816
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 68 times
Been thanked: 382 times

Re: Plasma desktop disappears after resume

#14 Post by Aki »

ralphb wrote: 2022-06-20 16:18 I did experiment with my own plasmoid, but as far as I can tell, no instances remain installed.
Something remained could be an explanation.

Could you create a brand new user account and test if the suspention to ram works with it ?
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

ralphb
Posts: 20
Joined: 2022-05-27 09:09
Has thanked: 1 time

Re: Plasma desktop disappears after resume

#15 Post by ralphb »

Yes, I'll try that once I'm done with my current task.

BTW, my plasmoid is still installed:

Code: Select all

cassiopeia ~ > ls .local/share/plasma/plasmoids/
pliff/
But where are widget instances registered? The file .config/plasma-org.kde.plasma.desktop-appletsrc contains pliff:

Code: Select all

[Containments][39][General]
extraItems=pliff,org.kde.plasma.nightcolorcontrol,org.kde.plasma.mediacontroller,org.kde.plasma.battery,org.kde.plasma.printmanager,org.kde.kupapplet,org.kde.plasma.bluetooth,org.kde.plasma.vault,org.kde.plasma.notifications,org.kde.plasma.devicenotifier,org.kde.kdeconnect,org.kde.plasma.keyboardindicator,org.kde.plasma.clipboard,org.kde.plasma.networkmanagement,org.kde.plasma.volume
knownItems=pliff,org.kde.plasma.nightcolorcontrol,org.kde.plasma.mediacontroller,org.kde.plasma.battery,org.kde.plasma.printmanager,org.kde.kupapplet,org.kde.plasma.bluetooth,org.kde.plasma.vault,org.kde.plasma.notifications,org.kde.plasma.devicenotifier,org.kde.kdeconnect,org.kde.plasma.keyboardindicator,org.kde.plasma.clipboard,org.kde.plasma.networkmanagement,org.kde.plasma.volume
I guess this only means that pliff is installed, but not instantiated, i.e., there is no actual pliff widget?

Could this plasmoid still crash plasmashell merely by being installed?

ralphb
Posts: 20
Joined: 2022-05-27 09:09
Has thanked: 1 time

Re: Plasma desktop disappears after resume

#16 Post by ralphb »

It has just happened again. Unfortunately, the journal is empty:

Code: Select all

cassiopeia:~# journalctl /usr/bin/plasmashell 
-- Journal begins at Sat 2022-05-21 11:24:01 CEST, ends at Fri 2022-06-24 16:00:10 CEST. --
-- No entries --
And because there is no more plasmashell running, I'm not sure how to apply the rest of the Debug description linked here.

Aki
Global Moderator
Global Moderator
Posts: 2816
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 68 times
Been thanked: 382 times

Re: Plasma desktop disappears after resume

#17 Post by Aki »

Hi,
ralphb wrote: 2022-06-23 15:57 Could this plasmoid still crash plasmashell merely by being installed?
I don't know it exactly, but, if you create a new user account and test if the issue occurs (or not) with the fresh new account, it could give you an answer (if you did a local installation - not system wide - of your custom test plasmoid).

Does plasmashell crashes every time you suspend to ram or randomly ? if it always occurs after system suspension, you could get a log restarting plasmashell before you trigger the crash and recording all console output in a file, for example with these commands from a konsole terminal as normal user:

Code: Select all

$ script plasmashell.log
$ plasmashell --replace &
After the plasmashell restarts, all its output should go to the terminal console and from it to the file called plasmashell.log

Then, you can trigger the issue (suspending the system) and, after resume from suspension, you should able to stop logging from the same previous konsole terminal with the command:

Code: Select all

$ exit
Logs should be in the file named plasmashell.log
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

ralphb
Posts: 20
Joined: 2022-05-27 09:09
Has thanked: 1 time

Re: Plasma desktop disappears after resume

#18 Post by ralphb »

It finally happened again (manually suspending and resuming doesn't seem to work?!), and this is what was in the window where I ran "plasmashell --replace &":

Code: Select all

Model size of -2147483647 is less than 0
libkcups: Renew-Subscription last error: 0 successful-ok
Model size of -2147483647 is less than 0
Model size of -2147483647 is less than 0
Model size of -2147483647 is less than 0
Model size of -2147483647 is less than 0
libkcups: Renew-Subscription last error: 0 successful-ok
qt.svg: <input>:406:376: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:407:130: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:408:130: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:408:393: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:409:130: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:410:129: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:411:129: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:412:129: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:413:129: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:413:379: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:413:631: Could not add child element to parent element because the types are incorrect.
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 41832, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41833, resource id: 100663785, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41834, resource id: 100663785, major code: 72 (PutImage), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 41835, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41836, resource id: 100663787, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41837, resource id: 100663787, major code: 72 (PutImage), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 41838, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41839, resource id: 100663789, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41840, resource id: 100663789, major code: 72 (PutImage), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 41854, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41855, resource id: 100663793, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41856, resource id: 100663793, major code: 72 (PutImage), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 41857, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41858, resource id: 100663795, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41859, resource id: 100663795, major code: 72 (PutImage), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 41860, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41861, resource id: 100663797, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41862, resource id: 100663797, major code: 72 (PutImage), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 41863, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41864, resource id: 100663799, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41865, resource id: 100663799, major code: 72 (PutImage), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 41866, resource id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41867, resource id: 100663801, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 41868, resource id: 100663801, major code: 72 (PutImage), minor code: 0
qt.svg: <input>:406:376: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:407:130: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:408:130: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:408:393: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:409:130: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:410:129: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:411:129: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:412:129: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:413:129: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:413:379: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:413:631: Could not add child element to parent element because the types are incorrect.
qt.qpa.xcb: QXcbConnection: XCB error: 4 (BadPixmap), sequence: 42558, resource id: 100663801, major code: 54 (FreePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 13 (BadGC), sequence: 42559, resource id: 100663802, major code: 60 (FreeGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 4 (BadPixmap), sequence: 42560, resource id: 100663793, major code: 54 (FreePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 13 (BadGC), sequence: 42561, resource id: 100663794, major code: 60 (FreeGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 4 (BadPixmap), sequence: 42562, resource id: 100663795, major code: 54 (FreePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 13 (BadGC), sequence: 42563, resource id: 100663796, major code: 60 (FreeGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 4 (BadPixmap), sequence: 42603, resource id: 100663797, major code: 54 (FreePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 13 (BadGC), sequence: 42604, resource id: 100663798, major code: 60 (FreeGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 4 (BadPixmap), sequence: 42605, resource id: 100663799, major code: 54 (FreePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 13 (BadGC), sequence: 42606, resource id: 100663800, major code: 60 (FreeGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 4 (BadPixmap), sequence: 42616, resource id: 100663785, major code: 54 (FreePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 13 (BadGC), sequence: 42617, resource id: 100663786, major code: 60 (FreeGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 4 (BadPixmap), sequence: 42618, resource id: 100663787, major code: 54 (FreePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 13 (BadGC), sequence: 42619, resource id: 100663788, major code: 60 (FreeGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 4 (BadPixmap), sequence: 42620, resource id: 100663789, major code: 54 (FreePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 13 (BadGC), sequence: 42621, resource id: 100663790, major code: 60 (FreeGC), minor code: 0
libkcups: Renew-Subscription last error: 0 successful-ok
I don't really see anything in this, though. And where would I find plasmashell.log? A find on ~ didn't reveal this file (but I had restarted plasmashell already).

Post Reply