After update to KDE Plasma 6 random freezes for 4-10 seconds

I’m using KDE Neon with X11 and KDE Plasma 6. All system updated.

My problem is like KDE Plasma completely freezes in fullscreen except cursor but with some diferences:

  1. This has start just after update to KDE plasma 6. No problem the other 4 month since I’ve received this laptop.
  2. I’m using Mesa Intel Graphics. Integrated video card, not Nvidia.
  3. I’m using X11 instead of Wayland (I need ksnip rectangular screenshots feature, that not compatible with wayland)

An example of journalctl -b (the freeze was between 11:15:07 and 11:15:14):

mar 03 11:14:36 pentangelo systemd[1]: Started Network Manager Script Dispatcher Service.
mar 03 11:14:46 pentangelo systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
mar 03 11:15:06 pentangelo NetworkManager[829]: <info>  [1709460906.6844] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.1.101
mar 03 11:15:21 pentangelo plasmashell[5149]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
mar 03 11:15:22 pentangelo plasmashell[5149]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.

another example (the freeze was between 11:20:50 and 11:21:00):

mar 03 11:20:13 pentangelo kinfocenter[8616]: qt.qml.context: qrc:/kcm/kcm_about-distro/main.qml:111:25 Parameter "event" is not declared. Injection of parameters into signal handlers is d>
mar 03 11:20:20 pentangelo plasmashell[5149]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
mar 03 11:20:20 pentangelo plasmashell[5149]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
mar 03 11:20:24 pentangelo NetworkManager[829]: <info>  [1709461224.1048] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.1.101
mar 03 11:20:54 pentangelo NetworkManager[829]: <info>  [1709461254.0995] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.1.101
mar 03 11:21:24 pentangelo NetworkManager[829]: <info>  [1709461284.0970] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.1.101

No relevant lines on dmesg:

[dom mar  3 11:18:19 2024] wlp0s20f3: Connection to AP 98:da:c4:8a:43:a2 lost
[dom mar  3 11:18:21 2024] wlp0s20f3: authenticate with 98:da:c4:8a:43:a2
[dom mar  3 11:18:21 2024] wlp0s20f3: 80 MHz not supported, disabling VHT
[dom mar  3 11:18:21 2024] wlp0s20f3: send auth to 98:da:c4:8a:43:a2 (try 1/3)
[dom mar  3 11:18:21 2024] wlp0s20f3: authenticated
[dom mar  3 11:18:21 2024] wlp0s20f3: associate with 98:da:c4:8a:43:a2 (try 1/3)
[dom mar  3 11:18:21 2024] wlp0s20f3: RX AssocResp from 98:da:c4:8a:43:a2 (capab=0x431 status=0 aid=3)
[dom mar  3 11:18:21 2024] wlp0s20f3: associated
[dom mar  3 11:23:30 2024] wlp0s20f3: Connection to AP 98:da:c4:8a:43:a2 lost
[dom mar  3 11:23:32 2024] wlp0s20f3: authenticate with 98:da:c4:8a:43:a2
[dom mar  3 11:23:32 2024] wlp0s20f3: 80 MHz not supported, disabling VHT
[dom mar  3 11:23:32 2024] wlp0s20f3: send auth to 98:da:c4:8a:43:a2 (try 1/3)
[dom mar  3 11:23:32 2024] wlp0s20f3: authenticated
[dom mar  3 11:23:32 2024] wlp0s20f3: associate with 98:da:c4:8a:43:a2 (try 1/3)
[dom mar  3 11:23:32 2024] wlp0s20f3: associate with 98:da:c4:8a:43:a2 (try 2/3)
[dom mar  3 11:23:32 2024] wlp0s20f3: RX AssocResp from 98:da:c4:8a:43:a2 (capab=0x431 status=0 aid=3)
[dom mar  3 11:23:32 2024] wlp0s20f3: associated

I’ve noticed that if I type something with the keyboard while the freeze is in progress, when I regain control of the system, what I typed is saved.

Any idea?

3 Likes

Same thing here with same config.

1 Like

Does it happen to anyone else?

Another hint… if I’m watching a streaming video, when the freeze appears the video is blocked, but the audio is still heard.

1 Like

You can try spectacle, it offers this feature in Wayland just fine.

1 Like

Exactly what is happening to me. Same setup here

