Bug 478911

Summary: KDE Crash Handler reports startplasma-x11 segmentation fault, Plasma crashes on close
Product: [Plasma] plasmashell Reporter: Wilbur Jaywright <zargulthewizard>
Component: Startup processAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: kde, nicolas.fella
Priority: NOR    
Version First Reported In: 5.27.10   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: What I see on login
Developer info from the crash handler
Developer info from the crash handler (Wayland)

Description Wilbur Jaywright 2023-12-23 01:54:52 UTC
Created attachment 164380 [details]
What I see on login

SUMMARY
So, I log in, and KDE Crash Handler reports that startplasma-x11 died due to a segmentation fault. The desktop works normally, until I close the crash handler window, at which point Plasma crashes within a few seconds, throwing me back out to SDDM.


STEPS TO REPRODUCE
1. Log in.
2. Close the appearing crash handler window.

OBSERVED RESULT
Plasma is ded.

EXPECTED RESULT
Plasma is not ded (and the crash handler never shows up in the first place).

SOFTWARE/OS VERSIONS
Windows: X
macOS: X
Linux/KDE Plasma: Fedora 39 x64
(available in About System)
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11

ADDITIONAL INFORMATION
Using NVidia proprietary drivers.
Comment 1 Wilbur Jaywright 2023-12-23 01:58:26 UTC
Created attachment 164381 [details]
Developer info from the crash handler
Comment 2 Wilbur Jaywright 2023-12-23 02:07:23 UTC
Created attachment 164383 [details]
Developer info from the crash handler (Wayland)

Dude, I tried using Wayland, and the same thing happened, but startplasma-wayland.
Comment 3 Wilbur Jaywright 2023-12-23 02:28:28 UTC
This seems to have been fixed by a simple reboot? I had already done the normal reboot after updates.
Comment 4 Nicolas Fella 2023-12-23 15:26:09 UTC
[KCrash Handler]
#4  0x00007f488a103080 in vorbis_synthesis () at /lib64/libvorbis.so.0
#5  0x00007f486dd480de in vorbis_dec_handle_frame () at /lib64/gstreamer-1.0/libgstvorbis.so
#6  0x00007f4878907ad7 in gst_audio_decoder_push_buffers.lto_priv () at /lib64/libgstaudio-1.0.so.0
#7  0x00007f487890800d in gst_audio_decoder_chain_forward () at /lib64/libgstaudio-1.0.so.0
#8  0x00007f4878908e4f in gst_audio_decoder_chain () at /lib64/libgstaudio-1.0.so.0
#9  0x00007f4878cf3e9c in gst_pad_chain_data_unchecked () at /lib64/libgstreamer-1.0.so.0
#10 0x00007f4878cf723e in gst_pad_push_data () at /lib64/libgstreamer-1.0.so.0
#11 0x00007f4878cf7874 in gst_pad_push () at /lib64/libgstreamer-1.0.so.0
#12 0x00007f486fe79184 in gst_multi_queue_loop.lto_priv () at /lib64/gstreamer-1.0/libgstcoreelements.so
#13 0x00007f4878d23f04 in gst_task_func () at /lib64/libgstreamer-1.0.so.0
#14 0x00007f488a946db2 in g_thread_pool_thread_proxy.lto_priv () at /lib64/libglib-2.0.so.0
#15 0x00007f488a942523 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#16 0x00007f488ceac897 in start_thread () at /lib64/libc.so.6
#17 0x00007f488cf336fc in clone3 () at /lib64/libc.so.6

It seems to crash in GStreamer code? Sounds like something caused by an update.

Please reopen this if it keeps happening
Comment 5 Wilbur Jaywright 2023-12-23 15:42:41 UTC
Yeah, it was. Not sure why a second reboot fixed it, but if it happens again, I’ll let you know.