XPost: linux.debian.bugs.dist
From: [email protected]

--=-dDh3ZvBfAb9CghhX8MV4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I think I have occasionally been encountering this (or a very
similar) issue. Like Abdurahman, I'm running trixie with KDE Plasma and
three times now in the past month the GPU has totally locked up. Two of
those times I had music playing in the background, and it continued
playing even after the GPU stopped responding.

Maybe relevant is that each time I've experienced this, I have had a
QEMU VM running (via libvirt) that has had 3D acceleration pass-though
enabled. I run this VM on a daily basis, so it may not be directly
related, but it is a commonality in all three crashes.

My GPU is a Sapphire NITRO+ RX 7900 XTX.

I was able to capture the kernel error and call trace (attached) the
first two times this happened, back on May 7 & 8 with kernel 6.12.25.
This morning it happened again with kernel 6.12.27, but I failed to
grab the kernel log before rebooting the system.

Back in May when this first happened, the only other relevant recent
change was an update of firmware-amd-graphics from 20241210-1 to
20250410-2. Because this issue didn't continue to occur for me, at the
time I wrote it off as a random issue. Having it happen again today
however indicates there is something, somewhere going wrong. Without a reproducer, though, I don't know if there's much more I can provide at
this time.

Mathias

--=-dDh3ZvBfAb9CghhX8MV4
Content-Disposition: attachment; filename="amdgpu errors"
Content-Type: text/plain; name="amdgpu errors"; charset="UTF-8" Content-Transfer-Encoding: base64
[SoupGate killed MIME-encoded file amdgpu errors (22068 bytes)]



--=-dDh3ZvBfAb9CghhX8MV4--

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEE1Bp60H32xfynSJ8cKe7i1uz0QvkFAmhBu+4ACgkQKe7i1uz0 Qvmf8w/8CO+dkSCNz8ouwzrqneTZ6wJVuK6s3LhfNJ+xJahngiLuW/J8RzsZ1deU hfvcMzWap6BqFAb4ZsYHEZlTF8/WLw6JospTQryvVm757FqKp48ZCGadBXKhj8Y/ Cjeo3lzv511kvACBC2850IO94CUGp/op56dVJL7GKtwyy7OK6uJ//vETYiPD1ESO OLQcfhY0KzTT7Qn4R21fDm4drs9CgfzOcImH/MhACRRDgjCw+dSvNU5Axi9JRnna N/Wq346KYMD+H5+DDIjntPaORi/DISyHxubo+OO1RIPX14S64kYXG3xuA4gy4YJR ahQXkfS5xuQqKcndK0EpZk2cBvohDRUfWUsMdoh6Xm2+0kPyygPpbC4rG65WCvGI DLL90F8zmCHUMbVrhFCEYE7nRFgThOIWQfjEZKM846P9XRtK1cSn2MS27+wOH4p9 vvUt31mo0bOmcAbhMbQ5qBSKyatf0B9woX7GzEzIhACri8XuY3wOaESaPLFnJN10 G2PJa+rwbOQNSnY3kj83WlrwM3NnKnMoec8YxjD3UGZNIYY6IUSrrL+XwytGC4W1 cwxuu9mirfBFNg56ONz0H9y3YLmITxdp5Y7Xqdx52Q/jAdW76aTWSBVsmEg5lxzF XyiNViccK/O2wcR8o8M8K+CXB4vjNys3k+7YE9yCRKgvcOBY9DU=
=6uhh
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Control: tags -1 + moreinfo

Hi,

On Sun, Apr 27, 2025 at 09:23:09PM -0500, Abdurahman Elmawi wrote:

Package: src:linux
Version: 6.12.22-1
Severity: critical
Tags: upstream
Justification: breaks unrelated software

Dear Maintainer,

While running Debian Trixie (Testing) with kernel 6.12.22-1, I encountered a serious amdgpu driver issue resulting in a full system lockup.