1 Like

Thank’s but I already tried spectacle. It doesn’t have an indispensable feature for me: tabs. Sometimes I need to take 10 o 15 rectangular screenshots quickly and after paste them in (sometimes) a different order.

Spectacle allows to ‘Save’ with one click, then you can use dolphin/gwenview or any other app to select the screenshot you want.
It also has a ‘Copy’ that copies to clipboard, or you can set a setting in general so that after taking a screenshot it copies to clipboard directly.
That’s the best I can suggest to you to align a bit with your workflow.

The rectangular area screenshot code is a bit complicated at the moment. A bit hard to integrate to ksnip, we’d want to improve our API.

The X11 freeze should be fixed in Plasma 6.0.1, in a few days (481721 – kwin_x11 compositor screen freeze (regression from kwin 5))

Yes, I know, and I’ve actually already given Spectable a shot, but it’s not as snappy as Ksnip’s tabs.

Thanks for the comment. Any way to track progress? I’m sorry, but I’m not a developer and I can’t help so much.

Great news! Thank you!

It happens the same and I suspect it has to do with the video card driver.

Don’t hold your breath on it, there are no plans and this is not a reported bug AFAICT.
Reporting it as a bug would be useful.

Ok, I will but where? at kde bug tracker? or at ksnip issues?

If is the second case, there are a few already opened:

Support Capture Rectangular Area for Wayland · ksnip/ksnip · Discussion #884 · GitHub (where @apol and @ngraham already commented)
No "rectangle area" screeshot option in ksnip-1.9.1-continuous-x86_64.AppImage · Issue #660 · ksnip/ksnip · GitHub

1 Like

I did not know/remember about those.

The X11 freeze should be fixed in Plasma 6.0.1, in a few days (481721 – kwin_x11 compositor screen freeze (regression from kwin 5) )

6.0.1 has been released, does anyone know when KDE Neon will get the update? If it doesn’t release soon I will have to roll back to a timeshift snapshot, I can’t deal with freezes every minute or two

1 Like

This motivated me to move to Wayland - and was pleasantly surprised that everything’s working quite nicely there. (Including the new Spectacle screenshot features that some have mentioned.)

I happens the same to me, no matter if it is X11 or Wayland session. Random freezes 3-10 seconds. My machine is Lenovo Yoga with Intel integrated graphics:
00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) (prog-if 00 [VGA controller])
Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics]
I use KDE Neon distribution. On Plasma 5 all works fine.

1 Like

Last update to Plasma 6.02 repairs this bug. I work all day and didn’t have any freeze.

2 Likes

exactly! After this update it no longer freezes

+1 seems solved here with 6.0.2 too

I also have the same issue on arch with 6.0.1. Here is journalctl when it happens

