Summary: | plasma is terminated because "invalid arguments for zwp_linux_buffer_params_v1.add" | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Lewis Lakerink <lewis> |
Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | kde, m.wege, nate |
Priority: | NOR | Keywords: | wayland-only |
Version: | 5.22.1 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
WAYLAND_DEBUG=1 Plasma shell crash with same error
WAYLAND_DEBUG=1 plasmashell - same error without screenshare troubles |
Description
Lewis Lakerink
2021-06-10 02:30:55 UTC
We need a backtrace so we can act effectively on crashes Is there a stack trace that's usable if the process doesn't actually segfault, but terminates itself? Do you need a wayland debug trace? Oh sorry, I just read crash, yeah I think a wayland trace would be useful Created attachment 139357 [details]
WAYLAND_DEBUG=1 Plasma shell crash with same error
It looks like both crashes have been caused by pipewire streams failing perhaps? Which is unusual, since plasmashell works fine, often for hours - including the thumbnails of applications in the launcher.
Created attachment 139362 [details]
WAYLAND_DEBUG=1 plasmashell - same error without screenshare troubles
I had a crash with the same wayland error - but this time without any problem referencing screensharing.
I do not immidately have an idea, from the log before the crash [1046822.980] -> zwp_linux_dmabuf_v1@25.create_params(new id zwp_linux_buffer_params_v1@56) [1046823.082] -> zwp_linux_buffer_params_v1@56.add(fd 55, 0, 0, 512, 33554436, 1079097857) [1046823.174] -> zwp_linux_buffer_params_v1@56.add(fd 56, 1, 917504, 512, 33554436, 1079097857) [1046823.247] -> zwp_linux_buffer_params_v1@56.create_immed(new id wl_buffer@253, 120, 1728, 875713089, 0) and then later [1050257.152] -> zwp_linux_dmabuf_v1@25.create_params(new id zwp_linux_buffer_params_v1@251) [1050257.302] -> zwp_linux_buffer_params_v1@251.add(fd 73, 0, 0, 512, 33554436, 1079097857) [1050257.466] -> zwp_linux_buffer_params_v1@251.add(fd 74, 1, 917504, 512, 33554436, 1079097857) [1050257.634] -> zwp_linux_buffer_params_v1@251.create_immed(new id wl_buffer@267, 120, 1728, 875713089, 0) looks to be using the same arguments but is wrong Likely related to https://bugs.kde.org/show_bug.cgi?id=438097 I believe this is now fixed as a duplicate of 438097 *** This bug has been marked as a duplicate of bug 438097 *** |