Bug 450922 - [Wayland] Plasmashell crashes when adjusting the volume when a fullscreen app is running (?)
Summary: [Wayland] Plasmashell crashes when adjusting the volume when a fullscreen app...
Status: RESOLVED DUPLICATE of bug 452806
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 5.24.2
Platform: Arch Linux Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2022-02-27 12:43 UTC by Jaroslav Krpálek
Modified: 2023-04-12 07:48 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Backtrace from the crash. Off-topic, debug symbols on Arch are a blessing now. (34.23 KB, text/vnd.kde.kcrash-report)
2022-02-27 12:43 UTC, Jaroslav Krpálek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Krpálek 2022-02-27 12:43:00 UTC
Created attachment 147170 [details]
Backtrace from the crash. Off-topic, debug symbols on Arch are a blessing now.

SUMMARY
When I tried adjusting the volume, I lost audio, so I tried changing the audio source and it crashed after a few seconds.

STEPS TO REPRODUCE
Note: I was unable to reproduce this the second time, but I will include the steps I did anyway.
1. Play a game on fullscreen (in my case, Grand Theft Auto V)
2. Start adjusting the volume via the dedicated volume keys on the keyboard
3. Lose audio (just happened for me, I have no idea why)
4. Go to the volume panel and try changing sources
5. Go back in the game
6. Plasmashell crashed

OBSERVED RESULT
Plasmashell crashed and respawned.

EXPECTED RESULT
The volume should change without the system having a mental breakdown.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux x86_64, kernel 5.16.11-zen1-1-zen
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version:  5.15.2
Comment 1 Nate Graham 2022-03-21 04:10:22 UTC
Pasting backtrace inline for searchability:

[KCrash Handler]
#6  0x00007ff59b0d4260 in wl_proxy_get_version () at /usr/lib/libwayland-client.so.0
#7  0x00007ff52cb989df in xdg_positioner_set_gravity (gravity=2873, xdg_positioner=0x0) at /usr/src/debug/build/src/plugins/shellintegration/xdg-shell/wayland-xdg-shell-client-protocol.h:822
#8  QtWayland::xdg_surface::ack_configure(unsigned int) (serial=2873, this=0x55d99115bc68) at /usr/src/debug/build/src/plugins/shellintegration/xdg-shell/qwayland-xdg-shell.cpp:303
#9  QtWaylandClient::QWaylandXdgSurface::applyConfigure() (this=0x55d99115bc50) at /usr/src/debug/qtwayland/src/plugins/shellintegration/xdg-shell/qwaylandxdgshell.cpp:337
#10 0x00007ff596e3c1aa in QtWaylandClient::QWaylandWindow::doApplyConfigure() (this=0x55d98e30d6b0) at /usr/src/debug/qtwayland/src/client/qwaylandwindow.cpp:505
#11 QtWaylandClient::QWaylandWindow::doApplyConfigure() (this=this@entry=0x55d98e30d6b0) at /usr/src/debug/qtwayland/src/client/qwaylandwindow.cpp:499
#12 0x00007ff596e3c849 in QtWaylandClient::QWaylandWindow::setCanResize(bool) (this=0x55d98e30d6b0, canResize=<optimized out>) at /usr/src/debug/qtwayland/src/client/qwaylandwindow.cpp:520
#13 0x00007ff59aa2588d in QSGRenderThread::syncAndRender(QImage*) (this=0x55d992432830, grabImage=0x0) at /usr/src/debug/qtdeclarative/src/quick/scenegraph/qsgthreadedrenderloop.cpp:870
#14 0x00007ff59aa29ef0 in QSGRenderThread::run() (this=0x55d992432830) at /usr/src/debug/qtdeclarative/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1043
#15 0x00007ff598fd48bc in QThreadPrivate::start(void*) (arg=0x55d992432830) at thread/qthread_unix.cpp:331
#16 0x00007ff598b4d5c2 in start_thread () at /usr/lib/libc.so.6
#17 0x00007ff598bd2584 in clone () at /usr/lib/libc.so.6
Comment 2 David Edmundson 2022-03-21 22:45:12 UTC
doApplyConfigure shouldn't run in the render thread. I meant to fix that the other day.

It's an upstream bug but lets keep this open till it's reported and fixed.
Comment 3 Nate Graham 2022-05-05 21:31:01 UTC
Not a duplicate of Bug 452806?
Comment 4 David Edmundson 2023-04-12 07:48:21 UTC
yep, well spotted

*** This bug has been marked as a duplicate of bug 452806 ***