Mar 15 11:04:01 arch plasmashell[4002]: [4002:1:0315/110401.542257:ERROR:command_buffer_proxy_impl.cc(131)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
Mar 15 11:04:15 arch kwin_wayland[636]: This plugin does not support raise()
Mar 15 11:04:43 arch kernel: INFO: task dolphin:9767 blocked for more than 122 seconds.
Mar 15 11:04:43 arch kernel:       Not tainted 6.7.9-zen1-1-zen #1
Mar 15 11:04:43 arch kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar 15 11:04:43 arch kernel: task:dolphin         state:D stack:0     pid:9767  tgid:9767  ppid:767    flags:0x00004002
Mar 15 11:04:43 arch kernel: Call Trace:
Mar 15 11:04:43 arch kernel:  <TASK>
Mar 15 11:04:43 arch kernel:  __schedule+0xcaa/0x1950
Mar 15 11:04:43 arch kernel:  ? __d_alloc+0x170/0x230
Mar 15 11:04:43 arch kernel:  ? __d_alloc+0x170/0x230
Mar 15 11:04:43 arch kernel:  schedule+0x32/0xd0
Mar 15 11:04:43 arch kernel:  d_alloc_parallel+0x376/0x450
Mar 15 11:04:43 arch kernel:  ? __pfx_default_wake_function+0x10/0x10
Mar 15 11:04:43 arch kernel:  __lookup_slow+0x5d/0x130
Mar 15 11:04:43 arch kernel:  path_lookupat+0x2b3/0x3e0
Mar 15 11:04:43 arch kernel:  filename_lookup+0xe8/0x1f0
Mar 15 11:04:43 arch kernel:  vfs_statx+0x92/0x190
Mar 15 11:04:43 arch kernel:  __x64_sys_statx+0xa7/0x100
Mar 15 11:04:43 arch kernel:  do_syscall_64+0x61/0xe0
Mar 15 11:04:43 arch kernel:  ? do_syscall_64+0x70/0xe0
Mar 15 11:04:43 arch kernel:  ? exc_page_fault+0x7f/0x180
Mar 15 11:04:43 arch kernel:  entry_SYSCALL_64_after_hwframe+0x6e/0x76
Mar 15 11:04:43 arch kernel: RIP: 0033:0x71c21cd19b4e
Mar 15 11:04:43 arch kernel: RSP: 002b:00007fffdd43a4e8 EFLAGS: 00000206 ORIG_RAX: 000000000000014c
Mar 15 11:04:43 arch kernel: RAX: ffffffffffffffda RBX: 000059bed866f840 RCX: 000071c21cd19b4e
Mar 15 11:04:43 arch kernel: RDX: 0000000000000800 RSI: 000059bed86dc800 RDI: 00000000ffffff9c
Mar 15 11:04:43 arch kernel: RBP: 0000000072a67077 R08: 00007fffdd43a550 R09: 0000000000000007
Mar 15 11:04:43 arch kernel: R10: 0000000000000fff R11: 0000000000000206 R12: 000059bed866f808
Mar 15 11:04:43 arch kernel: R13: 0000000000000000 R14: 00007fffdd43a510 R15: 0000000000000000
Mar 15 11:04:43 arch kernel:  </TASK>
Mar 15 11:04:43 arch kernel: INFO: task dolphin:20651 blocked for more than 122 seconds.
Mar 15 11:04:43 arch kernel:       Not tainted 6.7.9-zen1-1-zen #1
Mar 15 11:04:43 arch kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar 15 11:04:43 arch kernel: task:dolphin         state:D stack:0     pid:20651 tgid:20651 ppid:767    flags:0x00000002
Mar 15 11:04:43 arch kernel: Call Trace:
Mar 15 11:04:43 arch kernel:  <TASK>
Mar 15 11:04:43 arch kernel:  __schedule+0xcaa/0x1950
Mar 15 11:04:43 arch kernel:  ? __d_alloc+0x170/0x230
Mar 15 11:04:43 arch kernel:  ? __d_alloc+0x170/0x230
Mar 15 11:04:43 arch kernel:  schedule+0x32/0xd0
Mar 15 11:04:43 arch kernel:  d_alloc_parallel+0x376/0x450
Mar 15 11:04:43 arch kernel:  ? __pfx_default_wake_function+0x10/0x10
Mar 15 11:04:43 arch kernel:  __lookup_slow+0x5d/0x130
Mar 15 11:04:43 arch kernel:  path_lookupat+0x2b3/0x3e0
Mar 15 11:04:43 arch kernel:  filename_lookup+0xe8/0x1f0
Mar 15 11:04:43 arch kernel:  vfs_statx+0x92/0x190
Mar 15 11:04:43 arch kernel:  __x64_sys_statx+0xa7/0x100
Mar 15 11:04:43 arch kernel:  do_syscall_64+0x61/0xe0
Mar 15 11:04:43 arch kernel:  ? switch_fpu_return+0x50/0xe0
Mar 15 11:04:43 arch kernel:  ? exit_to_user_mode_prepare+0x132/0x1f0
Mar 15 11:04:43 arch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Mar 15 11:04:43 arch kernel:  ? do_syscall_64+0x70/0xe0
Mar 15 11:04:43 arch kernel:  ? exc_page_fault+0x7f/0x180
Mar 15 11:04:43 arch kernel:  entry_SYSCALL_64_after_hwframe+0x6e/0x76
Mar 15 11:04:43 arch kernel: RIP: 0033:0x71585e719b4e
Mar 15 11:04:43 arch kernel: RSP: 002b:00007ffe87f7f9f8 EFLAGS: 00000202 ORIG_RAX: 000000000000014c
Mar 15 11:04:43 arch kernel: RAX: ffffffffffffffda RBX: 00005eb2132862b0 RCX: 000071585e719b4e
Mar 15 11:04:43 arch kernel: RDX: 0000000000000900 RSI: 00005eb2136f6c80 RDI: 00000000ffffff9c
Mar 15 11:04:43 arch kernel: RBP: 0000000000010000 R08: 00007ffe87f7fa60 R09: 0000000000000007
Mar 15 11:04:43 arch kernel: R10: 0000000000000fff R11: 0000000000000202 R12: 00005eb213286278
Mar 15 11:04:43 arch kernel: R13: 0000000000000000 R14: 00007ffe87f7fa20 R15: 0000000000010000
Mar 15 11:04:43 arch kernel:  </TASK>
Mar 15 11:04:43 arch kernel: INFO: task dolphin:20735 blocked for more than 122 seconds.
Mar 15 11:04:43 arch kernel:       Not tainted 6.7.9-zen1-1-zen #1
Mar 15 11:04:43 arch kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar 15 11:04:43 arch kernel: task:dolphin         state:D stack:0     pid:20735 tgid:20735 ppid:767    flags:0x00004002
Mar 15 11:04:43 arch kernel: Call Trace:
Mar 15 11:04:43 arch kernel:  <TASK>
Mar 15 11:04:43 arch kernel:  __schedule+0xcaa/0x1950
Mar 15 11:04:43 arch kernel:  ? __d_alloc+0x170/0x230
Mar 15 11:04:43 arch kernel:  ? __d_alloc+0x170/0x230
Mar 15 11:04:43 arch kernel:  schedule+0x32/0xd0
Mar 15 11:04:43 arch kernel:  d_alloc_parallel+0x376/0x450
Mar 15 11:04:43 arch kernel:  ? __pfx_default_wake_function+0x10/0x10
Mar 15 11:04:43 arch kernel:  __lookup_slow+0x5d/0x130
Mar 15 11:04:43 arch kernel:  path_lookupat+0x2b3/0x3e0
Mar 15 11:04:43 arch kernel:  filename_lookup+0xe8/0x1f0
Mar 15 11:04:43 arch kernel:  vfs_statx+0x92/0x190
Mar 15 11:04:43 arch kernel:  __x64_sys_statx+0xa7/0x100
Mar 15 11:04:43 arch kernel:  do_syscall_64+0x61/0xe0
Mar 15 11:04:43 arch kernel:  ? switch_fpu_return+0x50/0xe0
Mar 15 11:04:43 arch kernel:  ? exit_to_user_mode_prepare+0x132/0x1f0
Mar 15 11:04:43 arch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Mar 15 11:04:43 arch kernel:  ? do_syscall_64+0x70/0xe0
Mar 15 11:04:43 arch kernel:  ? syscall_exit_to_user_mode+0x22/0x40
Mar 15 11:04:43 arch kernel:  ? do_syscall_64+0x70/0xe0
Mar 15 11:04:43 arch kernel:  ? exc_page_fault+0x7f/0x180
Mar 15 11:04:43 arch kernel:  entry_SYSCALL_64_after_hwframe+0x6e/0x76
Mar 15 11:04:43 arch kernel: RIP: 0033:0x778e34919b4e
Mar 15 11:04:43 arch kernel: RSP: 002b:00007fffaf5fbb88 EFLAGS: 00000202 ORIG_RAX: 000000000000014c
Mar 15 11:04:43 arch kernel: RAX: ffffffffffffffda RBX: 0000634cec33ab90 RCX: 0000778e34919b4e
Mar 15 11:04:43 arch kernel: RDX: 0000000000000900 RSI: 0000634cec407440 RDI: 00000000ffffff9c
Mar 15 11:04:43 arch kernel: RBP: 0000000000010000 R08: 00007fffaf5fbbf0 R09: 0000000000000007
Mar 15 11:04:43 arch kernel: R10: 0000000000000fff R11: 0000000000000202 R12: 0000634cec33ab58
Mar 15 11:04:43 arch kernel: R13: 0000000000000000 R14: 00007fffaf5fbbb0 R15: 0000000000010000
Mar 15 11:04:43 arch kernel:  </TASK>
Mar 15 11:04:43 arch kernel: INFO: task dolphin:20835 blocked for more than 122 seconds.
Mar 15 11:04:43 arch kernel:       Not tainted 6.7.9-zen1-1-zen #1
Mar 15 11:04:43 arch kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar 15 11:04:43 arch kernel: task:dolphin         state:D stack:0     pid:20835 tgid:20835 ppid:767    flags:0x00004002
Mar 15 11:04:43 arch kernel: Call Trace:
Mar 15 11:04:43 arch kernel:  <TASK>
Mar 15 11:04:43 arch kernel:  __schedule+0xcaa/0x1950
Mar 15 11:04:43 arch kernel:  ? __d_alloc+0x170/0x230
Mar 15 11:04:43 arch kernel:  schedule+0x32/0xd0
Mar 15 11:04:43 arch kernel:  d_alloc_parallel+0x376/0x450
Mar 15 11:04:43 arch kernel:  ? __pfx_default_wake_function+0x10/0x10
Mar 15 11:04:43 arch kernel:  __lookup_slow+0x5d/0x130
Mar 15 11:04:43 arch kernel:  path_lookupat+0x2b3/0x3e0
Mar 15 11:04:43 arch kernel:  filename_lookup+0xe8/0x1f0
Mar 15 11:04:43 arch kernel:  vfs_statx+0x92/0x190
Mar 15 11:04:43 arch kernel:  __x64_sys_statx+0xa7/0x100
Mar 15 11:04:43 arch kernel:  do_syscall_64+0x61/0xe0
Mar 15 11:04:43 arch kernel:  ? __rseq_handle_notify_resume+0xa9/0x590
Mar 15 11:04:43 arch kernel:  ? sched_clock+0x10/0x30
Mar 15 11:04:43 arch kernel:  ? task_mm_cid_work+0x1a1/0x220
Mar 15 11:04:43 arch kernel:  ? exit_to_user_mode_prepare+0x17d/0x1f0
Mar 15 11:04:43 arch kernel:  entry_SYSCALL_64_after_hwframe+0x6e/0x76
Mar 15 11:04:43 arch kernel: RIP: 0033:0x7b9d92319b4e
Mar 15 11:04:43 arch kernel: RSP: 002b:00007ffe49f5d9a8 EFLAGS: 00000206 ORIG_RAX: 000000000000014c
Mar 15 11:04:43 arch kernel: RAX: ffffffffffffffda RBX: 000057b48e1f9bd0 RCX: 00007b9d92319b4e
Mar 15 11:04:43 arch kernel: RDX: 0000000000000800 RSI: 000057b48e674850 RDI: 00000000ffffff9c
Mar 15 11:04:43 arch kernel: RBP: 0000000072a67077 R08: 00007ffe49f5da10 R09: 0000000000000007
Mar 15 11:04:43 arch kernel: R10: 0000000000000fff R11: 0000000000000206 R12: 000057b48e1f9b98
Mar 15 11:04:43 arch kernel: R13: 0000000000000000 R14: 00007ffe49f5d9d0 R15: 0000000000000000
Mar 15 11:04:43 arch kernel:  </TASK>
Mar 15 11:04:43 arch kernel: Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings
Mar 15 11:05:25 arch plasmashell[3254]: [3254:3254:0315/110525.998022:ERROR:device_event_log_impl.cc(192)] [11:05:25.997] Bluetooth: bluetooth_adapter_bluez.cc:1199 Failed to enable LL Privacy: org.freedesktop.DBus.Error.UnknownObject: Method "SetLLPrivacy" with signature "b" on interface "org.chromium.Bluetooth.Debug" doesn't exist
Mar 15 11:05:41 arch plasmashell[3254]: [3254:3254:0315/110541.573391:ERROR:device_event_log_impl.cc(192)] [11:05:41.572] Bluetooth: bluetooth_adapter_bluez.cc:1199 Failed to enable LL Privacy: org.freedesktop.DBus.Error.UnknownObject: Method "SetLLPrivacy" with signature "b" on interface "org.chromium.Bluetooth.Debug" doesn't exist
Mar 15 11:05:52 arch kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=367340 end=367341) time 195 us, min 763, max 767, scanline start 759, end 769
Mar 15 11:06:00 arch kwin_wayland[636]: This plugin does not support raise()

Will check if 6.0.2 fixes it once it drops in main repos

I also appear to have this issue even on the latest 6.0.2, it will randomly freeze and sometimes it seems kwin itself crashes and restarts, it appears to be getting worse for me since the update.