You are not logged in.

#1 2024-12-27 01:33:57

Big Scorpio
Member
Registered: 2024-12-15
Posts: 58

Why is my desktop environment unresponsive for 3 minutes?

Hello Arch Friends,

I'll simplify the problem i mentioned earlier.
I am using KDE as my desktop environment.
I believe zram is active. I set it to ON as per default when using the archinstaller

cat /proc/swaps
Filename                                Type            Size            Used            Priority
/dev/zram0                              partition       4003324         0               100

i notice, that the OS has created no swap partition. I am unsure if that is the nature of the problem.

My problem is that my desktop environment freezes and is unresponsive to any action. Not even any hovering effect. not even a click and drag on the desktop background functions but i can move the cursor freely and interact with the currently visible programs on the foreground. i observed the time to be 20:10 and it became responsive as soon as I saw the time was 20:13. This is unacceptable.
What's the reason for such system unresponsiveness? This is happening regularly since I started using Arch Linux.

Offline

#2 2024-12-27 10:31:40

seth
Member
Registered: 2012-09-03
Posts: 61,670

Re: Why is my desktop environment unresponsive for 3 minutes?

I'll simplify the problem i mentioned earlier.

Where?

i notice, that the OS has created no swap partition. I am unsure if that is the nature of the problem.

If you end up running OOM, yes.

Though

Not even any hovering effect. not even a click and drag on the desktop background functions but i can move the cursor freely and interact with the currently visible programs on the foreground.

What you describe sounds as if it only affects the desktop shell (plasmashell) specifically?
The predominant reason for that is some desktop shelll widget thing.

=> check your system journal after such stall

sudo journalctl -b -e

Offline

#3 2024-12-27 17:35:44

Big Scorpio
Member
Registered: 2024-12-15
Posts: 58

Re: Why is my desktop environment unresponsive for 3 minutes?

seth wrote:

Where?

Here -> https://bbs.archlinux.org/viewtopic.php?id=301968
I figured that was too much information at once, so i restarted but small this time.

seth wrote:

If you end up running OOM, yes.

OOM as in out of memory? I've got 8 GB RAM for now. I may try setting up a swap partition to see if there's any difference. Unless that conflicts with zram but i am not experienced enough to know what zram does and whether swap is compatible with it.

seth wrote:

What you describe sounds as if it only affects the desktop shell (plasmashell) specifically?
The predominant reason for that is some desktop shelll widget thing.

If that's what the system menu bar with the tray at the bottom is called, then yes.

seth wrote:

=> check your system journal after such stall

I'll try once I encounter it again. Today it didn't happen. However I see this

Dec 27 18:18:25 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Dec 27 18:18:29 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Dec 27 18:18:33 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Dec 27 18:18:37 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Dec 27 18:18:41 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Dec 27 18:18:45 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Dec 27 18:18:49 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?

And I see those messages even when I'm on the Arch Linux installation media on the USB drive, a live environment if you will.

Offline

#4 2024-12-27 21:54:59

xerxes_
Member
Registered: 2018-04-29
Posts: 885

Re: Why is my desktop environment unresponsive for 3 minutes?

Does it happen when your zram is heavy loaded/used?

You may try some lightweight DE to see if it also happens.

Does your usb ports stop working? If yes, then see here: https://askubuntu.com/questions/1359116 … ltiple-dev

Offline

#5 2024-12-28 08:49:45

seth
Member
Registered: 2012-09-03
Posts: 61,670

Re: Why is my desktop environment unresponsive for 3 minutes?

This is why shopping list threads are heavily discouraged wink

usb usb2-port1: Cannot enable. Maybe the USB cable is bad?

You should take this serious: https://bbs.archlinux.org/viewtopic.php?id=302043

Offline

#6 2024-12-28 15:28:55

Big Scorpio
Member
Registered: 2024-12-15
Posts: 58

Re: Why is my desktop environment unresponsive for 3 minutes?

Well, i decided to reinstall Arch with Full Disk Encryption as i was missing it and planned to do so after the install. Pfft. I wish. The f2fs file system cannot be shrunk yet and i spanned it over my whole SSD, leaving no room for FDE. So I had to redo it all from the beginning.
Now, I'd love to comply with your suggestions but I have encountered a more serious problem now. I can't access my encrypted drive. See my new blocking problem here -> https://bbs.archlinux.org/viewtopic.php … 4#p2216984

Still, I understood from you, that I'll have to fiddle around with the USB connectors to see which one of them is being 'faulty', meaning pulling out and plugging in again one by one until this nagging message vanishes.
xerxes_, The USB ports all work fine and all USB devices I have connected are functional. I don't really think it's a HW issue on the motherboards part. On my Windows system I see no such message appearing or io stalling.
Still, I will deduce it today and report back.

Offline

#7 2024-12-28 20:28:55

seth
Member
Registered: 2012-09-03
Posts: 61,670

Re: Why is my desktop environment unresponsive for 3 minutes?

meaning pulling out and plugging in again one by one until this nagging message vanishes

You can also bisect them (yank half them to check which half includes the bogus one) but kind pointless if you're "three" or so

Offline

#8 2025-01-03 07:50:17

Big Scorpio
Member
Registered: 2024-12-15
Posts: 58

Re: Why is my desktop environment unresponsive for 3 minutes?

Alright, I got back now that FDE works at last. I hope ya'll had a good start into the new year.

I did as you suggested seth and temporarily disconnected every single USB device on my machine while running

sudo dmesg -wH

In parallel to monitor if anything has changed.
I did all that and this USB cannot enable message never stopped printing. It appears, that none of my USB devices are connected to that port:

[  +3.973282] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?

[  +2.273260] usb 1-3: new low-speed USB device number 8 using xhci_hcd
[  +2.129868] usb 1-4: new high-speed USB device number 10 using xhci_hcd
[  +0.000006] usb 1-5: Manufacturer: VIA Labs, Inc.         
[  +0.002346] hub 1-5:1.0: USB hub found
[  +0.000279] hub 1-5:1.0: 4 ports detected
[  +0.731988] usb 1-5.2: new full-speed USB device number 14 using xhci_hcd

[  +0.000008] usb 2-5: Product: USB3.0 Hub             
[  +0.000006] usb 2-5: Manufacturer: VIA Labs, Inc.         
[  +0.003348] hub 2-5:1.0: USB hub found
[  +0.000316] hub 2-5:1.0: 4 ports detected

[  +0.325780] usb 1-2: USB disconnect, device number 3

[  +1.203287] usb 3-1: new low-speed USB device number 3 using xhci_hcd
[  +0.637847] usb 2-5.3: USB disconnect, device number 6
[  +0.909755] usb 2-5.4: USB disconnect, device number 7
[  +0.446869] usb 1-5.4: new high-speed USB device number 17 using xhci_hcd

[  +3.109934] usb 5-2: new high-speed USB device number 2 using xhci_hcd
[  +0.004752] hub 5-2:1.0: USB hub found

[  +0.001250] hub 6-2:1.0: USB hub found


[  +3.973282] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?

I shortened the output here but you'll have to take my word when I say the USB cannot enable message was printing before and after the disconnect and reconnect of the USB devices - one by one.

If I am logically thinking about it, if that port is unused, can i just persistently disable it as a workaround to deal with the delayed IO problem?

If that port number is referring to the frontal USB connectors, I do not have any frontal USB connectors handy, meaning the Motherboard's section responsible for the frontal USB and Audio connectors is not connected to anything.

UPDATE
To the initial point with the "sudo journalctl -b -e" part I got more data on that.

(1) I went AFK. My System has suspended as a result of that. I came back later and the screens were blank and my Keyboard and mouse didn't have their RGB lit up. I attempt to wake it up with random keystrokes. Keyboard & Mouse's LED are lit. 2 Minutes pass before I see the login screen. I log in and immediately perform "sudo journalctl -b -e" I had prepared on the terminal to execute right away. Here's the output:

Jan 03 09:14:15 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:14:19 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:14:23 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:14:26 Nexus systemd-logind[706]: The system will suspend now!
Jan 03 09:14:26 Nexus NetworkManager[705]: <info>  [1735892066.5830] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 03 09:14:26 Nexus NetworkManager[705]: <info>  [1735892066.5833] manager: NetworkManager state is now ASLEEP
Jan 03 09:14:26 Nexus NetworkManager[705]: <info>  [1735892066.5840] device (enp7s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jan 03 09:14:26 Nexus kded6[936]: org.kde.plasma.nm.kded: Unhandled active connection state change:  3
Jan 03 09:14:26 Nexus systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 03 09:14:26 Nexus systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 03 09:14:26 Nexus NetworkManager[705]: <info>  [1735892066.6420] device (enp7s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jan 03 09:14:26 Nexus NetworkManager[705]: <info>  [1735892066.6423] dhcp4 (enp7s0): canceled DHCP transaction
Jan 03 09:14:26 Nexus NetworkManager[705]: <info>  [1735892066.6424] dhcp4 (enp7s0): activation: beginning transaction (timeout in 45 seconds)
Jan 03 09:14:26 Nexus NetworkManager[705]: <info>  [1735892066.6424] dhcp4 (enp7s0): state changed no lease
Jan 03 09:14:26 Nexus NetworkManager[705]: <info>  [1735892066.7128] device (enp7s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jan 03 09:14:26 Nexus systemd[1]: Reached target Sleep.
Jan 03 09:14:26 Nexus systemd[1]: Starting NVIDIA system suspend actions...
Jan 03 09:14:26 Nexus suspend[24559]: nvidia-suspend.service
Jan 03 09:14:26 Nexus logger[24559]: <13>Jan  3 09:14:26 suspend: nvidia-suspend.service
Jan 03 09:14:27 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:14:28 Nexus systemd[1]: nvidia-suspend.service: Deactivated successfully.
Jan 03 09:14:28 Nexus systemd[1]: Finished NVIDIA system suspend actions.
Jan 03 09:14:28 Nexus systemd[1]: nvidia-suspend.service: Consumed 1.157s CPU time, 1.1G memory peak.
Jan 03 09:14:28 Nexus systemd[1]: Starting System Suspend...
Jan 03 09:14:28 Nexus systemd-sleep[24572]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Jan 03 09:14:28 Nexus systemd-sleep[24572]: This is not recommended, and might result in unexpected behavior, particularly
Jan 03 09:14:28 Nexus systemd-sleep[24572]: in suspend-then-hibernate operations or setups with encrypted home directories.
Jan 03 09:14:28 Nexus systemd-sleep[24572]: Performing sleep operation 'suspend'...
Jan 03 09:14:28 Nexus kernel: PM: suspend entry (deep)
Jan 03 09:14:28 Nexus kernel: Filesystems sync: 0.209 seconds
Jan 03 09:45:51 Nexus kernel: Freezing user space processes
Jan 03 09:45:51 Nexus kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Jan 03 09:45:51 Nexus kernel: OOM killer disabled.
Jan 03 09:45:51 Nexus kernel: Freezing remaining freezable tasks
Jan 03 09:45:51 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:45:51 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:45:51 Nexus kernel: Freezing remaining freezable tasks completed (elapsed 6.741 seconds)
Jan 03 09:45:51 Nexus kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 03 09:45:51 Nexus kernel: serial 00:01: disabled
Jan 03 09:45:51 Nexus kernel: e1000e: EEE TX LPI TIMER: 00000011
Jan 03 09:45:51 Nexus kernel: sd 8:0:0:0: [sde] Synchronizing SCSI cache
Jan 03 09:45:51 Nexus kernel: sd 5:0:0:0: [sdd] Synchronizing SCSI cache
Jan 03 09:45:51 Nexus kernel: sd 4:0:0:0: [sdc] Synchronizing SCSI cache
Jan 03 09:45:51 Nexus kernel: sd 3:0:0:0: [sdb] Synchronizing SCSI cache
Jan 03 09:45:51 Nexus kernel: sd 1:0:0:0: [sda] Synchronizing SCSI cache
Jan 03 09:45:51 Nexus kernel: ata5.00: Entering standby power mode
Jan 03 09:45:51 Nexus kernel: ata6.00: Entering standby power mode
Jan 03 09:45:51 Nexus kernel: ata4.00: Entering standby power mode
Jan 03 09:45:51 Nexus kernel: ata2.00: Entering standby power mode
Jan 03 09:45:51 Nexus kernel: ACPI: PM: Preparing to enter system sleep state S3
Jan 03 09:45:51 Nexus kernel: ACPI: PM: Saving platform NVS memory
Jan 03 09:45:51 Nexus kernel: Disabling non-boot CPUs ...
Jan 03 09:45:51 Nexus kernel: smpboot: CPU 7 is now offline
Jan 03 09:45:51 Nexus kernel: smpboot: CPU 6 is now offline
Jan 03 09:45:51 Nexus kernel: smpboot: CPU 5 is now offline
Jan 03 09:45:51 Nexus kernel: smpboot: CPU 4 is now offline
Jan 03 09:45:51 Nexus kernel: smpboot: CPU 3 is now offline
Jan 03 09:45:51 Nexus kernel: smpboot: CPU 2 is now offline
Jan 03 09:45:51 Nexus kernel: smpboot: CPU 1 is now offline
Jan 03 09:45:51 Nexus kernel: ACPI: PM: Low-level resume complete
Jan 03 09:45:51 Nexus kernel: ACPI: PM: Restoring platform NVS memory
Jan 03 09:45:51 Nexus kernel: Enabling non-boot CPUs ...
Jan 03 09:45:51 Nexus kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Jan 03 09:45:51 Nexus kernel: CPU1 is up
Jan 03 09:45:51 Nexus kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Jan 03 09:45:51 Nexus kernel: CPU2 is up
Jan 03 09:45:51 Nexus kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Jan 03 09:45:51 Nexus kernel: CPU3 is up
Jan 03 09:45:51 Nexus kernel: smpboot: Booting Node 0 Processor 4 APIC 0x1
Jan 03 09:45:51 Nexus kernel: CPU4 is up
Jan 03 09:45:51 Nexus kernel: smpboot: Booting Node 0 Processor 5 APIC 0x3
Jan 03 09:45:51 Nexus kernel: CPU5 is up
Jan 03 09:45:51 Nexus kernel: smpboot: Booting Node 0 Processor 6 APIC 0x5
Jan 03 09:45:51 Nexus kernel: CPU6 is up
Jan 03 09:45:51 Nexus kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
Jan 03 09:45:51 Nexus kernel: CPU7 is up
Jan 03 09:45:51 Nexus kernel: ACPI: PM: Waking up from system sleep state S3
Jan 03 09:45:51 Nexus kernel: usb usb3: root hub lost power or was reset
Jan 03 09:45:51 Nexus kernel: usb usb4: root hub lost power or was reset
Jan 03 09:45:51 Nexus kernel: serial 00:01: activated
Jan 03 09:45:51 Nexus kernel: nvme nvme0: 8/0/0 default/read/poll queues
Jan 03 09:45:51 Nexus kernel: ata8: SATA link down (SStatus 0 SControl 300)
Jan 03 09:45:51 Nexus kernel: ata7: SATA link down (SStatus 0 SControl 300)
Jan 03 09:45:51 Nexus kernel: ata1: SATA link down (SStatus 4 SControl 300)
Jan 03 09:45:51 Nexus kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 03 09:45:51 Nexus kernel: ata3: SATA link down (SStatus 4 SControl 300)
Jan 03 09:45:51 Nexus kernel: ata2.00: supports DRM functions and may not be fully accessible
Jan 03 09:45:51 Nexus kernel: sd 1:0:0:0: [sda] Starting disk
Jan 03 09:45:51 Nexus kernel: ata2.00: supports DRM functions and may not be fully accessible
Jan 03 09:45:51 Nexus kernel: ata2.00: configured for UDMA/133
Jan 03 09:45:51 Nexus kernel: ahci 0000:00:17.0: port does not support device sleep
Jan 03 09:45:51 Nexus kernel: ata2.00: Enabling discard_zeroes_data
Jan 03 09:45:51 Nexus kernel: usb 3-1: reset low-speed USB device number 3 using xhci_hcd
Jan 03 09:45:51 Nexus kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 03 09:45:51 Nexus kernel: sd 4:0:0:0: [sdc] Starting disk
Jan 03 09:45:51 Nexus kernel: ata5.00: configured for UDMA/100
Jan 03 09:45:51 Nexus kernel: OOM killer enabled.
Jan 03 09:45:51 Nexus kernel: Restarting tasks ... 
Jan 03 09:45:51 Nexus kernel: pci_bus 0000:09: Allocating resources
Jan 03 09:45:51 Nexus kernel: pci_bus 0000:09: Allocating resources
Jan 03 09:45:51 Nexus kernel: usb 1-2: USB disconnect, device number 15
Jan 03 09:45:51 Nexus kernel: done.
Jan 03 09:45:51 Nexus kernel: random: crng reseeded on system resumption
Jan 03 09:45:51 Nexus kernel: PM: suspend exit
Jan 03 09:45:51 Nexus kernel: snd_hda_intel 0000:00:1f.3: Direct firmware load for ctefx-r3di.bin failed with error -2
Jan 03 09:45:51 Nexus rtkit-daemon[918]: The canary thread is apparently starving. Taking action.
Jan 03 09:45:51 Nexus pipewire[989]: pw.node: (auto_null-57) graph xrun not-triggered (0 suppressed)
Jan 03 09:45:51 Nexus rtkit-daemon[918]: Demoting known real-time threads.
Jan 03 09:45:51 Nexus pipewire[989]: pw.node: (auto_null-57) xrun state:0x7ce50defb008 pending:0/3 s:15086788497881 a:15086788547393 f:15086788557924 waiting:49512 process:10531 status:triggered
Jan 03 09:45:51 Nexus rtkit-daemon[918]: Successfully demoted thread 3274 of process 2521.
Jan 03 09:45:51 Nexus systemd[1]: Starting Load/Save RF Kill Switch Status...
Jan 03 09:45:51 Nexus rtkit-daemon[918]: Successfully demoted thread 2329 of process 2186.
Jan 03 09:45:51 Nexus systemd-sleep[24572]: System returned from sleep operation 'suspend'.
Jan 03 09:45:51 Nexus rtkit-daemon[918]: Successfully demoted thread 1007 of process 991.
Jan 03 09:45:51 Nexus rtkit-daemon[918]: Successfully demoted thread 991 of process 991.
Jan 03 09:45:51 Nexus rtkit-daemon[918]: Successfully demoted thread 997 of process 992.
Jan 03 09:45:51 Nexus rtkit-daemon[918]: Successfully demoted thread 992 of process 992.
Jan 03 09:45:51 Nexus rtkit-daemon[918]: Successfully demoted thread 995 of process 989.
Jan 03 09:45:51 Nexus rtkit-daemon[918]: Successfully demoted thread 989 of process 989.
Jan 03 09:45:51 Nexus rtkit-daemon[918]: Demoted 8 threads.
Jan 03 09:45:51 Nexus systemd[1]: Started Load/Save RF Kill Switch Status.
Jan 03 09:45:51 Nexus systemd[1]: Stopped target Bluetooth Support.
Jan 03 09:45:51 Nexus systemd[821]: Stopped target Bluetooth.
Jan 03 09:45:51 Nexus kernel: pci_bus 0000:09: Allocating resources
Jan 03 09:45:52 Nexus kernel: snd_hda_codec_ca0132 hdaudioC2D0: ca0132 DSP downloaded and running
Jan 03 09:45:52 Nexus kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 03 09:45:52 Nexus kernel: sd 3:0:0:0: [sdb] Starting disk
Jan 03 09:45:52 Nexus kernel: ata4.00: configured for UDMA/133
Jan 03 09:45:53 Nexus systemd[1]: systemd-suspend.service: Deactivated successfully.
Jan 03 09:45:53 Nexus systemd[1]: Finished System Suspend.
Jan 03 09:45:53 Nexus systemd[1]: systemd-suspend.service: Consumed 1.804s CPU time, 20.1M memory peak.
Jan 03 09:45:53 Nexus systemd[1]: Stopped target Sleep.
Jan 03 09:45:53 Nexus systemd[1]: Reached target Suspend.
Jan 03 09:45:53 Nexus systemd[1]: Starting NVIDIA system resume actions...
Jan 03 09:45:53 Nexus systemd[1]: Stopped target Suspend.
Jan 03 09:45:53 Nexus systemd-logind[706]: Operation 'suspend' finished.
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.1313] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.1313] device (enp0s31f6): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jan 03 09:45:53 Nexus suspend[24738]: nvidia-resume.service
Jan 03 09:45:53 Nexus logger[24738]: <13>Jan  3 09:45:53 suspend: nvidia-resume.service
Jan 03 09:45:53 Nexus systemd[1]: nvidia-resume.service: Deactivated successfully.
Jan 03 09:45:53 Nexus systemd[1]: Finished NVIDIA system resume actions.
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.2078] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jan 03 09:45:53 Nexus kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.3910] device (enp7s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jan 03 09:45:53 Nexus kernel: alx 0000:07:00.0 enp7s0: NIC Up: 100 Mbps Full
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.3958] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.3967] device (enp7s0): carrier: link connected
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.3974] device (enp7s0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.3989] policy: auto-activating connection 'Wired connection 2' (033f2013-2080-38b2-bed9-a78c10a95e7f)
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.4003] device (enp7s0): Activation: starting connection 'Wired connection 2' (033f2013-2080-38b2-bed9-a78c10a95e7f)
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.4013] device (enp7s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.4023] manager: NetworkManager state is now CONNECTING
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.4027] device (enp7s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.4043] device (enp7s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.4056] dhcp4 (enp7s0): activation: beginning transaction (timeout in 45 seconds)
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.4098] dhcp4 (enp7s0): error parsing DHCP option 6 (domain_name_servers): address 0.0.0.0 is ignored
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.4099] dhcp4 (enp7s0): state changed new lease, address=192.168.1.13, acd pending
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.5719] dhcp4 (enp7s0): state changed new lease, address=192.168.1.13
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.5721] policy: set 'Wired connection 2' (enp7s0) as default for IPv4 routing and DNS
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.5846] device (enp7s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.5857] device (enp7s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.5858] device (enp7s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.5861] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 03 09:45:53 Nexus NetworkManager[705]: <info>  [1735893953.5862] device (enp7s0): Activation: successful, device activated.
Jan 03 09:45:53 Nexus systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jan 03 09:45:53 Nexus systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 03 09:45:53 Nexus systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 03 09:45:54 Nexus wireplumber[991]: spa.bluez5: BlueZ system service is not available
Jan 03 09:45:54 Nexus kernel: ata6: link is slow to respond, please be patient (ready=0)
Jan 03 09:45:55 Nexus pipewire[989]: spa.v4l2: '/dev/video0' VIDIOC_QUERYCTRL: Value too large for defined data type
Jan 03 09:45:55 Nexus kernel: usb 1-4: Failed to query (GET_DEF) UVC control 9 on unit 1: -75 (exp. 2).
Jan 03 09:45:55 Nexus pipewire[989]: spa.v4l2: '/dev/video0' VIDIOC_QUERYCTRL: Broken pipe
Jan 03 09:45:55 Nexus kernel: usb 1-4: Failed to query (GET_DEF) UVC control 9 on unit 1: 0 (exp. 2).
Jan 03 09:45:55 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:45:56 Nexus systemd[1]: systemd-rfkill.service: Deactivated successfully.
Jan 03 09:45:58 Nexus kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 03 09:45:58 Nexus kernel: sd 5:0:0:0: [sdd] Starting disk
Jan 03 09:45:58 Nexus kernel: ata6.00: configured for UDMA/133
Jan 03 09:45:59 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:46:03 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:46:03 Nexus systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jan 03 09:46:03 Nexus org_kde_powerdevil[1017]: dh=Display_Handle[i2c-8: fd=40], Keeping adjusted sleep multiplier 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
Jan 03 09:46:07 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:46:08 Nexus plasmashell[22455]: QRhiGles2: Context is lost.
Jan 03 09:46:08 Nexus plasmashell[22455]: Graphics device lost, cleaning up scenegraph and releasing RHI
Jan 03 09:46:11 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:46:14 Nexus kded6[936]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:46:15 Nexus kcminit[24790]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
                                      Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
                                      If this causes problems, reconfigure your locale. See the locale(1) manual
                                      for more information.
