I just upgraded to 5.24 beta and I am getting intermittent crashes when clicking on the kicker application menu and then placing the cursor on a sub-menu, for example "Internet". This happens on wayland. Completely random, I cannot reproduce consistently and there is no core dump... QWaylandDataOffer: timeout reading from pipe QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection QWaylandDataOffer: timeout reading from pipe QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection QWaylandDataOffer: timeout reading from pipe QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection QWaylandDataOffer: timeout reading from pipe QWaylandDataOffer: error reading data for mimeType application/x-kde-cutselection The Wayland connection broke. Did the Wayland compositor die? Operating System: Arch Linux KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-1-amd-staging-drm-next-git-01870-g8e74e0923ed4 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT
I am getting closer to reproducing this now. the bug is related to clipboard behavior. 1. Use flameshot to select a rectangle on the desktop and click the copy to clipboard button. we now have the image in the clipboard. 2. Right click on the desktop and click "Paste Clipboard Contents". Nothing gets pasted but this is ok 3. Click on the kicker application menu and then placing the cursor on a sub-menu, for example "Internet" 4. plasma/kwin/something crashes I wish obs worked for me on wayland so I could record this but sadly it does not...
I suspect a killer part is we're closing flameshot there. So we're copying klipper -> plasmashell This is known to deadlock on wayland. The "crash" is just we have a new window so kwin sends a ping to see if the client is alive. This bug a duplicate somewhere in plasmashell.
I can no longer reproduce this on beta 5.26. A recent plasma or flameshot update must have fixed this issue. I will mark it as resolved.