What led up to the situation:
- System is running Debian Trixie, with KDE Plasma desktop environment (installed via tasksel).
- I had a large number of windows open and was heavily multitasking.
- Suddenly, the system completely froze.
- Attempting to switch to a TTY (Ctrl+Alt+F4) took a very long time before any
text appeared.
- I eventually killed the KDE session and re-logged in, after which the system
returned to normal.

What exactly did you do (or not do) that was effective (or ineffective):
- Switching to TTY eventually worked (after long delay).
- Killing the KDE session recovered the system without a reboot.

What was the outcome of this action:
- I lost all unsaved data
- After re-logging in, system worked normally again.
- The issue has not reoccurred so far.

What outcome did you expect instead:
- The system should not lock up during normal multitasking.
- GPU/display updates should not cause hard stalls or flip timeouts.

Relevant logs from dmesg:
```
amdgpu 0000:0b:00.0: [drm] *ERROR* [CRTC:85:crtc-0] flip_done timed out amdgpu 0000:0b:00.0: [drm] *ERROR* [CRTC:85:crtc-0] commit wait timed out amdgpu 0000:0b:00.0: [drm] *ERROR* [PLANE:82:plane-7] commit wait timed out WARNING: CPU: 3 PID: 994 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:8646 amdgpu_dm_atomic_commit_tail
```

Tracebacks point to amdgpu_dm_atomic_commit_tail

Hardware details:
- Motherboard: ASUS TUF GAMING X570-PLUS (Wi-Fi)
- GPU: AMD Radeon RX 6600
- Kernel: 6.12.22-amd64
- Firmware: Up-to-date firmware-amd-graphics package installed.

Notes:
- This problem may be related to other recent AMDGPU instability reports on 6.12.x, but this is distinct: no PCIe AER errors were present, and no VRAM leaks were observed prior to the crash.
- The bug appears in normal operation, not just after suspend/resume.

Can you please retest this with the most current 6.12.32-1 and report
back if the issue persist? If so can you please again provide a full
log?

If this will look like an upstream issue we might ask you to fill an
upstream issue at https://gitlab.freedesktop.org/drm/amd/, but we
would like to see if the issue still persist on most recent version
and have a look at a fresh boot log.

Regards,
Salvatore

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Hello, it's still happening at least once a day for me with 6.12.33+deb13-amd64 and AMD 9070.

Relevant journalctl and dmesg:

Jul 03 10:00:16 RED kernel: Linux version 6.12.33+deb13-amd64 ([email protected]) (x86_64-linux-gnu-gcc-14 (Debian 14.2.0-19) 14.2.0,>
Jul 03 10:00:16 RED kernel: Command line: BOOT_IMAGE=/vmlinuz-6.12.33+deb13-amd64 root=/dev/mapper/RED--vg-root ro quiet
...
Jul 03 15:34:03 RED kernel: amdgpu 0000:03:00.0: [drm] *ERROR* [CRTC:79:crtc-0] flip_done timed out
Jul 03 15:34:12 RED dbus-daemon[1762]: [session uid=1000 pid=1762 pidfd=5] Activating via systemd: service name='org.kde.spectacle' unit='app-org.>
Jul 03 15:34:12 RED systemd[1739]: Starting app-org.kde.spectacle.service - Spectacle screenshot capture utility...
Jul 03 15:34:12 RED dbus-daemon[1762]: [session uid=1000 pid=1762 pidfd=5] Successfully activated service 'org.kde.spectacle'
Jul 03 15:34:12 RED systemd[1739]: Started app-org.kde.spectacle.service - Spectacle screenshot capture utility.
Jul 03 15:34:16 RED spectacle[22935]: KWin screenshot request failed:
Jul 03 15:34:16 RED spectacle[22935]: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message b>
Jul 03 15:34:16 RED spectacle[22935]: Potentially relevant information:
Jul 03 15:34:16 RED spectacle[22935]: - Method: CaptureScreen
Jul 03 15:34:16 RED spectacle[22935]: - Method specific arguments: "DP-2"
Jul 03 15:34:19 RED kwin_wayland_wrapper[1822]: kwin_wayland_drm: Pageflip timed out! This is a bug in the amdgpu kernel driver
Jul 03 15:34:19 RED kwin_wayland_wrapper[1822]: kwin_wayland_drm: Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues
Jul 03 15:34:19 RED kwin_wayland_wrapper[1822]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland >
Jul 03 15:34:28 RED kernel: amdgpu 0000:03:00.0: [drm] *ERROR* flip_done timed out
Jul 03 15:34:28 RED kernel: amdgpu 0000:03:00.0: [drm] *ERROR* [CRTC:79:crtc-0] commit wait timed out
Jul 03 15:34:38 RED kernel: amdgpu 0000:03:00.0: [drm] *ERROR* flip_done timed out
Jul 03 15:34:38 RED kernel: amdgpu 0000:03:00.0: [drm] *ERROR* [PLANE:76:plane-6] commit wait timed out
Jul 03 15:34:38 RED kernel: ------------[ cut here ]------------
Jul 03 15:34:38 RED kernel: WARNING: CPU: 1 PID: 1414 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:8684 amdgpu_dm_atomic_commit_>
Jul 03 15:34:38 RED kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device rfkill qrtr binfmt_misc nls_ascii nls_cp437 vfat f>
Jul 03 15:34:38 RED kernel:  realtek sha1_ssse3 nvme_core mdio_devres aesni_intel libphy gf128mul crypto_simd cryptd i2c_piix4 i2c_smbus usb_commo>
Jul 03 15:34:38 RED kernel: CPU: 1 UID: 0 PID: 1414 Comm: systemd-logind Not tainted 6.12.33+deb13-amd64 #1  Debian 6.12.33-1
Jul 03 15:34:38 RED kernel: Hardware name: ASRock X870 Pro RS/X870 Pro RS, BIOS 3.30 06/16/2025
Jul 03 15:34:38 RED kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x39bb/0x3a80 [amdgpu]
Jul 03 15:34:38 RED kernel: Code: 0f 0b e9 75 f3 ff ff 0f 0b 49 8d 87 58 31 04 00 c6 85 38 fe ff ff 00 48 89 85 48 fe ff ff e9 6f cc ff ff 0f 0b e>
Jul 03 15:34:38 RED kernel: RSP: 0018:ffffab8f81ba36c8 EFLAGS: 00010082
Jul 03 15:34:38 RED kernel: RAX: 0000000000000001 RBX: 0000000000000286 RCX: ffff9f77c0944118
Jul 03 15:34:38 RED kernel: RDX: 0000000000000001 RSI: 0000000000000297 RDI: ffff9f77e0780178
Jul 03 15:34:38 RED kernel: RBP: ffffab8f81ba3910 R08: ffffab8f81ba35b4 R09: 0000000000000000
Jul 03 15:34:38 RED kernel: R10: ffffab8f81ba3620 R11: ffffab8f81ba3624 R12: 0000000000000000
Jul 03 15:34:38 RED kernel: R13: 0000000000000001 R14: ffff9f77c0944000 R15: ffff9f79543cc400
Jul 03 15:34:38 RED kernel: FS:  00007f3bbac7ca00(0000) GS:ffff9f7e7d680000(0000) knlGS:0000000000000000
Jul 03 15:34:38 RED kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 03 15:34:38 RED kernel: CR2: 0000254c025d50a0 CR3: 00000001227c0000 CR4: 0000000000f50ef0
Jul 03 15:34:38 RED kernel: PKRU: 55555554
Jul 03 15:34:38 RED kernel: Call Trace:
Jul 03 15:34:38 RED kernel:  <TASK>
Jul 03 15:34:38 RED kernel:  commit_tail+0x91/0x130 [drm_kms_helper]
Jul 03 15:34:38 RED kernel:  drm_atomic_helper_commit+0x11a/0x140 [drm_kms_helper]
Jul 03 15:34:38 RED kernel:  drm_atomic_commit+0xa6/0xe0 [drm]
Jul 03 15:34:38 RED kernel:  ? __pfx___drm_printfn_info+0x10/0x10 [drm]
Jul 03 15:34:38 RED kernel:  drm_client_modeset_commit_atomic+0x203/0x250 [drm]
Jul 03 15:34:38 RED kernel:  drm_client_modeset_commit_locked+0x5a/0x160 [drm] Jul 03 15:34:38 RED kernel:  __drm_fb_helper_restore_fbdev_mode_unlocked+0x5e/0xd0 [drm_kms_helper]
Jul 03 15:34:38 RED kernel:  drm_fb_helper_set_par+0x30/0x40 [drm_kms_helper] Jul 03 15:34:38 RED kernel:  fb_set_var+0x25c/0x460
Jul 03 15:34:38 RED kernel:  ? update_load_avg+0x7e/0x7b0
Jul 03 15:34:38 RED kernel:  ? update_curr+0x98/0x290
Jul 03 15:34:38 RED kernel:  ? place_entity+0x1b/0x130
Jul 03 15:34:38 RED kernel:  ? sched_clock+0x10/0x30
Jul 03 15:34:38 RED kernel:  ? sched_clock_cpu+0xf/0x1d0
Jul 03 15:34:38 RED kernel:  ? update_load_avg+0x7e/0x7b0
Jul 03 15:34:38 RED kernel:  ? update_curr+0x98/0x290
Jul 03 15:34:38 RED kernel:  ? place_entity+0x1b/0x130
Jul 03 15:34:38 RED kernel:  fbcon_blank+0x271/0x330
Jul 03 15:34:38 RED kernel:  do_unblank_screen+0xad/0x150
Jul 03 15:34:38 RED kernel:  complete_change_console+0x54/0x120
Jul 03 15:34:38 RED kernel:  vt_ioctl+0xec3/0x12b0
Jul 03 15:34:38 RED kernel:  tty_ioctl+0xe2/0x8a0
Jul 03 15:34:38 RED kernel:  ? __seccomp_filter+0x303/0x520
Jul 03 15:34:38 RED kernel:  __x64_sys_ioctl+0x91/0xd0
Jul 03 15:34:38 RED kernel:  do_syscall_64+0x82/0x190
Jul 03 15:34:38 RED kernel:  ? switch_fpu_return+0x4e/0xd0

[continued in next message]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Hi Leon,

On Thu, Jul 03, 2025 at 04:54:57PM +0200, Leon Moser wrote:

Hello, it's still happening at least once a day for me with 6.12.33+deb13-amd64 and AMD 9070.

Relevant journalctl and dmesg:

Jul 03 10:00:16 RED kernel: Linux version 6.12.33+deb13-amd64 ([email protected]) (x86_64-linux-gnu-gcc-14 (Debian 14.2.0-19) 14.2.0,>
Jul 03 10:00:16 RED kernel: Command line: BOOT_IMAGE=/vmlinuz-6.12.33+deb13-amd64 root=/dev/mapper/RED--vg-root ro quiet
...
Jul 03 15:34:03 RED kernel: amdgpu 0000:03:00.0: [drm] *ERROR* [CRTC:79:crtc-0] flip_done timed out
Jul 03 15:34:12 RED dbus-daemon[1762]: [session uid=1000 pid=1762 pidfd=5] Activating via systemd: service name='org.kde.spectacle' unit='app-org.>
Jul 03 15:34:12 RED systemd[1739]: Starting app-org.kde.spectacle.service - Spectacle screenshot capture utility...
Jul 03 15:34:12 RED dbus-daemon[1762]: [session uid=1000 pid=1762 pidfd=5] Successfully activated service 'org.kde.spectacle'
Jul 03 15:34:12 RED systemd[1739]: Started app-org.kde.spectacle.service - Spectacle screenshot capture utility.
Jul 03 15:34:16 RED spectacle[22935]: KWin screenshot request failed:
Jul 03 15:34:16 RED spectacle[22935]: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message b>
Jul 03 15:34:16 RED spectacle[22935]: Potentially relevant information:
Jul 03 15:34:16 RED spectacle[22935]: - Method: CaptureScreen
Jul 03 15:34:16 RED spectacle[22935]: - Method specific arguments: "DP-2"
Jul 03 15:34:19 RED kwin_wayland_wrapper[1822]: kwin_wayland_drm: Pageflip timed out! This is a bug in the amdgpu kernel driver
Jul 03 15:34:19 RED kwin_wayland_wrapper[1822]: kwin_wayland_drm: Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues
Jul 03 15:34:19 RED kwin_wayland_wrapper[1822]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland >
Jul 03 15:34:28 RED kernel: amdgpu 0000:03:00.0: [drm] *ERROR* flip_done timed out
Jul 03 15:34:28 RED kernel: amdgpu 0000:03:00.0: [drm] *ERROR* [CRTC:79:crtc-0] commit wait timed out
Jul 03 15:34:38 RED kernel: amdgpu 0000:03:00.0: [drm] *ERROR* flip_done timed out
Jul 03 15:34:38 RED kernel: amdgpu 0000:03:00.0: [drm] *ERROR* [PLANE:76:plane-6] commit wait timed out
Jul 03 15:34:38 RED kernel: ------------[ cut here ]------------
Jul 03 15:34:38 RED kernel: WARNING: CPU: 1 PID: 1414 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:8684 amdgpu_dm_atomic_commit_>
Jul 03 15:34:38 RED kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device rfkill qrtr binfmt_misc nls_ascii nls_cp437 vfat f>
Jul 03 15:34:38 RED kernel:  realtek sha1_ssse3 nvme_core mdio_devres aesni_intel libphy gf128mul crypto_simd cryptd i2c_piix4 i2c_smbus usb_commo>
Jul 03 15:34:38 RED kernel: CPU: 1 UID: 0 PID: 1414 Comm: systemd-logind Not tainted 6.12.33+deb13-amd64 #1  Debian 6.12.33-1
Jul 03 15:34:38 RED kernel: Hardware name: ASRock X870 Pro RS/X870 Pro RS, BIOS 3.30 06/16/2025
Jul 03 15:34:38 RED kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x39bb/0x3a80 [amdgpu]
Jul 03 15:34:38 RED kernel: Code: 0f 0b e9 75 f3 ff ff 0f 0b 49 8d 87 58 31 04 00 c6 85 38 fe ff ff 00 48 89 85 48 fe ff ff e9 6f cc ff ff 0f 0b e>
Jul 03 15:34:38 RED kernel: RSP: 0018:ffffab8f81ba36c8 EFLAGS: 00010082
Jul 03 15:34:38 RED kernel: RAX: 0000000000000001 RBX: 0000000000000286 RCX: ffff9f77c0944118
Jul 03 15:34:38 RED kernel: RDX: 0000000000000001 RSI: 0000000000000297 RDI: ffff9f77e0780178
Jul 03 15:34:38 RED kernel: RBP: ffffab8f81ba3910 R08: ffffab8f81ba35b4 R09: 0000000000000000
Jul 03 15:34:38 RED kernel: R10: ffffab8f81ba3620 R11: ffffab8f81ba3624 R12: 0000000000000000
Jul 03 15:34:38 RED kernel: R13: 0000000000000001 R14: ffff9f77c0944000 R15: ffff9f79543cc400
Jul 03 15:34:38 RED kernel: FS:  00007f3bbac7ca00(0000) GS:ffff9f7e7d680000(0000) knlGS:0000000000000000
Jul 03 15:34:38 RED kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 03 15:34:38 RED kernel: CR2: 0000254c025d50a0 CR3: 00000001227c0000 CR4: 0000000000f50ef0
Jul 03 15:34:38 RED kernel: PKRU: 55555554
Jul 03 15:34:38 RED kernel: Call Trace:
Jul 03 15:34:38 RED kernel:  <TASK>
Jul 03 15:34:38 RED kernel:  commit_tail+0x91/0x130 [drm_kms_helper]
Jul 03 15:34:38 RED kernel:  drm_atomic_helper_commit+0x11a/0x140 [drm_kms_helper]
Jul 03 15:34:38 RED kernel:  drm_atomic_commit+0xa6/0xe0 [drm]
Jul 03 15:34:38 RED kernel:  ? __pfx___drm_printfn_info+0x10/0x10 [drm]
Jul 03 15:34:38 RED kernel:  drm_client_modeset_commit_atomic+0x203/0x250 [drm]
Jul 03 15:34:38 RED kernel:  drm_client_modeset_commit_locked+0x5a/0x160 [drm]
Jul 03 15:34:38 RED kernel:  __drm_fb_helper_restore_fbdev_mode_unlocked+0x5e/0xd0 [drm_kms_helper]
Jul 03 15:34:38 RED kernel:  drm_fb_helper_set_par+0x30/0x40 [drm_kms_helper]
Jul 03 15:34:38 RED kernel:  fb_set_var+0x25c/0x460
Jul 03 15:34:38 RED kernel:  ? update_load_avg+0x7e/0x7b0
Jul 03 15:34:38 RED kernel:  ? update_curr+0x98/0x290
Jul 03 15:34:38 RED kernel:  ? place_entity+0x1b/0x130
Jul 03 15:34:38 RED kernel:  ? sched_clock+0x10/0x30
Jul 03 15:34:38 RED kernel:  ? sched_clock_cpu+0xf/0x1d0
Jul 03 15:34:38 RED kernel:  ? update_load_avg+0x7e/0x7b0
Jul 03 15:34:38 RED kernel:  ? update_curr+0x98/0x290
Jul 03 15:34:38 RED kernel:  ? place_entity+0x1b/0x130
Jul 03 15:34:38 RED kernel:  fbcon_blank+0x271/0x330
Jul 03 15:34:38 RED kernel:  do_unblank_screen+0xad/0x150
Jul 03 15:34:38 RED kernel:  complete_change_console+0x54/0x120

[continued in next message]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Hello Salvatore, thanks for the reply.
If you search for 'flip_done timed out' in the amd gitlab there are several very similar issues.
For example: https://gitlab.freedesktop.org/drm/amd/-/issues/4345
Many of the replies in this one (including my own) are apparently the same issue I have.

Do you think I should still open a new issue?

Also it does seem stable using arch with kernel 6.15.4, or at least much more stable than before (3 days uptime so far). With debian 6.12.33 it crashes daily.

Cordially,
Leon
--
Secured with Tuta Mail:
https://tuta.com/free-email


5 Jul 2025, 20:17 by [email protected]:

Hi Leon,

On Thu, Jul 03, 2025 at 04:54:57PM +0200, Leon Moser wrote:

Hello, it's still happening at least once a day for me with 6.12.33+deb13-amd64 and AMD 9070.

Relevant journalctl and dmesg:

Jul 03 10:00:16 RED kernel: Linux version 6.12.33+deb13-amd64 ([email protected]) (x86_64-linux-gnu-gcc-14 (Debian 14.2.0-19) 14.2.0,>
Jul 03 10:00:16 RED kernel: Command line: BOOT_IMAGE=/vmlinuz-6.12.33+deb13-amd64 root=/dev/mapper/RED--vg-root ro quiet
...
Jul 03 15:34:03 RED kernel: amdgpu 0000:03:00.0: [drm] *ERROR* [CRTC:79:crtc-0] flip_done timed out
Jul 03 15:34:12 RED dbus-daemon[1762]: [session uid=1000 pid=1762 pidfd=5] Activating via systemd: service name='org.kde.spectacle' unit='app-org.>
Jul 03 15:34:12 RED systemd[1739]: Starting app-org.kde.spectacle.service - Spectacle screenshot capture utility...
Jul 03 15:34:12 RED dbus