Jan 03 09:46:15 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:46:19 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:46:19 Nexus kcminit[24790]: Initializing  "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_mouse.so"
Jan 03 09:46:19 Nexus kcminit[24790]: Initializing  "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_touchpad.so"
Jan 03 09:46:19 Nexus kcminit[24790]: kcm_touchpad: Using X11 backend
Jan 03 09:46:23 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:46:26 Nexus kscreenlocker_greet[24135]: QRhiGles2: Context is lost.
Jan 03 09:46:26 Nexus kscreenlocker_greet[24135]: Graphics device lost, cleaning up scenegraph and releasing RHI
Jan 03 09:46:26 Nexus kscreenlocker_greet[24135]: QRhiGles2: Context is lost.
Jan 03 09:46:26 Nexus kscreenlocker_greet[24135]: Graphics device lost, cleaning up scenegraph and releasing RHI
Jan 03 09:46:27 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:46:31 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:46:35 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:46:39 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:46:43 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:46:43 Nexus bitwarden-desktop[1354]: [1354:0103/094643.898454:ERROR:shared_context_state.cc(1244)] SharedContextState context lost via ARB/EXT_robustness. Reset status = GL_GUILTY_CONTEXT_RESET_KHR
Jan 03 09:46:43 Nexus bitwarden-desktop[1354]: [1354:0103/094643.900519:ERROR:gpu_service_impl.cc(1164)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
Jan 03 09:46:43 Nexus kwin_x11[937]: kwin_scene_opengl: A graphics reset attributable to the current GL context occurred.
Jan 03 09:46:43 Nexus bitwarden-desktop[1295]: [1295:0103/094643.915442:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=8704
Jan 03 09:46:44 Nexus kwin_x11[937]: BlurConfig::instance called after the first use - ignoring
Jan 03 09:46:44 Nexus kwin_x11[937]: KscreenConfig::instance called after the first use - ignoring
Jan 03 09:46:44 Nexus kwin_x11[937]: OverviewConfig::instance called after the first use - ignoring
Jan 03 09:46:44 Nexus kwin_x11[937]: SlideConfig::instance called after the first use - ignoring
Jan 03 09:46:44 Nexus kwin_x11[937]: SlidingPopupsConfig::instance called after the first use - ignoring
Jan 03 09:46:44 Nexus kwin_x11[937]: WindowViewConfig::instance called after the first use - ignoring
Jan 03 09:46:44 Nexus kwin_x11[937]: ZoomConfig::instance called after the first use - ignoring
Jan 03 09:46:44 Nexus bitwarden-desktop[24841]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Jan 03 09:46:44 Nexus bitwarden-desktop[24841]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Jan 03 09:46:44 Nexus bitwarden-desktop[24841]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Jan 03 09:46:44 Nexus bitwarden-desktop[24841]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Jan 03 09:46:44 Nexus bitwarden-desktop[24841]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Jan 03 09:46:44 Nexus bitwarden-desktop[24841]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Jan 03 09:46:44 Nexus bitwarden-desktop[24841]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Jan 03 09:46:44 Nexus bitwarden-desktop[24841]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Jan 03 09:46:44 Nexus bitwarden-desktop[24841]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Jan 03 09:46:44 Nexus bitwarden-desktop[24841]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Jan 03 09:46:47 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:46:51 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:46:55 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:46:59 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:47:01 Nexus kscreenlocker_greet[24135]: QRhiGles2: Context is lost.
Jan 03 09:47:01 Nexus kscreenlocker_greet[24135]: Graphics device lost, cleaning up scenegraph and releasing RHI
Jan 03 09:47:01 Nexus kscreenlocker_greet[24135]: QRhiGles2: Context is lost.
Jan 03 09:47:01 Nexus kscreenlocker_greet[24135]: Graphics device lost, cleaning up scenegraph and releasing RHI
Jan 03 09:47:03 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:47:07 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:47:11 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:47:15 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:47:15 Nexus plasmashell[22455]: QRhiGles2: Context is lost.
Jan 03 09:47:15 Nexus plasmashell[22455]: Graphics device lost, cleaning up scenegraph and releasing RHI
Jan 03 09:47:19 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:47:22 Nexus kscreenlocker_greet[24135]: QRhiGles2: Context is lost.
Jan 03 09:47:22 Nexus kscreenlocker_greet[24135]: Graphics device lost, cleaning up scenegraph and releasing RHI
Jan 03 09:47:23 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:47:27 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:47:28 Nexus plasmashell[22455]: QRhiGles2: Context is lost.
Jan 03 09:47:28 Nexus plasmashell[22455]: Graphics device lost, cleaning up scenegraph and releasing RHI
Jan 03 09:47:29 Nexus plasmashell[22455]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jan 03 09:47:29 Nexus plasmashell[22455]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jan 03 09:47:29 Nexus plasmashell[22455]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jan 03 09:47:29 Nexus plasmashell[22455]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jan 03 09:47:29 Nexus plasmashell[22455]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:47:29 Nexus kded6[936]: Service  ":1.470" unregistered
Jan 03 09:47:29 Nexus plasmashell[22455]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jan 03 09:47:29 Nexus plasmashell[22455]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:47:29 Nexus plasmashell[22455]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jan 03 09:47:29 Nexus plasmashell[22455]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:47:29 Nexus plasmashell[22455]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jan 03 09:47:29 Nexus plasmashell[22455]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:47:29 Nexus plasmashell[22455]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:47:29 Nexus plasmashell[22455]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:47:29 Nexus kded6[936]: Registering ":1.480/StatusNotifierItem" to system tray
Jan 03 09:47:29 Nexus plasmashell[22455]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:47:29 Nexus plasmashell[22455]: org.kde.pulseaudio: No object for name "alsa_input.usb-Sonix_Technology_Co.__Ltd._A4tech_FHD_1080P_PC_Camera_SN0001-02.analog-stereo"
Jan 03 09:47:29 Nexus plasmashell[22455]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
Jan 03 09:47:31 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:47:35 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:47:37 Nexus kscreenlocker_greet[24135]: QRhiGles2: Context is lost.
Jan 03 09:47:37 Nexus kscreenlocker_greet[24135]: Graphics device lost, cleaning up scenegraph and releasing RHI
Jan 03 09:47:39 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:47:43 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:47:47 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:47:51 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:47:55 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:47:59 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:48:00 Nexus sudo[24941]: motherfucker_big_scorpio : TTY=pts/2 ; PWD=/home/motherfucker_big_scorpio ; USER=root ; COMMAND=/usr/bin/journalctl -b -e
Jan 03 09:48:00 Nexus sudo[24941]: pam_unix(sudo:session): session opened for user root(uid=0) by motherfucker_big_scorpio(uid=1000)

(2) Right after that I attempt to interact with the taskbar (or the plasma shell) to open a text editor to store this output. One more stalling has occurred. I wait exactly 4 minutes until the taskbar became responsive and immediately performed "sudo journalctl -b -e" again. Here's the output (continued from the previous one above):

Jan 03 09:48:00 Nexus sudo[24941]: motherfucker_big_scorpio : TTY=pts/2 ; PWD=/home/motherfucker_big_scorpio ; USER=root ; COMMAND=/usr/bin/journalctl -b -e
Jan 03 09:48:00 Nexus sudo[24941]: pam_unix(sudo:session): session opened for user root(uid=0) by motherfucker_big_scorpio(uid=1000)
Jan 03 09:48:00 Nexus sudo[24941]: pam_unix(sudo:session): session closed for user root
Jan 03 09:48:03 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:48:07 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:48:11 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:48:14 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:48:18 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:48:22 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:48:26 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:48:30 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:48:34 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:48:38 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:48:42 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:48:46 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:48:50 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:48:54 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:48:58 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:49:02 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:49:06 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:49:10 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:49:14 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:49:18 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:49:22 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:49:26 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:49:30 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:49:34 Nexus kwin_x11[937]: kwin_core: XCB error: 152 (BadDamage), sequence: 4683, resource id: 22134835, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Jan 03 09:49:34 Nexus kwin_x11[937]: kwin_core: XCB error: 3 (BadWindow), sequence: 4684, resource id: 123732035, major code: 129 (SHAPE), minor code: 6 (Input)
Jan 03 09:49:34 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:49:38 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:49:42 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:49:46 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:49:50 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:49:54 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:49:58 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:50:02 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:50:06 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:50:10 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:50:14 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:50:18 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:50:22 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:50:26 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:50:30 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:50:34 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:50:38 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:50:42 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:50:46 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:50:46 Nexus bitwarden-desktop[1295]: 09:50:46.871 › Starting decryption using multithreading with 1 workers for 184 items
Jan 03 09:50:47 Nexus bitwarden-desktop[1295]: 09:50:47.048 › Finished decrypting 184 items using 1 workers
Jan 03 09:50:47 Nexus bitwarden-desktop[1295]: 09:50:47.117 › Finished search indexing
Jan 03 09:50:50 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:50:54 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:50:58 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:51:02 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:51:06 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:51:10 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:51:14 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:51:18 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:51:22 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:51:24 Nexus plasmashell[22455]: QRhiGles2: Context is lost.
Jan 03 09:51:24 Nexus plasmashell[22455]: Graphics device lost, cleaning up scenegraph and releasing RHI
Jan 03 09:51:24 Nexus kwin_x11[937]: qt.dbus.integration: QDBusConnection: couldn't handle call to Teardown, no slot matched
Jan 03 09:51:24 Nexus baloorunner[22820]: qt.dbus.integration: QDBusConnection: couldn't handle call to Teardown, no slot matched
Jan 03 09:51:24 Nexus kwin_x11[937]: qt.dbus.integration: QDBusConnection: couldn't handle call to Teardown, no slot matched
Jan 03 09:51:24 Nexus baloorunner[22820]: qt.dbus.integration: QDBusConnection: couldn't handle call to Teardown, no slot matched
Jan 03 09:51:24 Nexus kwin_x11[937]: qt.dbus.integration: Could not find slot Krunner1Adaptor::Teardown
Jan 03 09:51:24 Nexus baloorunner[22820]: qt.dbus.integration: Could not find slot Krunner1Adaptor::Teardown
Jan 03 09:51:26 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:51:30 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:51:34 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:51:37 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:51:40 Nexus plasmashell[22455]: QRhiGles2: Context is lost.
Jan 03 09:51:40 Nexus plasmashell[22455]: Graphics device lost, cleaning up scenegraph and releasing RHI
Jan 03 09:51:41 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:51:45 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:51:49 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:51:53 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:51:57 Nexus kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Jan 03 09:52:00 Nexus sudo[25119]: motherfucker_big_scorpio : TTY=pts/3 ; PWD=/home/motherfucker_big_scorpio ; USER=root ; COMMAND=/usr/bin/journalctl -b -e
Jan 03 09:52:00 Nexus sudo[25119]: pam_unix(sudo:session): session opened for user root(uid=0) by motherfucker_big_scorpio(uid=1000)

Well?

Last edited by Big Scorpio (2025-01-03 08:59:57)

Offline

#9 2025-01-03 22:38:07

seth
Member
Registered: 2012-09-03
Posts: 61,670

Re: Why is my desktop environment unresponsive for 3 minutes?

I did all that and this USB cannot enable message never stopped printing. It appears, that none of my USB devices are connected to that port:

USB is a bus, not a plug - this might be some internal device :\

If that port number is referring to the frontal USB connectors, I do not have any frontal USB connectors handy, meaning the Motherboard's section responsible for the frontal USB and Audio connectors is not connected to anything.

Can you disable it in the firmware/bios?
There's also not just a cable attached and dangling inside the case?

If I am logically thinking about it, if that port is unused, can i just persistently disable it as a workaround to deal with the delayed IO problem?

You could try to deauthenticate the entire bus, https://www.projectgus.com/2014/09/blac … rom-linux/



However, that error seems a constant and therefore it might be not directly related to your intermittent(?) stalls.

Jan 03 09:46:08 Nexus plasmashell[22455]: QRhiGles2: Context is lost.
Jan 03 09:46:26 Nexus kscreenlocker_greet[24135]: QRhiGles2: Context is lost.
Jan 03 09:46:26 Nexus kscreenlocker_greet[24135]: QRhiGles2: Context is lost.
Jan 03 09:46:43 Nexus bitwarden-desktop[1354]: [1354:0103/094643.898454:ERROR:shared_context_state.cc(1244)] SharedContextState context lost via ARB/EXT_robustness. Reset status = GL_GUILTY_CONTEXT_RESET_KHR
Jan 03 09:46:43 Nexus kwin_x11[937]: kwin_scene_opengl: A graphics reset attributable to the current GL context occurred.
Jan 03 09:47:01 Nexus kscreenlocker_greet[24135]: QRhiGles2: Context is lost.
Jan 03 09:47:01 Nexus kscreenlocker_greet[24135]: QRhiGles2: Context is lost.
Jan 03 09:47:15 Nexus plasmashell[22455]: QRhiGles2: Context is lost.
Jan 03 09:47:22 Nexus kscreenlocker_greet[24135]: QRhiGles2: Context is lost.
Jan 03 09:47:28 Nexus plasmashell[22455]: QRhiGles2: Context is lost.
Jan 03 09:47:37 Nexus kscreenlocker_greet[24135]: QRhiGles2: Context is lost.
Jan 03 09:51:24 Nexus plasmashell[22455]: QRhiGles2: Context is lost.
Jan 03 09:51:40 Nexus plasmashell[22455]: QRhiGles2: Context is lost.

looks worse itr.

Disable bitwarden, see whether you get more stalls.
If so, please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

not just some segments.
Also your Xorg log, https://wiki.archlinux.org/title/Xorg#General

Offline

#10 2025-01-04 19:49:27

Big Scorpio
Member
Registered: 2024-12-15
Posts: 58

Re: Why is my desktop environment unresponsive for 3 minutes?

seth wrote:

If that port number is referring to the frontal USB connectors, I do not have any frontal USB connectors handy, meaning the Motherboard's section responsible for the frontal USB and Audio connectors is not connected to anything.

Can you disable it in the firmware/bios?
There's also not just a cable attached and dangling inside the case?

I didn't see such an ability in my BIOS and my Hardware is still on the modern range. No such cables are connected to nothing.

seth wrote:

looks worse

It gets better (sarcasm).
Now I am not even able to log in anymore. All I see is blank screen and my cursor, that i can move around. Waited for 10 minutes, rebooted several times. Same crap. I'm completely locked out.
Last I remember doing before starting up my Arch Linux OS was performing "pacman -Syu" and "killall plasmashell" (it was stalling again for too long) followed by running plasmashell in the terminal to bring it back up.

seth wrote:

Disable bitwarden, see whether you get more stalls.

Disable as in disabling Bitwarden, the service or disabling the program itself? I couldn't find any documentation about disabling bitwarden as a program. The only alternative meaning I can understand from this is uninstalling bitwarden. We'll cross that bridge once I get inside the system again.

seth wrote:

If so, please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

not just some segments.
Also your Xorg log, https://wiki.archlinux.org/title/Xorg#General

I caught the Xorg log here by jumping to it from the arch install live environment.
http://0x0.st/8iAg.txt
journalctl captures only the live environment itself even if using arch-chroot into the installed OS.

Last edited by Big Scorpio (2025-01-04 20:06:26)

Offline

#11 2025-01-04 20:56:34

seth
Member
Registered: 2012-09-03
Posts: 61,670

Re: Why is my desktop environment unresponsive for 3 minutes?

All I see is blank screen and my cursor, that i can move around.

That's your session or the kwin compositor - not that severe.
You're gonna be able to switch the VT and log into the console look around there.
You can probably even log into a GUI session as different user (this is typically configuration thing or some bogus extension)
The system journal will likely have records of something crashing or errors of any kind.
For X11, try to press "SHIFT+Alt+F12" to toggle the compositor.

https://archlinux.org/packages/extra/x86_64/bitwarden/ doesn't seem to ship a service, so just don't run it and make sure it's not in some autostart system (session restorage)

You're running on the nvidia GPU and your outputs are all attached there.
The intel one would be present for prime, but that's pointless  - you could disable it, but nothing there looks like major trouble and the simpledrm device doesn't show up either.

People have/had issues w/ nvidia fbdev, though.
Try to add "nvidia_drm.modeset=1 nvidia_drm.fbdev=0" to the https://wiki.archlinux.org/title/Kernel_parameters (not! the modprobe.conf)

Offline

#12 2025-01-05 02:09:36

Big Scorpio
Member
Registered: 2024-12-15
Posts: 58

Re: Why is my desktop environment unresponsive for 3 minutes?

seth wrote:

For X11, try to press "SHIFT+Alt+F12" to toggle the compositor.

People have/had issues w/ nvidia fbdev, though.
Try to add "nvidia_drm.modeset=1 nvidia_drm.fbdev=0" to the https://wiki.archlinux.org/title/Kernel_parameters (not! the modprobe.conf)

That key combo did absolutely nothing.
I did try something else. I pressed CTRL + ALT + F3 as I saw being suggested on a linux subreddit.
But that terminal display was shown only *after* i modified the kernel parameters for grub and regenerated grub config.
I was able to enter the OS through the terminal and obtain the system journal. Here it is: https://0x0.st/8iMj.txt

Furthermore on status check on SDDM i saw, that sddm-helper exited with 127. Greeter stopped. SDDM::Auth::HelperExitStatus(127). Although it was enabled and running. Probably normal behavior.
Yes, I'm currently using X11 per old habit. I wonder if using Wayland would work and be less of a pain in the ass?

Offline

#13 2025-01-05 09:08:29

seth
Member
Registered: 2012-09-03
Posts: 61,670

Re: Why is my desktop environment unresponsive for 3 minutes?

That key combo did absolutely nothing.

It does toggle the kwin_x11 compositor, provided kwin_x11 is actually running at the time. You however won't get any visual feedback if the compositor isn't the problem and there're just absolutely no windows to composit.

I pressed CTRL + ALT + F3 as I saw being suggested

seth wrote:

You're gonna be able to switch the VT and log into the console look around there.

Now I am not even able to log in anymore. All I see is blank screen and my cursor

Jan 05 02:53:33 Nexus systemd[1]: Started Session 2 of User motherfucker_big_scorpio.
Jan 05 02:53:33 Nexus systemd[895]: Starting Update XDG user dir configuration...
Jan 05 02:53:33 Nexus login[887]: LOGIN ON tty3 BY motherfucker_big_scorpio

The problem wasn't that you can't login - at least there's no attempt to login from SDDM.
So the problem is likely SDDM and the cause is likely

Jan 05 02:52:37 Nexus sddm[842]: Loading theme configuration from "/usr/share/sddm/themes/elarun/theme.conf"
Jan 05 02:52:37 Nexus sddm-helper[854]: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-ISUCGU --theme /usr/share/sddm/themes/elarun"

CHange that to the breeze theme.

Offline

#14 2025-01-05 14:43:49

Big Scorpio
Member
Registered: 2024-12-15
Posts: 58

Re: Why is my desktop environment unresponsive for 3 minutes?

seth wrote:

It does toggle the kwin_x11 compositor, provided kwin_x11 is actually running at the time. You however won't get any visual feedback if the compositor isn't the problem and there're just absolutely no windows to composit.

Oh, ok, that makes sense. I expected something to happen visually.

seth wrote:

The problem wasn't that you can't login - at least there's no attempt to login from SDDM.
So the problem is likely SDDM and the cause is likely

Jan 05 02:52:37 Nexus sddm[842]: Loading theme configuration from "/usr/share/sddm/themes/elarun/theme.conf"
Jan 05 02:52:37 Nexus sddm-helper[854]: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-ISUCGU --theme /usr/share/sddm/themes/elarun"

CHange that to the breeze theme.

Gah, that figures. I set the [Theme] Current to "breeze" in "/etc/sddm.conf.d/kde_settings.conf" and rebooted. Now i'm back in the desktop environment.

Now, seth, i need a little hand holding here with deauthorizing the seemingly unused USB bus "usb2-port1". How do I target that specific USB bus? From what I dug through I came only so far:

// Listing USB buses here

[motherfucker_big_scorpio@Nexus ~]$ ls /sys/bus/usb/devices/
1-0:1.0  1-2      1-3      1-4      1-4:1.2  1-5.2      1-5.2:1.2  2-0:1.0  2-5.3:1.0  2-5:1.0  3-1:1.0  5-0:1.0  6-0:1.0  usb1  usb4
1-1      1-2:1.0  1-3:1.0  1-4:1.0  1-4:1.3  1-5.2:1.0  1-5.2:1.3  2-5      2-5.4      3-0:1.0  3-1:1.1  5-2      6-2      usb2  usb5
1-1:1.0  1-2:1.1  1-3:1.1  1-4:1.1  1-5      1-5.2:1.1  1-5:1.0    2-5.3    2-5.4:1.0  3-1      4-0:1.0  5-2:1.0  6-2:1.0  usb3  usb6
[motherfucker_big_scorpio@Nexus ~]$ ls /sys/bus/usb/devices/ | grep usb2
usb2
[motherfucker_big_scorpio@Nexus ~]$ ls /sys/bus/usb/devices/ | grep 2-
2-0:1.0
2-5
2-5.3
2-5.3:1.0
2-5.4
2-5.4:1.0
2-5:1.0
[motherfucker_big_scorpio@Nexus ~]$ 

// ChatGPT's suggestion to deauthorize usb2-port1 goes like so
#echo "0" | sudo tee /sys/bus/usb/devices/usb2-1/authorized
// i see no such directory under "/sys/bus/usb/devices/"

// Listing sys classes for USB

[motherfucker_big_scorpio@Nexus ~]$ ls /sys/class/usbmisc/
hiddev0  hiddev1
[motherfucker_big_scorpio@Nexus ~]$ 

// information from udevadm

[motherfucker_big_scorpio@Nexus ~]$ udevadm info -a -p /sys/class/usbmisc/

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/class/usbmisc':
    KERNEL=="usbmisc"
    SUBSYSTEM=="subsystem"
    DRIVER==""

  looking at parent device '/class':
    KERNELS=="class"
    SUBSYSTEMS==""
    DRIVERS==""
    ATTRS{devcoredump/disabled}=="0"
    ATTRS{drm/version}=="drm 1.1.0 20060810"
    ATTRS{zram-control/hot_add}=="(not readable)"
    ATTRS{zram-control/hot_remove}=="(not readable)"

According to ChatGPT, which in my experience has limited usefulness on Advanced Linux System Administration topics, it suggested me to blacklist the USB bus like so as an alternative but I am not sure if the udev blacklist rule is precise enough to disable only usb2-port1 and not the whole usb2 row because disabling the entire usb2 row is not what i want to do.

ChatGPT wrote:

Create a custom udev rule file, e.g., /etc/udev/rules.d/99-disable-usb2-port1.rules
Add the following content to it:

ACTION=="add", SUBSYSTEM=="usb", KERNEL=="usb2", ATTR{authorized}="0"

This will prevent the device from being authorized as soon as it’s connected.

I will also follow your instructions and exit Bitwarden and see when i encounter the next system hiccup and post you the contents of both

sudo journalctl -b | curl -F 'file=@-' 0x0.st
cat /var/log/Xorg.0.log

Or do you no longer need the contents of Xorg the next time as i've provided these prior?

Thanks for the assistance so far.

Offline

#15 2025-01-06 13:09:22

Big Scorpio
Member
Registered: 2024-12-15
Posts: 58

Re: Why is my desktop environment unresponsive for 3 minutes?

Also please note, that a relevant problem to my main problem here is that plasmashell takes long to show up to be responsive and usable when I boot up my computer and log in normally through sddm(-helper). I captured the journalctl contents here: http://0x0.st/8iJ8.txt

See the time delta between when i log in and when the plasma shell first became usable. That's 2 minutes of waiting.
Last time I remembered to quit bitwarden (i have explicitly selected "Quit Bitwarden" on the top dropdown menu) in order to isolate this case of my system's unresponsiveness before shutting down my computer.

Jan 06 13:54:21 Nexus sddm[844]: Authentication for user  "motherfucker_big_scorpio"  successful
Jan 06 13:54:21 Nexus sddm-helper[900]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Jan 06 13:54:21 Nexus sddm-helper[900]: pam_unix(sddm:session): session opened for user motherfucker_big_scorpio(uid=1000) by motherfucker_big_scorpio(uid=0)
Jan 06 13:54:21 Nexus systemd-logind[765]: New session 2 of user motherfucker_big_scorpio.
Jan 06 13:54:21 Nexus systemd[1]: Created slice User Slice of UID 1000.
Jan 06 13:54:21 Nexus sddm-greeter-qt6[871]: Message received from daemon: LoginSucceeded

[...]

Jan 06 13:56:20 Nexus systemd[906]: Started Konsole - Terminal.
Jan 06 13:56:26 Nexus systemd[906]: Started Firefox - Web Browser.

Last edited by Big Scorpio (2025-01-06 13:11:18)

Offline

#16 2025-01-06 17:51:03

seth
Member
Registered: 2012-09-03
Posts: 61,670

Re: Why is my desktop environment unresponsive for 3 minutes?

One rather obvious thing to fix would be your https://wiki.archlinux.org/title/Locale

lcoalectl; locale; locale -a

maybe see https://wiki.archlinux.org/title/Locale … g_language

But there's no obvious stall, plasmashell just takes ages to go through the plasmaoids

Jan 06 13:54:23 Nexus plasmashell[1064]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Jan 06 13:54:26 Nexus plasmashell[1064]: kf.plasma.quick: Applet preload policy set to 1
Jan 06 13:54:26 Nexus plasmashell[1064]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth":
Jan 06 13:54:47 Nexus plasmashell[1064]: Toolbox not loading, toolbox package is either invalid or disabled.
Jan 06 13:54:47 Nexus plasmashell[1064]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth":
Jan 06 13:54:47 Nexus plasmashell[1064]: Toolbox not loading, toolbox package is either invalid or disabled.
Jan 06 13:54:49 Nexus plasmashell[1064]: qt.dbus.integration: QDBusConnection: name 'org.freedesktop.UPower' had owner '' but we thought it was ':1.28'
Jan 06 13:55:27 Nexus plasmashell[1064]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
Jan 06 13:55:27 Nexus plasmashell[1064]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
Jan 06 13:55:43 Nexus plasmashell[1064]: qt.dbus.integration: Could not connect "org.cups.cupsd.Notifier" to PrinterFinishingsChanged(QString, QString, QString, uint, QString, bool) :
Jan 06 13:55:43 Nexus plasmashell[1064]: kde.plasmashell: requesting unexisting screen available rect -1
Jan 06 13:55:43 Nexus plasmashell[1064]: kde.plasmashell: requesting unexisting screen available rect -1
Jan 06 13:55:43 Nexus plasmashell[1064]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
Jan 06 13:56:07 Nexus plasmashell[1064]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
Jan 06 13:56:07 Nexus plasmashell[1064]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/FullRepresentation.qml:94:5: QML ScrollView: Binding loop detected for property "contentWidth":
Jan 06 13:56:07 Nexus plasmashell[1064]: qrc:/qt/qml/org/kde/plasma/components/ScrollView.qml:53:29: QML ScrollBar: Binding loop detected for property "visible":
Jan 06 13:56:07 Nexus plasmashell[1064]: qrc:/qt/qml/org/kde/plasma/components/ScrollView.qml:53:29: QML ScrollBar: Binding loop detected for property "visible":
Jan 06 13:56:07 Nexus plasmashell[1064]: error getting max keyboard brightness via dbus QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/org/kde/Solid/PowerManagement/Actions/KeyboardBrightnessControl'")
Jan 06 13:56:07 Nexus plasmashell[1064]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
Jan 06 13:56:07 Nexus plasmashell[1064]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
Jan 06 13:56:14 Nexus plasmashell[1064]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
Jan 06 13:56:37 Nexus plasmashell[1064]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Jan 06 13:57:03 Nexus plasmashell[1064]: kf.kio.core: "/usr/share/applications/bitwarden.desktop" contains supported protocols but doesn't use %u or %U in its Exec line! This is inconsistent.

while you're getting IO errors from that usb device.

it suggested me to blacklist the USB bus

Blacklisting usbcore will certainl rid you of that probm. And the usb bus.

ChatGPT's suggestion to deauthorize usb2-port1 goes like so

You'd have to block the entire hub, usb2 - did you try to remove the external drives that seem attached there?

Offline

#17 2025-01-06 21:15:39

Big Scorpio
Member
Registered: 2024-12-15
Posts: 58

Re: Why is my desktop environment unresponsive for 3 minutes?

seth wrote:

One rather obvious thing to fix would be your https://wiki.archlinux.org/title/Locale

lcoalectl; locale; locale -a

maybe see https://wiki.archlinux.org/title/Locale … g_language

I was wondering about seeing that too just recently. Didn't think it would be problematic since Qt uses C UTF-8 as fallback?

[motherfucker_big_scorpio@Nexus ~]$ lcoalectl; locale; locale -a
bash: lcoalectl: command not found
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=en_CH.UTF-8
LC_TIME=en_CH.UTF-8
LC_COLLATE=en_US.UTF-8
LC_MONETARY=pt_PT.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_PAPER=en_CH.UTF-8
LC_NAME=C
LC_ADDRESS=C
LC_TELEPHONE=C
LC_MEASUREMENT=C
LC_IDENTIFICATION=en_US.UTF-8
LC_ALL=

C
C.utf8
de_DE
de_DE@euro
de_DE.iso88591
de_DE.iso885915@euro
de_DE.utf8
deutsch
en_US.utf8
german
POSIX

What I did now was editing the /etc/locale.conf accordingly. Here's what I've got:

[motherfucker_big_scorpio@Nexus ~]$ sudo locale-gen en_CH.UTF-8
Generating locales...
  de_DE.UTF-8... done
  de_DE.ISO-8859-1... done
  de_DE.ISO-8859-15@euro... done
  en_US.UTF-8... done
Generation complete.

# edit locale.conf
[motherfucker_big_scorpio@Nexus ~]$ sudo vim /etc/locale.conf

# before
[motherfucker_big_scorpio@Nexus ~]$ sudo locale
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=en_CH.UTF-8
LC_TIME=en_CH.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=pt_PT.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=en_CH.UTF-8
LC_NAME=C
LC_ADDRESS=C
LC_TELEPHONE=C
LC_MEASUREMENT=C
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

# after
[motherfucker_big_scorpio@Nexus ~]$ cat /etc/locale.conf 
LANG=en_US.UTF-8
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=en_CH.UTF-8
LC_TIME=en_CH.UTF-8
LC_COLLATE=en_US.UTF-8
LC_MONETARY=pt_PT.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_PAPER=en_CH.UTF-8
LC_NAME=en_CH.UTF-8
LC_ADDRESS=en_CH.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_CH.UTF-8
LC_IDENTIFICATION=en_CH.UTF-8

[motherfucker_big_scorpio@Nexus ~]$ localectl
System Locale: LANG=en_US.UTF-8
               LC_NUMERIC=en_CH.UTF-8
               LC_TIME=en_CH.UTF-8
               LC_MONETARY=pt_PT.UTF-8
               LC_PAPER=en_CH.UTF-8
               LC_NAME=en_CH.UTF-8
               LC_ADDRESS=en_CH.UTF-8
               LC_MEASUREMENT=en_CH.UTF-8
               LC_IDENTIFICATION=en_CH.UTF-8
    VC Keymap: us
   X11 Layout: (unset)           

Not sure if that'll make these warnings disappear.

seth wrote:

But there's no obvious stall, plasmashell just takes ages to go through the plasmaoids

I don't remember KDE Plasma being that slow back in 2018-2019 on CentOS 7. It was as quick as Windows.
Do I take this particular issue up with the KDE community or developers then since that's their part?

seth wrote:

it suggested me to blacklist the USB bus

Blacklisting usbcore will certainl rid you of that probm. And the usb bus.
You'd have to block the entire hub, usb2 - did you try to remove the external drives that seem attached there?

I'd really hate to do this.
But yes, I did remove all connected USB devices/cables from it and in dmesg the spam message never stopped.
However I've got some news on that matter. I was able to identify which bus & ports correspond to the USB connectors like so:

[motherfucker_big_scorpio@Nexus ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 045b:0209 Hitachi, Ltd 
Bus 001 Device 004: ID 1a2c:4b5e China Resource Semico Co., Ltd USB Keyboard
Bus 001 Device 005: ID 09da:2696 A4Tech Co., Ltd. A4tech FHD 1080P PC Camera
Bus 001 Device 006: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub             
Bus 001 Device 007: ID 1395:1000 DSEA A/S Sennheiser 3D G4ME1
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub             
Bus 002 Device 003: ID 0781:55a3 SanDisk Corp.  SanDisk 3.2Gen1
Bus 002 Device 004: ID 0781:5583 SanDisk Corp. Ultra Fit
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 18f8:0f99 [Maxxter] Optical gaming mouse
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 002: ID 0451:8140 Texas Instruments, Inc. TUSB8041 4-Port Hub

Bus 2 in my case is an external USB Hub device, that splits into 4 more USB 3.0 sockets (or ports as the system calls it), connected to the backpanel of my motherboard. All 4 sockets were connected to something:
Port 1 -> USB to USB Type C datalink cable & charging device for my smartphone, which was not connected to anything (and I can't make data transfers with Linux from/to it out of the box)
Port 2 -> USB to external Soundcard for Audio
Port 3 & 4 -> USB Flash Drives

I disconnected that USB to USB Type C Cable, that was not connected to anything. dmesg still reports

usb usb2-port1: Cannot enable. Maybe the USB cable is bad?

???

Offline

#18 2025-01-07 10:27:18

seth
Member
Registered: 2012-09-03
Posts: 61,670

Re: Why is my desktop environment unresponsive for 3 minutes?

en_CH isn't a locale?

I disconnected that USB to USB Type C Cable, that was not connected to anything. dmesg still reports

Even after a reboot?

Bus 2 in my case is an external USB Hub device

Have you tried to remove that thing entirely?

(We primarily want to know whether the unresponsive usb is the source of your plasma slowdowns)

Offline

#19 2025-01-07 19:53:47

Big Scorpio
Member
Registered: 2024-12-15
Posts: 58

Re: Why is my desktop environment unresponsive for 3 minutes?

seth wrote:

en_CH isn't a locale?

I thought so too. ChatGPT doesn't know Linux all that much. I should take it less serious from that AI. Disregard this part.

seth wrote:

I disconnected that USB to USB Type C Cable, that was not connected to anything. dmesg still reports

Even after a reboot?

Yes. I tested that today. dmesg is still spamming that.

seth wrote:

Have you tried to remove that thing entirely?

(We primarily want to know whether the unresponsive usb is the source of your plasma slowdowns)

That's what I intend to do next. Disconnecting the USB hub, reboot and then will report back.

In the meantime I have one more update with the stalling. Conditions are:
USB Hub connected. Port 1 of USB Hub is free (no cables attached there).
Bitwarden was quit before I went AFK at 17:20

Came back from being AFK at 19:49, the sddm login screen took it's sweet time to show itself in order to log me in. I logged in.
plasmashell was stalling again for almost 3 minutes. Later it even crashed when i clicked on the Application Launcher (i pressed the Windows key on the keyboard to make it happen).

Journalctl -b (does not include plasmashell crash output. I'll post it separately) -> http://0x0.st/8idV.txt

Here's the journalctl -b part of plasmashell crash

Jan 07 20:34:17 Nexus plasmashell[1045]: QRhiGles2: Context is lost.
Jan 07 20:34:17 Nexus plasmashell[1045]: Graphics device lost, cleaning up scenegraph and releasing RHI
Jan 07 20:34:17 Nexus plasmashell[1045]: KCrash: Application 'plasmashell' crashing... crashRecursionCounter = 2
Jan 07 20:34:18 Nexus systemd-coredump[22115]: Process 1045 (plasmashell) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Jan 07 20:34:18 Nexus systemd[1]: Started Process Core Dump (PID 22115/UID 0).
Jan 07 20:34:18 Nexus systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Jan 07 20:34:18 Nexus drkonqi-coredump-processor[22118]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
                                                         Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
                                                         If this causes problems, reconfigure your locale. See the locale(1) manual
                                                         for more information.
Jan 07 20:34:20 Nexus systemd-coredump[22117]: [?] Process 1045 (plasmashell) of user 1000 dumped core.
                                               
                                               Stack trace of thread 2067:
                                               #0  0x00007619d3d693f4 n/a (libc.so.6 + 0x963f4)
                                               #1  0x00007619d3d10120 raise (libc.so.6 + 0x3d120)
                                               #2  0x00007619d6b822a1 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x62a1)
                                               #3  0x00007619d3d101d0 n/a (libc.so.6 + 0x3d1d0)
                                               #4  0x00007619d4de3df0 _ZN14QOpenGLContext11doneCurrentEv (libQt6Gui.so.6 + 0x4f2df0)
                                               #5  0x00007619d4dee912 n/a (libQt6Gui.so.6 + 0x4fd912)
                                               #6  0x00007619d451af2c _ZN18QThreadStorageData6finishEPPv (libQt6Core.so.6 + 0x2e1f2c)
                                               #7  0x00007619d4665499 n/a (libQt6Core.so.6 + 0x42c499)
                                               #8  0x00007619d45120d6 n/a (libQt6Core.so.6 + 0x2d90d6)
                                               #9  0x00007619d3d6739d n/a (libc.so.6 + 0x9439d)
                                               #10 0x00007619d3dec49c n/a (libc.so.6 + 0x11949c)
                                               
                                               Stack trace of thread 1065:
                                               #0  0x00007619d3dde63d __poll (libc.so.6 + 0x10b63d)
                                               #1  0x00007619d6b9520b n/a (libxcb.so.1 + 0xd20b)
                                               #2  0x00007619d6b96f3d xcb_wait_for_event (libxcb.so.1 + 0xef3d)
                                               #3  0x00007619cd884d19 n/a (libQt6XcbQpa.so.6 + 0x4ed19)
                                               #4  0x00007619d45120cd n/a (libQt6Core.so.6 + 0x2d90cd)
                                               #5  0x00007619d3d6739d n/a (libc.so.6 + 0x9439d)
                                               #6  0x00007619d3dec49c n/a (libc.so.6 + 0x11949c)
                                               
                                               Stack trace of thread 1722:
                                               #0  0x00007619d3ddebb0 ppoll (libc.so.6 + 0x10bbb0)
                                               #1  0x00007619d2d67327 n/a (libglib-2.0.so.0 + 0xc0327)
                                               #2  0x00007619d2d03a55 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca55)
                                               #3  0x00007619d45fb2fd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3c22fd)
                                               #4  0x00007619d439aee6 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x161ee6)
                                               #5  0x00007619d4490f22 _ZN7QThread4execEv (libQt6Core.so.6 + 0x257f22)
                                               #6  0x00007619d5cec538 n/a (libQt6Quick.so.6 + 0x37e538)
                                               #7  0x00007619d45120cd n/a (libQt6Core.so.6 + 0x2d90cd)
                                               #8  0x00007619d3d6739d n/a (libc.so.6 + 0x9439d)
                                               #9  0x00007619d3dec49c n/a (libc.so.6 + 0x11949c)
                                               
                                               Stack trace of thread 1182:
                                               #0  0x00007619d3ddebb0 ppoll (libc.so.6 + 0x10bbb0)
                                               #1  0x00007619d2d67327 n/a (libglib-2.0.so.0 + 0xc0327)
                                               #2  0x00007619d2d03a55 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca55)
                                               #3  0x00007619d45fb2fd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3c22fd)
                                               #4  0x00007619d439aee6 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x161ee6)
                                               #5  0x00007619d4491082 _ZN7QThread3runEv (libQt6Core.so.6 + 0x258082)
                                               #6  0x00007619d45120cd n/a (libQt6Core.so.6 + 0x2d90cd)
                                               #7  0x00007619d3d6739d n/a (libc.so.6 + 0x9439d)
                                               #8  0x00007619d3dec49c n/a (libc.so.6 + 0x11949c)
                                               
                                               Stack trace of thread 1045:
                                               #0  0x00007619d3d63a19 n/a (libc.so.6 + 0x90a19)
                                               #1  0x00007619d3d66479 pthread_cond_wait (libc.so.6 + 0x93479)
                                               #2  0x00007619d450c31b _ZN7QThread4waitE14QDeadlineTimer (libQt6Core.so.6 + 0x2d331b)
                                               #3  0x00007619d5db6860 n/a (libQt6Quick.so.6 + 0x448860)
                                               #4  0x00007619d4ae1828 _ZN7QWindow5eventEP6QEvent (libQt6Gui.so.6 + 0x1f0828)
                                               #5  0x00007619d637578a _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfe78a)
                                               #6  0x00007619d4390ac8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x157ac8)
                                               #7  0x00007619d4ade465 _ZN14QWindowPrivate10setVisibleEb (libQt6Gui.so.6 + 0x1ed465)
                                               #8  0x00007619d564d9e3 n/a (libQt6Qml.so.6 + 0x26b9e3)
                                               #9  0x00007619d5667c68 n/a (libQt6Qml.so.6 + 0x285c68)
                                               #10 0x00007619d566412d _ZN11QQmlBinding8doUpdateERKN24QQmlJavaScriptExpression13DeleteWatcherE6QFlagsIN16QQmlPropertyData9WriteFlagEERN3QV45ScopeE (libQt6Qml.so.6 + 0x28212d)
                                               #11 0x00007619d56635ee _ZN11QQmlBinding6updateE6QFlagsIN16QQmlPropertyData9WriteFlagEE (libQt6Qml.so.6 + 0x2815ee)
                                               #12 0x00007619d56e981c _ZN12QQmlNotifier10emitNotifyEP20QQmlNotifierEndpointPPv (libQt6Qml.so.6 + 0x30781c)
                                               #13 0x00007619d43ea82a n/a (libQt6Core.so.6 + 0x1b182a)
                                               #14 0x00007619d6c6a855 _ZN11PlasmaQuick15AppletQuickItem15expandedChangedEb (libPlasmaQuick.so.6 + 0x25855)
                                               #15 0x00007619d6c72619 _ZN11PlasmaQuick15AppletQuickItem11qt_metacallEN11QMetaObject4CallEiPPv (libPlasmaQuick.so.6 + 0x2d619)
                                               #16 0x00007619d6ca0e9f n/a (libPlasmaQuick.so.6 + 0x5be9f)
                                               #17 0x00007619d564da29 n/a (libQt6Qml.so.6 + 0x26ba29)
                                               #18 0x00007619d570b924 _ZN19QQmlPropertyPrivate5writeEP7QObjectRK16QQmlPropertyDataRK8QVariantRK14QQmlRefPointerI15QQmlContextDataE6QFlagsINS2_9WriteFlagEE (libQt6Qml.so.6 + 0x329924)
                                               #19 0x00007619d55bd308 _ZN3QV414QObjectWrapper11setPropertyEPNS_15ExecutionEngineEP7QObjectPK16QQmlPropertyDataRKNS_5ValueE (libQt6Qml.so.6 + 0x1db308)
                                               #20 0x00007619d55bdabe _ZN3QV414QObjectWrapper14setQmlPropertyEPNS_15ExecutionEngineERK14QQmlRefPointerI15QQmlContextDataEP7QObjectPNS_6StringE6QFlagsINS0_4FlagEERKNS_5ValueE (libQt6Qml.so.6 + 0x1dbabe)
                                               #21 0x00007619d55bdc4b _ZN3QV414QObjectWrapper10virtualPutEPNS_7ManagedENS_11PropertyKeyERKNS_5ValueEPS4_ (libQt6Qml.so.6 + 0x1dbc4b)
                                               #22 0x00007619d5594c4c _ZN3QV46Lookup14setterFallbackEPS0_PNS_15ExecutionEngineERNS_5ValueERKS4_ (libQt6Qml.so.6 + 0x1b2c4c)
                                               #23 0x00007619af32ecf9 n/a (n/a + 0x0)
                                               #24 0x00007619d563806f n/a (libQt6Qml.so.6 + 0x25606f)
                                               #25 0x00007619d55712a4 n/a (libQt6Qml.so.6 + 0x18f2a4)
                                               #26 0x00007619d557afe9 _ZN3QV48Function4callEP7QObjectPPvPK9QMetaTypeiPNS_16ExecutionContextE (libQt6Qml.so.6 + 0x198fe9)
                                               #27 0x00007619d56c7a64 _ZN24QQmlJavaScriptExpression8evaluateEPPvPK9QMetaTypei (libQt6Qml.so.6 + 0x2e5a64)
                                               #28 0x00007619d566929d _ZN25QQmlBoundSignalExpression8evaluateEPPv (libQt6Qml.so.6 + 0x28729d)
                                               #29 0x00007619d566e65f n/a (libQt6Qml.so.6 + 0x28c65f)
                                               #30 0x00007619d56e981c _ZN12QQmlNotifier10emitNotifyEP20QQmlNotifierEndpointPPv (libQt6Qml.so.6 + 0x30781c)
                                               #31 0x00007619d43ea82a n/a (libQt6Core.so.6 + 0x1b182a)
                                               #32 0x00007619d5b3c029 _ZN15QQuickMouseArea10setPressedEN2Qt11MouseButtonEbNS0_16MouseEventSourceE (libQt6Quick.so.6 + 0x1ce029)
                                               #33 0x00007619d5b3c303 _ZN15QQuickMouseArea17mouseReleaseEventEP11QMouseEvent (libQt6Quick.so.6 + 0x1ce303)
                                               #34 0x00007619d5b11675 _ZN17QQuickItemPrivate19deliverPointerEventEP6QEvent (libQt6Quick.so.6 + 0x1a3675)
                                               #35 0x00007619d5b118cb _ZN10QQuickItem5eventEP6QEvent (libQt6Quick.so.6 + 0x1a38cb)
                                               #36 0x00007619d637578a _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfe78a)
                                               #37 0x00007619d4390ac8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x157ac8)
                                               #38 0x00007619d5cd4460 _ZN26QQuickDeliveryAgentPrivate27deliverMatchingPointsToItemEP10QQuickItembP13QPointerEventb (libQt6Quick.so.6 + 0x366460)
                                               #39 0x00007619d5cd4b12 _ZN26QQuickDeliveryAgentPrivate20deliverUpdatedPointsEP13QPointerEvent (libQt6Quick.so.6 + 0x366b12)
                                               #40 0x00007619d5cd6ab3 _ZN26QQuickDeliveryAgentPrivate19deliverPointerEventEP13QPointerEvent (libQt6Quick.so.6 + 0x368ab3)
                                               #41 0x00007619d5cd7bad _ZN26QQuickDeliveryAgentPrivate16handleMouseEventEP11QMouseEvent (libQt6Quick.so.6 + 0x369bad)
                                               #42 0x00007619d5cd8353 _ZN19QQuickDeliveryAgent5eventEP6QEvent (libQt6Quick.so.6 + 0x36a353)
                                               #43 0x00007619d5bcc9dc _ZN12QQuickWindow5eventEP6QEvent (libQt6Quick.so.6 + 0x25e9dc)
                                               #44 0x00005711cea85aac n/a (n/a + 0x0)
                                               #45 0x00007619d637578a _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfe78a)
                                               #46 0x00007619d4390ac8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x157ac8)
                                               #47 0x00007619d4a7852b _ZN22QGuiApplicationPrivate17processMouseEventEPN29QWindowSystemInterfacePrivate10MouseEventE (libQt6Gui.so.6 + 0x18752b)
                                               #48 0x00007619d4af3b44 _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Gui.so.6 + 0x202b44)
                                               #49 0x00007619cd887c67 n/a (libQt6XcbQpa.so.6 + 0x51c67)
                                               #50 0x00007619d2d04559 n/a (libglib-2.0.so.0 + 0x5d559)
                                               #51 0x00007619d2d67257 n/a (libglib-2.0.so.0 + 0xc0257)
                                               #52 0x00007619d2d03a55 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca55)
                                               #53 0x00007619d45fb2fd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3c22fd)
                                               #54 0x00007619d439aee6 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x161ee6)
                                               #55 0x00007619d4391f4f _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x158f4f)
                                               #56 0x00005711cea60148 n/a (n/a + 0x0)
                                               #57 0x00007619d3cf8e08 n/a (libc.so.6 + 0x25e08)
                                               #58 0x00007619d3cf8ecc __libc_start_main (libc.so.6 + 0x25ecc)
                                               #59 0x00005711cea60665 n/a (n/a + 0x0)
                                               ELF object binary architecture: AMD x86-64
Jan 07 20:34:20 Nexus systemd[1]: systemd-coredump@1-22115-0.service: Deactivated successfully.
Jan 07 20:34:20 Nexus systemd[1]: systemd-coredump@1-22115-0.service: Consumed 2.116s CPU time, 698.6M memory peak.
Jan 07 20:34:20 Nexus systemd[901]: plasma-plasmashell.service: Main process exited, code=dumped, status=11/SEGV
Jan 07 20:34:20 Nexus systemd[901]: plasma-plasmashell.service: Failed with result 'core-dump'.
Jan 07 20:34:20 Nexus systemd[901]: plasma-plasmashell.service: Consumed 3min 42.455s CPU time, 566M memory peak, 166.7M memory swap peak.
Jan 07 20:34:20 Nexus systemd[901]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 1.
Jan 07 20:34:20 Nexus drkonqi-coredump-processor[22118]: "/usr/bin/plasmashell" 1045 "/var/lib/systemd/coredump/core.plasmashell.1000.25e36c1cb4d24dd4baff79cd907c78ed.1045.1736278457000000.zst"
Jan 07 20:34:20 Nexus systemd[901]: Starting KDE Plasma Workspace...

and the dump

Application: plasmashell (plasmashell), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  <https://debuginfod.archlinux.org>
Enable debuginfod for this session? (y or [n]) [answered N; input not from terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.

warning: Can't open file /memfd:JSGCHeap:QtQml (deleted) during file-backed mapping note processing

warning: Can't open file /memfd:JITCode:QtQml (deleted) during file-backed mapping note processing

warning: Can't open file /memfd:unknown-usage:QtQml (deleted) during file-backed mapping note processing

warning: Can't open file /memfd:/.nvidia_drv.XXXXXX (deleted) during file-backed mapping note processing

warning: Can't open file /memfd:/.glXXXXXX (deleted) during file-backed mapping note processing

warning: Can't open file /memfd:xorg (deleted) during file-backed mapping note processing

warning: Can't open file /memfd:JSVMStack:QtQml (deleted) during file-backed mapping note processing

warning: Can't open file /home/motherfucker_big_scorpio/.cache/plasma_theme_default.kcache (deleted) during file-backed mapping note processing

warning: Can't open file /memfd:pulseaudio (deleted) during file-backed mapping note processing
[New LWP 2067]
[New LWP 1065]
[New LWP 1722]
[New LWP 1182]
[New LWP 1045]
[New LWP 1064]
[New LWP 22054]
[New LWP 1862]
[New LWP 2009]
[New LWP 22056]
[New LWP 1871]
[New LWP 1865]
[New LWP 1887]
[New LWP 1891]
[New LWP 1889]
[New LWP 2069]
[New LWP 7460]
[New LWP 22053]
[New LWP 22055]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007619d3d693f4 in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7619afbff6c0 (LWP 2067))]
Cannot QML trace cores :(
/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py:516: DeprecationWarning: datetime.datetime.utcfromtimestamp() is deprecated and scheduled for removal in a future version. Use timezone-aware objects to represent datetimes in UTC: datetime.datetime.fromtimestamp(timestamp, datetime.UTC).
  boot_time = datetime.utcfromtimestamp(psutil.boot_time()).strftime('%Y-%m-%dT%H:%M:%S')
/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py:533: DeprecationWarning: datetime.datetime.utcnow() is deprecated and scheduled for removal in a future version. Use timezone-aware objects to represent datetimes in UTC: datetime.datetime.now(datetime.UTC).
  'timestamp': datetime.utcnow().isoformat(),
[Current thread is 1 (Thread 0x7619afbff6c0 (LWP 2067))]

Thread 19 (Thread 0x761973fff6c0 (LWP 22055)):
#0  0x00007619d3d63a19 in ?? () from /usr/lib/libc.so.6
#1  0x00007619d3d667e2 in pthread_cond_timedwait () from /usr/lib/libc.so.6
#2  0x00007619d45173c8 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt6Core.so.6
#3  0x00007619d4518ad5 in ?? () from /usr/lib/libQt6Core.so.6
#4  0x00007619d45120cd in ?? () from /usr/lib/libQt6Core.so.6
#5  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#6  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 18 (Thread 0x76194bfff6c0 (LWP 22053)):
#0  0x00007619d3d63a19 in ?? () from /usr/lib/libc.so.6
#1  0x00007619d3d667e2 in pthread_cond_timedwait () from /usr/lib/libc.so.6
#2  0x00007619d45173c8 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt6Core.so.6
#3  0x00007619d4518ad5 in ?? () from /usr/lib/libQt6Core.so.6
#4  0x00007619d45120cd in ?? () from /usr/lib/libQt6Core.so.6
#5  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#6  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 17 (Thread 0x76196a9ea6c0 (LWP 7460)):
#0  0x00007619d3d63a19 in ?? () from /usr/lib/libc.so.6
#1  0x00007619d3d66479 in pthread_cond_wait () from /usr/lib/libc.so.6
#2  0x00007619d4517440 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt6Core.so.6
#3  0x00007619d5db252a in ?? () from /usr/lib/libQt6Quick.so.6
#4  0x00007619d45120cd in ?? () from /usr/lib/libQt6Core.so.6
#5  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#6  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 16 (Thread 0x761953fff6c0 (LWP 2069)):
#0  0x00007619d3d63a19 in ?? () from /usr/lib/libc.so.6
#1  0x00007619d3d66479 in pthread_cond_wait () from /usr/lib/libc.so.6
#2  0x00007619d4517440 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt6Core.so.6
#3  0x00007619d5db252a in ?? () from /usr/lib/libQt6Quick.so.6
#4  0x00007619d45120cd in ?? () from /usr/lib/libQt6Core.so.6
#5  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#6  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 15 (Thread 0x761994eec6c0 (LWP 1889)):
#0  0x00007619d3d63a19 in ?? () from /usr/lib/libc.so.6
#1  0x00007619d3d66479 in pthread_cond_wait () from /usr/lib/libc.so.6
#2  0x00007619d4517440 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt6Core.so.6
#3  0x00007619d5db252a in ?? () from /usr/lib/libQt6Quick.so.6
#4  0x00007619d45120cd in ?? () from /usr/lib/libQt6Core.so.6
#5  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#6  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 14 (Thread 0x76197ffff6c0 (LWP 1891)):
#0  0x00007619d3d63a19 in ?? () from /usr/lib/libc.so.6
#1  0x00007619d3d66479 in pthread_cond_wait () from /usr/lib/libc.so.6
#2  0x00007619d4517440 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt6Core.so.6
#3  0x00007619d5db252a in ?? () from /usr/lib/libQt6Quick.so.6
#4  0x00007619d45120cd in ?? () from /usr/lib/libQt6Core.so.6
#5  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#6  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 13 (Thread 0x761995b326c0 (LWP 1887)):
#0  0x00007619d3dde63d in poll () from /usr/lib/libc.so.6
#1  0x00007619c693f987 in ?? () from /usr/lib/libnvidia-glcore.so.565.77
#2  0x00007619c692e864 in ?? () from /usr/lib/libnvidia-glcore.so.565.77
#3  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#4  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 12 (Thread 0x7619978e16c0 (LWP 1865)):
#0  0x00007619d3ddebb0 in ppoll () from /usr/lib/libc.so.6
#1  0x00007619d2d67327 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007619d2d03a55 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007619d45fb2fd in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt6Core.so.6
#4  0x00007619d439aee6 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt6Core.so.6
#5  0x00007619d4490f22 in QThread::exec() () from /usr/lib/libQt6Core.so.6
#6  0x0000761997e798b0 in KCupsConnection::run() () from /usr/lib/libkcupslib.so.6.2.5
#7  0x00007619d45120cd in ?? () from /usr/lib/libQt6Core.so.6
#8  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#9  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 11 (Thread 0x76199660f6c0 (LWP 1871)):
#0  0x00007619d3d63a19 in ?? () from /usr/lib/libc.so.6
#1  0x00007619d3d66479 in pthread_cond_wait () from /usr/lib/libc.so.6
#2  0x00007619d4517440 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt6Core.so.6
#3  0x00007619d5db252a in ?? () from /usr/lib/libQt6Quick.so.6
#4  0x00007619d45120cd in ?? () from /usr/lib/libQt6Core.so.6
#5  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#6  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 10 (Thread 0x76197ebff6c0 (LWP 22056)):
#0  0x00007619d3d63a19 in ?? () from /usr/lib/libc.so.6
#1  0x00007619d3d667e2 in pthread_cond_timedwait () from /usr/lib/libc.so.6
#2  0x00007619d45173c8 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt6Core.so.6
#3  0x00007619d4518ad5 in ?? () from /usr/lib/libQt6Core.so.6
#4  0x00007619d45120cd in ?? () from /usr/lib/libQt6Core.so.6
#5  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#6  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 9 (Thread 0x76196b1eb6c0 (LWP 2009)):
#0  0x00007619d3d63a19 in ?? () from /usr/lib/libc.so.6
#1  0x00007619d3d66479 in pthread_cond_wait () from /usr/lib/libc.so.6
#2  0x00007619d4517440 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt6Core.so.6
#3  0x00007619d5db252a in ?? () from /usr/lib/libQt6Quick.so.6
#4  0x00007619d45120cd in ?? () from /usr/lib/libQt6Core.so.6
#5  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#6  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 8 (Thread 0x7619b53616c0 (LWP 1862)):
#0  0x00007619d3dde63d in poll () from /usr/lib/libc.so.6
#1  0x00007619b473aa78 in ?? () from /usr/lib/libpulse.so.0
#2  0x00007619b4724654 in pa_mainloop_poll () from /usr/lib/libpulse.so.0
#3  0x00007619b472e7c5 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#4  0x00007619b472e891 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#5  0x00007619b473fbd4 in ?? () from /usr/lib/libpulse.so.0
#6  0x00007619b46df34f in ?? () from /usr/lib/pulseaudio/libpulsecommon-17.0.so
#7  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#8  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7619697ff6c0 (LWP 22054)):
#0  0x00007619d3d63a19 in ?? () from /usr/lib/libc.so.6
#1  0x00007619d3d667e2 in pthread_cond_timedwait () from /usr/lib/libc.so.6
#2  0x00007619d45173c8 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt6Core.so.6
#3  0x00007619d4518ad5 in ?? () from /usr/lib/libQt6Core.so.6
#4  0x00007619d45120cd in ?? () from /usr/lib/libQt6Core.so.6
#5  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#6  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7619cd75c6c0 (LWP 1064)):
#0  0x00007619d3ddebb0 in ppoll () from /usr/lib/libc.so.6
#1  0x00007619d2d67327 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007619d2d03a55 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007619d45fb2fd in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt6Core.so.6
#4  0x00007619d439aee6 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt6Core.so.6
#5  0x00007619d4490f22 in QThread::exec() () from /usr/lib/libQt6Core.so.6
#6  0x00007619d48645ae in ?? () from /usr/lib/libQt6DBus.so.6
#7  0x00007619d45120cd in ?? () from /usr/lib/libQt6Core.so.6
#8  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#9  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7619cdcc3a00 (LWP 1045)):
#0  0x00007619d3d63a19 in ?? () from /usr/lib/libc.so.6
#1  0x00007619d3d66479 in pthread_cond_wait () from /usr/lib/libc.so.6
#2  0x00007619d450c31b in QThread::wait(QDeadlineTimer) () from /usr/lib/libQt6Core.so.6
#3  0x00007619d5db6860 in ?? () from /usr/lib/libQt6Quick.so.6
#4  0x00007619d4ae1828 in QWindow::event(QEvent*) () from /usr/lib/libQt6Gui.so.6
#5  0x00007619d637578a in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt6Widgets.so.6
#6  0x00007619d4390ac8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt6Core.so.6
#7  0x00007619d4ade465 in QWindowPrivate::setVisible(bool) () from /usr/lib/libQt6Gui.so.6
#8  0x00007619d564d9e3 in ?? () from /usr/lib/libQt6Qml.so.6
#9  0x00007619d5667c68 in ?? () from /usr/lib/libQt6Qml.so.6
#10 0x00007619d566412d in QQmlBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&, QFlags<QQmlPropertyData::WriteFlag>, QV4::Scope&) () from /usr/lib/libQt6Qml.so.6
#11 0x00007619d56635ee in QQmlBinding::update(QFlags<QQmlPropertyData::WriteFlag>) () from /usr/lib/libQt6Qml.so.6
#12 0x00007619d56e981c in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /usr/lib/libQt6Qml.so.6
#13 0x00007619d43ea82a in ?? () from /usr/lib/libQt6Core.so.6
#14 0x00007619d6c6a855 in PlasmaQuick::AppletQuickItem::expandedChanged(bool) () from /usr/lib/libPlasmaQuick.so.6
#15 0x00007619d6c72619 in PlasmaQuick::AppletQuickItem::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libPlasmaQuick.so.6
#16 0x00007619d6ca0e9f in ?? () from /usr/lib/libPlasmaQuick.so.6
#17 0x00007619d564da29 in ?? () from /usr/lib/libQt6Qml.so.6
#18 0x00007619d570b924 in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData const&, QVariant const&, QQmlRefPointer<QQmlContextData> const&, QFlags<QQmlPropertyData::WriteFlag>) () from /usr/lib/libQt6Qml.so.6
#19 0x00007619d55bd308 in QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData const*, QV4::Value const&) () from /usr/lib/libQt6Qml.so.6
#20 0x00007619d55bdabe in QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlRefPointer<QQmlContextData> const&, QObject*, QV4::String*, QFlags<QV4::QObjectWrapper::Flag>, QV4::Value const&) () from /usr/lib/libQt6Qml.so.6
#21 0x00007619d55bdc4b in QV4::QObjectWrapper::virtualPut(QV4::Managed*, QV4::PropertyKey, QV4::Value const&, QV4::Value*) () from /usr/lib/libQt6Qml.so.6
#22 0x00007619d5594c4c in QV4::Lookup::setterFallback(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value&, QV4::Value const&) () from /usr/lib/libQt6Qml.so.6
#23 0x00007619af32ecf9 in ?? ()
#24 0x00007ffd8f89b770 in ?? ()
#25 0x00007ffd8f89b7e0 in ?? ()
#26 0x000057120e58e020 in ?? ()
#27 0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7619c55ae6c0 (LWP 1182)):
#0  0x00007619d3ddebb0 in ppoll () from /usr/lib/libc.so.6
#1  0x00007619d2d67327 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007619d2d03a55 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007619d45fb2fd in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt6Core.so.6
#4  0x00007619d439aee6 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt6Core.so.6
#5  0x00007619d4491082 in QThread::run() () from /usr/lib/libQt6Core.so.6
#6  0x00007619d45120cd in ?? () from /usr/lib/libQt6Core.so.6
#7  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#8  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7619b5b6b6c0 (LWP 1722)):
#0  0x00007619d3ddebb0 in ppoll () from /usr/lib/libc.so.6
#1  0x00007619d2d67327 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007619d2d03a55 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007619d45fb2fd in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt6Core.so.6
#4  0x00007619d439aee6 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt6Core.so.6
#5  0x00007619d4490f22 in QThread::exec() () from /usr/lib/libQt6Core.so.6
#6  0x00007619d5cec538 in ?? () from /usr/lib/libQt6Quick.so.6
#7  0x00007619d45120cd in ?? () from /usr/lib/libQt6Core.so.6
#8  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#9  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7619ccf5b6c0 (LWP 1065)):
#0  0x00007619d3dde63d in poll () from /usr/lib/libc.so.6
#1  0x00007619d6b9520b in ?? () from /usr/lib/libxcb.so.1
#2  0x00007619d6b96f3d in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x00007619cd884d19 in ?? () from /usr/lib/qt6/plugins/platforms/../../../libQt6XcbQpa.so.6
#4  0x00007619d45120cd in ?? () from /usr/lib/libQt6Core.so.6
#5  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#6  0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7619afbff6c0 (LWP 2067)):
[KCrash Handler]
#4  0x00007619d4de3df0 in QOpenGLContext::doneCurrent() () from /usr/lib/libQt6Gui.so.6
#5  0x00007619d4dee912 in ?? () from /usr/lib/libQt6Gui.so.6
#6  0x00007619d451af2c in QThreadStorageData::finish(void**) () from /usr/lib/libQt6Core.so.6
#7  0x00007619d4665499 in ?? () from /usr/lib/libQt6Core.so.6
#8  0x00007619d45120d6 in ?? () from /usr/lib/libQt6Core.so.6
#9  0x00007619d3d6739d in ?? () from /usr/lib/libc.so.6
#10 0x00007619d3dec49c in ?? () from /usr/lib/libc.so.6

You'll notice i have some locale warnings still. Unsure how that happened. I did set most things to en_CH.UTF-8 as reported previously and LC_ADDRESS is back at C. Did I miss to do something?

[motherfucker_big_scorpio@Nexus ~]$ locale 
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=en_CH.UTF-8
LC_TIME=en_CH.UTF-8
LC_COLLATE=en_US.UTF-8
LC_MONETARY=pt_PT.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_PAPER=en_CH.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=C
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_CH.UTF-8
LC_IDENTIFICATION=en_CH.UTF-8
LC_ALL=

Will report again to see if it's going to be different without the USB Hub being attached.

Offline

#20 2025-01-07 20:52:54

seth
Member
Registered: 2012-09-03
Posts: 61,670

Re: Why is my desktop environment unresponsive for 3 minutes?

Did I miss to do something?

en_CH is still not a thing?
You can have de_CH,fr_CH and it_CH - I know there's a 4th language but whatever that's supposed to be, it's not english tongue

plasma crash-aborted after losing the GL context which is likely related to

Jan 07 15:24:54 Nexus kwin_x11[1019]: kf.config.core: "\"fsrestore1\" - conversion of \"0,0,0,0\" to QRect failed"
Jan 07 15:24:54 Nexus kwin_x11[1019]: kf.config.core: "\"restore2\" - conversion of \"0,0,0,0\" to QRect failed"
Jan 07 15:24:54 Nexus kwin_x11[1019]: kf.config.core: "\"fsrestore2\" - conversion of \"0,0,0,0\" to QRect failed"
Jan 07 15:24:54 Nexus kwin_x11[1019]: kf.config.core: "\"fsrestore3\" - conversion of \"0,0,0,0\" to QRect failed"
Jan 07 15:24:54 Nexus kwin_x11[1019]: kf.config.core: "\"fsrestore4\" - conversion of \"0,0,0,0\" to QRect failed"
Jan 07 15:24:54 Nexus kwin_x11[1019]: kf.config.core: "\"fsrestore5\" - conversion of \"0,0,0,0\" to QRect failed"

the zero-size rect there heavily implying that you lost every output - typically kscreen removing them after they unregistered in response to DPMS (try to disable kscreen, but I don't think that's related to your overall problem)

Edit: the errors in the "dump" seem to suggest some IO trouble - pointing at the USB device again…

Last edited by seth (2025-01-07 20:54:17)

Offline

#21 2025-01-07 22:35:36

Big Scorpio
Member
Registered: 2024-12-15
Posts: 58

Re: Why is my desktop environment unresponsive for 3 minutes?

seth wrote:

en_CH is still not a thing?
You can have de_CH,fr_CH and it_CH - I know there's a 4th language but whatever that's supposed to be, it's not english tongue

I think not. Not, that i've seen in in the locale.gen. In KDE's Region and Language Settings I set the locales to en_CH.UTF-8 as they popped up on the list and match the way i interpret things.

seth wrote:

the zero-size rect there heavily implying that you lost every output - typically kscreen removing them after they unregistered in response to DPMS (try to disable kscreen, but I don't think that's related to your overall problem)

Edit: the errors in the "dump" seem to suggest some IO trouble - pointing at the USB device again…

Well, I did it now with the USB Hub completely disconnected from the motherboard and then rebooted.

[motherfucker_big_scorpio@Nexus ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 045b:0209 Hitachi, Ltd 
Bus 001 Device 004: ID 1a2c:4b5e China Resource Semico Co., Ltd USB Keyboard
Bus 001 Device 005: ID 09da:2696 A4Tech Co., Ltd. A4tech FHD 1080P PC Camera
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 18f8:0f99 [Maxxter] Optical gaming mouse
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 002: ID 0451:8140 Texas Instruments, Inc. TUSB8041 4-Port Hub

I found, that the system booted up double as fast and the plasmashell was ready to go shortly after logging in - just the way i expected. The USB port error also didn't show up.
I let it go AFK again (i think it was hibernating or something?) at

22:47:32 Nexus systemd-logind[736]: The system will suspend now!

Came back and woke it up at

Jan 07 23:18:10 Nexus kernel: Freezing user space processes
Jan 07 23:18:10 Nexus kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Jan 07 23:18:10 Nexus kernel: OOM killer disabled.

Now this USB port warning shows up out of nowhere again as you can see AFTER i woke it up.
And the locale warnings with "C" have not vanished either.
Running "locale" yields the same as before but with "LC_ADDRESS=en_CH.UTF-8" this time. I don't know where it gets that non UTF-8 "C" from.

Problem persists.

Might really blacklist USB Bus 2 and then plug the USB Hub elsewhere.

Offline

#22 2025-01-08 00:23:37

seth
Member
Registered: 2012-09-03
Posts: 61,670

Re: Why is my desktop environment unresponsive for 3 minutes?

as they popped up on the list and match the way i interpret things

https://wiki.archlinux.org/title/Locale … g_language

grep CH /etc/locale.gen

en_CH.UTF-8 is not a valid locale unless you added a custom one.
Get rid of that.

Then please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

I let it go AFK again (i think it was hibernating or something?) at

On my Windows system I see no such message appearing or io stalling.

Gahhh… 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Offline

#23 2025-01-08 20:58:39

Big Scorpio
Member
Registered: 2024-12-15
Posts: 58

Re: Why is my desktop environment unresponsive for 3 minutes?

seth wrote:

en_CH.UTF-8 is not a valid locale unless you added a custom one.
Get rid of that.

Then please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Will do (currently on Windows)

seth wrote:

Gahhh… 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Make that Gah 2. Apparently Windows did not disable fast startup initially. The

powercfg /H off

did nothing. I'm not taking any chances this time -> https://imgur.com/a/929hO5F
I also saw, that i must strictly shut down the machine for the effects to take place.

Continuing ...
Update:

I complied seth. In short, I believe the stalling is really caused by the USB2 port1 message spamming nature, in which I find it unknown whether it's the HUB Device or the cable to it or Windows Fast Boot intervening somehow.

I deauthorized usb2-port1 by running

echo 'ACTION=="add", SUBSYSTEM=="usb", KERNEL=="usb2", ATTR{authorized}="0"' > /etc/udev/rules.d/99-disable-usb2-port1.rules

dmesg no longer reports these spam after rebooting. The bootup time and log in is as swift as in Windows again. This behavior is in fact identical to before changing my locales to (i did this too)

[motherfucker_big_scorpio@Nexus ~]$ locale
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LC_CTYPE=en_AG.UTF-8
LC_NUMERIC=en_AG.UTF-8
LC_TIME=en_AG.UTF-8
LC_COLLATE=en_AG.UTF-8
LC_MONETARY=pt_PT.UTF-8
LC_MESSAGES=en_AG.UTF-8
LC_PAPER=en_AG.UTF-8
LC_NAME=en_AG.UTF-8
LC_ADDRESS=en_AG.UTF-8
LC_TELEPHONE=en_AG.UTF-8
LC_MEASUREMENT=en_AG.UTF-8
LC_IDENTIFICATION=en_AG.UTF-8
LC_ALL=
[motherfucker_big_scorpio@Nexus ~]$  locale --all-locales
C
C.utf8
de_DE
de_DE@euro
de_DE.iso88591
de_DE.iso885915@euro
de_DE.utf8
deutsch
en_AG
en_AG.utf8
en_US.utf8
german
POSIX

As a consequence the USB devices connected to the USB Hub are no longer functional regardless to which USB port I plug it in to my motherboard's back panel. Keyboard and Mouse function normally.

However I ran out of time today to test it going into a sleep or hibernate like state and coming back from being AFK long enough. Will have to continue this the following day.

Here's the journalctl -b now -> http://0x0.st/8-8s.txt
As you can see, the texts

journalctl -b wrote:

Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
                                   Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.

Have not vanished.

Note for myself:
1) Figure out what to do next with the USB Hub and the devices I plug into it
2) I need to install an additional locale in English language but in European format and start using it. US formats aren't for me.

Last edited by Big Scorpio (2025-01-08 23:48:24)

Offline

#24 2025-01-09 14:28:45

Big Scorpio
Member
Registered: 2024-12-15
Posts: 58

Re: Why is my desktop environment unresponsive for 3 minutes?

Alright, I did it again. Went AFK and came back hours later. System is still stalling. On top of that before I got to see the login screen several minutes have passed. Plasmashell is unresponsive for several minutes too.
Conditions are USB2 Port1 is deauthorized, so no more spam messages.
And the locale's are just like i posted 1 post previously.

Here is the journalctl -b -> http://0x0.st/8-cY.txt

By this time

Jan 09 15:18:33 Nexus sudo[3121]: motherfucker_big_scorpio : TTY=pts/1 ; PWD=/home/motherfucker_big_scorpio ; USER=root ; COMMAND=/usr/bin/journalctl -b
Jan 09 15:18:33 Nexus sudo[3121]: pam_unix(sudo:session): session opened for user root(uid=0) by motherfucker_big_scorpio(uid=1000)

I got to see the desktop but plasmashell was unresponsive.
By this time

Jan 09 15:19:39 Nexus sudo[3520]: motherfucker_big_scorpio : TTY=pts/1 ; PWD=/home/motherfucker_big_scorpio ; USER=root ; COMMAND=/usr/bin/journalctl -b
Jan 09 15:19:39 Nexus sudo[3520]: pam_unix(sudo:session): session opened for user root(uid=0) by motherfucker_big_scorpio(uid=1000)

plasmashell became responsive

Here's some of the dmesg content

[   10.447352] snd_hda_codec_ca0132 hdaudioC2D0: ca0132 DSP downloaded and running
[   10.873472] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1f.3/sound/card2/input18
[   10.873511] input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1f.3/sound/card2/input19
[   10.873541] input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1f.3/sound/card2/input20
[   10.873569] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card2/input21
[   10.873595] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card2/input22
[   10.873620] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card2/input23
[   10.873651] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card2/input24
[   24.731906] usb 1-4: 3:1: cannot get freq at ep 0x84
[   24.742991] usb 1-4: 3:1: cannot get freq at ep 0x84
[   24.845581] [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[   24.845662] [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[   26.582352] usb 1-4: Failed to query (GET_DEF) UVC control 9 on unit 1: 0 (exp. 2).
[   26.585348] usb 1-4: Failed to query (GET_DEF) UVC control 9 on unit 1: 0 (exp. 2).
[ 1618.130218] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 0
[ 1619.073314] PM: suspend entry (deep)
[ 1619.292571] Filesystems sync: 0.219 seconds
[ 1619.326918] Freezing user space processes
[ 1619.328701] Freezing user space processes completed (elapsed 0.001 seconds)
[ 1619.328703] OOM killer disabled.
[ 1619.328704] Freezing remaining freezable tasks
[ 1619.329782] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[ 1619.329823] printk: Suspending console(s) (use no_console_suspend to debug)
[ 1619.366652] serial 00:01: disabled
[ 1619.366989] e1000e: EEE TX LPI TIMER: 00000011
[ 1619.383618] sd 4:0:0:0: [sdc] Synchronizing SCSI cache
[ 1619.383620] sd 5:0:0:0: [sdd] Synchronizing SCSI cache
[ 1619.383634] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
[ 1619.384404] ata4.00: Entering standby power mode
[ 1619.385025] ata5.00: Entering standby power mode
[ 1619.385078] ata6.00: Entering standby power mode
[ 1619.386833] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[ 1619.390455] ata2.00: Entering standby power mode
[ 1620.640390] ACPI: PM: Preparing to enter system sleep state S3
[ 1620.643204] ACPI: PM: Saving platform NVS memory
[ 1620.643455] Disabling non-boot CPUs ...
[ 1620.645824] smpboot: CPU 7 is now offline
[ 1620.649293] smpboot: CPU 6 is now offline
[ 1620.653375] smpboot: CPU 5 is now offline
[ 1620.655667] smpboot: CPU 4 is now offline
[ 1620.657320] smpboot: CPU 3 is now offline
[ 1620.658846] smpboot: CPU 2 is now offline
[ 1620.660469] smpboot: CPU 1 is now offline
[ 1620.662631] ACPI: PM: Low-level resume complete
[ 1620.662670] ACPI: PM: Restoring platform NVS memory
[ 1620.663378] Enabling non-boot CPUs ...
[ 1620.663427] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 1620.664050] CPU1 is up
[ 1620.664093] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ 1620.664707] CPU2 is up
[ 1620.664739] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ 1620.665366] CPU3 is up
[ 1620.665397] smpboot: Booting Node 0 Processor 4 APIC 0x1
[ 1620.666169] CPU4 is up
[ 1620.666210] smpboot: Booting Node 0 Processor 5 APIC 0x3
[ 1620.666894] CPU5 is up
[ 1620.666933] smpboot: Booting Node 0 Processor 6 APIC 0x5
[ 1620.667589] CPU6 is up
[ 1620.667621] smpboot: Booting Node 0 Processor 7 APIC 0x7
[ 1620.668289] CPU7 is up
[ 1620.670850] ACPI: PM: Waking up from system sleep state S3
[ 1621.792880] usb usb3: root hub lost power or was reset
[ 1621.792884] usb usb4: root hub lost power or was reset
[ 1621.812018] serial 00:01: activated
[ 1621.840262] nvme nvme0: 8/0/0 default/read/poll queues
[ 1622.049787] usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd
[ 1622.099299] ata7: SATA link down (SStatus 0 SControl 300)
[ 1622.099337] ata8: SATA link down (SStatus 0 SControl 300)
[ 1622.145939] ata1: SATA link down (SStatus 4 SControl 300)
[ 1622.145971] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1622.145996] ata3: SATA link down (SStatus 4 SControl 300)
[ 1622.146485] ata2.00: supports DRM functions and may not be fully accessible
[ 1622.157230] sd 1:0:0:0: [sda] Starting disk
[ 1622.157615] ata2.00: supports DRM functions and may not be fully accessible
[ 1622.167417] ata2.00: configured for UDMA/133
[ 1622.177577] ahci 0000:00:17.0: port does not support device sleep
[ 1622.178069] ata2.00: Enabling discard_zeroes_data
[ 1622.319645] usb 3-1: reset low-speed USB device number 2 using xhci_hcd
[ 1622.712839] usb 3-2: reset high-speed USB device number 3 using xhci_hcd
[ 1623.023303] usb 4-2.3: reset SuperSpeed USB device number 3 using xhci_hcd
[ 1623.113403] usb 4-2.4: reset SuperSpeed USB device number 4 using xhci_hcd
[ 1623.566158] usb 3-2.2: reset full-speed USB device number 4 using xhci_hcd
[ 1623.586035] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1623.669821] sd 4:0:0:0: [sdc] Starting disk
[ 1623.670432] ata5.00: configured for UDMA/100
[ 1624.317842] OOM killer enabled.
[ 1624.317848] Restarting tasks ... 
[ 1624.318708] pci_bus 0000:09: Allocating resources
[ 1624.319556] pci_bus 0000:09: Allocating resources
[ 1624.319934] usb 1-2: USB disconnect, device number 3
[ 1624.326043] done.
[ 1624.326050] random: crng reseeded on system resumption
[ 1624.326162] PM: suspend exit
[ 1624.356742] snd_hda_intel 0000:00:1f.3: Direct firmware load for ctefx-r3di.bin failed with error -2
[ 1624.554754] pci_bus 0000:09: Allocating resources
[ 1624.922578] snd_hda_codec_ca0132 hdaudioC2D0: ca0132 DSP downloaded and running
[ 1625.615749] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1625.650444] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down
[ 1625.711425] sd 3:0:0:0: [sdb] Starting disk
[ 1625.711969] ata4.00: configured for UDMA/133
[ 1625.834515] alx 0000:07:00.0 enp7s0: NIC Up: 100 Mbps Full
[ 1627.169108] ata6: link is slow to respond, please be patient (ready=0)
[ 1627.666524] usb 1-4: Failed to query (GET_DEF) UVC control 9 on unit 1: 0 (exp. 2).
[ 1627.669147] usb 1-4: Failed to query (GET_DEF) UVC control 9 on unit 1: 0 (exp. 2).
[ 1631.069059] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1631.096070] sd 5:0:0:0: [sdd] Starting disk
[ 1631.098354] ata6.00: configured for UDMA/133

I'm thinking of disabling hibernation & sleep. It's too much of a pain in the ass on the regular. Either that or downgrade KDE to a more stable and workable version somehow.

I'll retest again with kscreen disabled

Last edited by Big Scorpio (2025-01-09 14:32:22)

Offline

#25 2025-01-11 20:51:29

Big Scorpio
Member
Registered: 2024-12-15
Posts: 58

Re: Why is my desktop environment unresponsive for 3 minutes?

Big Scorpio wrote:

I'll retest again with kscreen disabled

No, I won't. I've had enough for now. Maybe sometime later I'll revise this again unless we're getting close to get to the bottom of these issues.
I'll disagreeably settle for less by disabling usb2-port1 and disabling f#@&ing hibernating before I'll waste another hour or so.

Still, the login screen after AFKing takes a minute to be interactive until i can type my password and enter. Got no data to provide it for now. Still 1 minute is better than what feels like a boring class in high school.

Offline

Board footer

Powered by FluxBB