Summary: | [Wayland] Plasmashell freezes briefly after focusing the desktop if it was started with a non-empty clipboard history | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Firlaev-Hans <firlaevhans.fiete> |
Component: | generic-performance | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | dev.bacteriostat, kde, kustodian, leguen.yannick, nate, sn1128231220jd |
Priority: | NOR | Keywords: | wayland |
Version: | 5.24.3 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Firlaev-Hans
2022-03-17 18:20:25 UTC
One important detail I forgot to mention in my original report is that this only happens when switching from a desktop with a focused window to an empty desktop, not when switching between empty desktops or between desktops that both have windows on them. In fact, it doesn't seem to be related to switching desktops directly at all. The same thing happens when you have a window focused and then click on the desktop to un-focus the window. I updated the title accordingly. So in general, it happens when switching from having a window focused to having no window focused. But still, it's inconsistent / doesn't happen in every session, so that's always fun to debug. Here's some possibly (but maybe not at all) related info from journalctl: QWaylandDataOffer: timeout reading from pipe QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection Cannot reproduce on Wayland when switching from a desktop with a focused window to an empty window. You said that the panel and other Plasma components freeze, and then you also said, "it happens throughout the entire session". Can you clarify? Does just the panel freeze, or does everything freeze? Are apps also frozen? Or just the Plasma panel and other Plasma components? During this freeze, can you open KRunner with Alt+Space? (In reply to Nate Graham from comment #2) > Does just the panel freeze, or does everything > freeze? Are apps also frozen? Or just the Plasma panel and other Plasma > components? During this freeze, can you open KRunner with Alt+Space? Just the Panels and other Plasma components, such as visible notifications. Application windows don't freeze, nor does KRunner. I can't test if Plasmoids on the desktop are affected too because while I get this bug right now I can't add widgets right now because of Bug 439159. > "it happens throughout the entire session". Can you clarify? By that I meant that when I do encounter this bug, I can consistently reproduce it until the session ends or is suspended. However I just realized that this isn't entirely true, I was able to consistently reproduce just a moment ago but now it's been a few minutes and even though I'm still in the same session and did nothing special it suddenly stopped happening. So it doesn't surprise me that you couldn't reproduce it on first try, since it only happens some of the time. Frustratingly I don't know how to reproduce this reliably, it just randomly seems to happen some of the time. But I have encountered this bug many times on multiple different computers, so I'd be surprised if nobody else besides me (and Bug 451840 ?) is ever able to reproduce this. Thanks for the info. I have now found a reliable way to reproduce this issue:
1. Completely fill up your Klipper history with anything
2. Either restart plasmashell yourself or reboot / log out and back in
3. Focus a window, then focus the desktop
4. Clear the clipboard history, then repeat step 3
After step 3 you will notice this brief freeze. After step 4, you won't.
This is still reproducible on Plasma 5.25.0 / Frameworks 5.95.0 on Arch.
This journal log is definitely related as it is printed every time the freeze happens:
>plasmashell[5515]: QWaylandDataOffer: timeout reading from pipe
>plasmashell[5515]: QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection
Minor correction, the clipboard doesn't need to be full, it just needs to be *not* empty when plasmashell (re)starts for this bug to trigger Same issue here, on Archlinux and Plasma 5.25.2 on wayland (no issue on X11). I've got the same messages in the journal log when the freeze happens. However on my end it only seems to happen when there's a document in the clipboard, it doesn't happen with text selection in the clipboard. (In reply to Yannick from comment #7) > Same issue here, on Archlinux and Plasma 5.25.2 on wayland (no issue on X11). > I've got the same messages in the journal log when the freeze happens. > > However on my end it only seems to happen when there's a document in the > clipboard, it doesn't happen with text selection in the clipboard. Yes, you're right. It only happens when your clipboard contains files rather than just text. Same on Tumbleweed (Plasma 5.25.3) when using Wayland. It happens whenever there are some non-text items in the clipboard history. But 454379 appears to be the same issue and has some more information (basically, it also happens when instead of restarting plasmashell you close dolphin after copying a file). Also, I have found the criteria for reproducing this bug is not only that you need to have non-text items like files in your clipboard, these items must also be the top most item in the clipboard history. i. e. if you have a file in your clipboard but also copied text after that, the issue doesn't happen / stops happening. *** This bug has been marked as a duplicate of bug 454379 *** I noticed the same thing, but I'm using the Icon-only Task Manager. Every time I move my cursor over the open windows' icons the cursor lags. I thought that it was because of generating window thumbnails, but that's not the issue. I disabled window thumbnails in the Icon-only Task Manager and the lag is still there when hovering over icons of the open windows. This is very annoying and it's breaking my Plasma experience. Strahinja, that you're describing is something else. Can you submit a new bug report for it? Thanks! |