| Summary: | Plasma crashes due to libpipewire | ||
|---|---|---|---|
| Product: | [KDE Neon] neon | Reporter: | Loren <lordman1982> |
| Component: | Packages User Edition | Assignee: | Neon Bugs <neon-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | jr, lordman1982, meven.car, nate, neon-bugs-null, plasma-bugs-null, sitter |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Loren
2020-12-07 13:54:43 UTC
This is a bug in pipewire, was reported https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/422 and is already fixed https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/fc2b0b20ad4271b0c6f258451a82311b792b7a57 in pipewire 0.3.17 but neon doesn't ship it as of yet. apt show libpipewire-0.3-0 is at 0.3.16 in neon Dear neon maintainer, could you update libpipewire to 0.3.17 or is it out of reach ? Created attachment 133924 [details]
New crash information added by DrKonqi
plasmashell (5.20.4) using Qt 5.15.2
- What I was doing when the application crashed:
I was closing KDE Connect after having comed back from Firefox.
I have no issues using Firefow, just Plasma software.
-- Backtrace (Reduced):
#4 spa_hook_remove (hook=0x55f5d08718e8) at ../spa/include/spa/utils/hook.h:112
#5 spa_hook_list_clean (list=0x55f5d08ac318) at ../spa/include/spa/utils/hook.h:119
#6 pw_proxy_destroy (proxy=proxy@entry=0x55f5d08ac2c0) at ../src/pipewire/proxy.c:261
#7 0x00007f0afe6fa354 in pw_core_disconnect (core=0x55f5d08ac2c0) at ../src/pipewire/core.c:496
#8 0x00007f0afe79cc09 in PipeWireCore::~PipeWireCore (this=0x55f5d08718c0, __in_chrg=<optimized out>) at ./libtaskmanager/declarative/pipewirecore.cpp:53
Does the snapshot update today help? Hi Jonathan. I have no experienced the issue since I applied the update and rebooted the system, so it seems it has solved the issue. Thank you very much for the speed! |