| Summary: | kwin_wayland busyloops processing "zwp_primary_selection_source_v1_requests" messages when screen is locked | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Vasily Khoruzhick <anarsoul> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kde, kdedev, nate, xaver.hugl |
| Priority: | NOR | ||
| Version: | 6.1.4 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screencast demonstrating the issue | ||
|
Description
Vasily Khoruzhick
2024-08-13 01:25:03 UTC
Could be related to BUG484323 which was originally reported for X11 Might be the same as bug 489644? (In reply to Zamundaaa from comment #2) > Might be the same as bug 489644? I'm running kwin-6.1.4, which already has a fix for 489644 (c91040d3deee8a2028562451fa056c002f35ae42 in origin/Plasma/6.1 branch), but I'm still seeing the issue. The backtrace looks suspect, it's apparently not using data_control waylandclipboard in kguiaddons. Is you kguiaddons build with wayland/from distro? (In reply to David Redondo from comment #4) > The backtrace looks suspect, it's apparently not using data_control > waylandclipboard in kguiaddons. Is you kguiaddons build with wayland/from > distro? It's coming from distro, it has wayland in dependencies and plasma-wayland-protocols in makedeps. See https://gitlab.archlinux.org/archlinux/packaging/packages/kguiaddons/-/blob/bdb649fb62712ac260968f5343b63d350561f408/PKGBUILD It is somehow related to clipboard. If I have anything (e.g. text) in clipboard prior to locking the screen, I see the issue. If I explicitly clear clipboard, I don't see the issue. BTW, it is not a cosmetic issue. On my 2020 Dell XPS 15 power consumption jumps x2 when screen is locked vs idle with screen unlocked. On wayland this code path should not wp_primary_clipboard but it seems it is. Can you share a relevant WAYLAND_DEBUG log plasmashell? The log is over 4M even when compressed, so I cannot attach it to the bug. See https://drive.google.com/file/d/10nyKKcdiKLcDA0L1laSgOmUK_-zpJKBB/view?usp=sharing (In reply to David Redondo from comment #8) > On wayland this code path should not wp_primary_clipboard but it seems it is. > Can you share a relevant WAYLAND_DEBUG log plasmashell? Do you need any other logs? Or could you give any pointers on how to debug it? It doesn't look like it's something trivial (at least it involves plasmashell and kwin) and I'm not really familiar with modern Plasma architecture. Another symptom is when I see the issue: sometimes if I open clipboard history in a tray, I don't see current clipboard contents in the list and clipboard contents reset to previous one, and CPU usage drops back to normal. Created attachment 173221 [details]
Screencast demonstrating the issue
It looks like clipboard widget isn't working properly and it may be related to the issue
With "Middle Click: Pastes selected text" disabled I don't see the issue anymore, so I'll use it as a workaround. In the log from https://bugs.kde.org/show_bug.cgi?id=491648#c9 you can see that something generates a ton of zwp_primary_selection_source_v1.offer/zwp_primary_selection_source_v1.cancelled pairs, so it's obviously something wrong in this functionality implementation. I'm not sure if it's Qt, Plasma or kwin. Feel free to ping me if you need more logs or if you want me to poke it with gdb. Can you post the output of `journalctl --boot --user-unit plasma-plasmashell`? Also do you have QT_QPA_PLATFORM envvar set?
> Linux/KDE Plasma: Archlinux
Are you using stock arch linux packages?
> Also do you have QT_QPA_PLATFORM envvar set? Nvm, it's irrelevant for this bug report. > Are you using stock arch linux packages? Oh I see https://bugs.kde.org/show_bug.cgi?id=491648#c5 --- As David pointed out in a comment above, plasmashell doesn't use the data control protocol, which is a red flag. Maybe WaylandClipboard fails to initialize, hopefully the logs would contain some info Setting NEEDSINFO while we wait for the output of `journalctl --boot --user-unit plasma-plasmashell` I cannot reproduce it anymore after upgrading to 6.1.5. I use stock Archlinux packages and I don't have QT_QPA_PLATFORM set. I guess you don't want `journalctl --boot --user-unit plasma-plasmashell` output if I cannot reproduce it? Yeah, there's no point to provide logs if you can't reproduce the issue. Thank you for the update. Please reopen the bug report if the issue comes back. In which case, please provide plasmashell logs and it won't hurt to capture wayland debug logs again too |