| Summary: | In Wayland session, plasmashell crashes immediately and frequently | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | luciros601084 |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | itahilinus, kde, nate, tomblackwhite |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 6.1.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | crashing-clip-voidlinux | ||
|
Description
luciros601084
2024-06-20 14:28:52 UTC
Created attachment 170683 [details]
crashing-clip-voidlinux
Very clear screen recording, thanks. Unfortunately no KDE code is implicated in the backtrace. Seems like maybe a Wayland client/server error or a protocol error or something? Reply to change in title: This is happening on real hardware too (at end video, you can see I was not able to stop screen recorder, my desktop shell was already crashed) I confirm it also happens on my machine (on real hardware). I'm using CRUX The specific error is as follows: listener function for opcode 5 of org_kde_plasma_window_management is NULL It happens when you interact with the taskbar in any way (for example hovering on a pinned icons produces a tooltip that crashes plasmashell immediately). listener function for opcode 5 of org_kde_plasma_window_management is NULL
opcode 5 is { "stacking_order_changed_2", "17", plasma_window_management_types + 0 },
This is another case of something build with an older wayland protocol and due to qtwaylandscanner defaulting to public-code and the wl_ interface being exported, the linker ultimately resolving it to the older symbol.
See https://bugs.kde.org/show_bug.cgi?id=481791 hitting Neon before.
We cannot do anything about this until Qt 6.8 where we can control/disable this. Until then everything needs to be build against latest plasma-wayland-protocols.
...So please tell your distro! (In reply to Nate Graham from comment #6) > ...So please tell your distro! Void Linux (In reply to David Redondo from comment #5) > listener function for opcode 5 of org_kde_plasma_window_management is NULL > > opcode 5 is { "stacking_order_changed_2", "17", > plasma_window_management_types + 0 }, > > This is another case of something build with an older wayland protocol and > due to qtwaylandscanner defaulting to public-code and the wl_ interface > being exported, the linker ultimately resolving it to the older symbol. > See https://bugs.kde.org/show_bug.cgi?id=481791 hitting Neon before. > > We cannot do anything about this until Qt 6.8 where we can control/disable > this. Until then everything needs to be build against latest > plasma-wayland-protocols. I have rebuilt all plasma packages again plasma-wayland-protocols-1.13.0 , but is still crashing I don't mean tell me what your distro is, I mean tell the people involved with your distro about this issue! :D In my case, I rebuilt all packages dependent on plasma-wayland-protocols and it works now. Ok I was re-built of some kde framework packages, thing are stable now |