Bug#1028208: plasma-discover: Program terminated with signal SIGSEGV

[Bernhard Übelacker <bernhardu@mailbox.org>]

> (gdb) bt
> #0  0x00007fbffc2a9ccc in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> #1  0x00007fbffc25aef2 in raise () from /lib/x86_64-linux-gnu/libc.so.6
> #2  0x00007fbffe79dbe1 in KCrash::defaultCrashHandler(int) () from /lib/x86_64-linux-gnu/libKF5Crash.so.5
> #3  <signal handler called>
> #4  0x00007fbffc2a9ccc in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> #5  0x00007fbffc25aef2 in raise () from /lib/x86_64-linux-gnu/libc.so.6
> #6  <signal handler called>
> #7  0x00007fbffc2a9ccc in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> #8  0x00007fbffc25aef2 in raise () from /lib/x86_64-linux-gnu/libc.so.6
> #9  0x00007fbffad3c3b0 in g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
> #10 0x00007fbffad4f1a5 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0


Hello Piotr,
this raise might indicate that libgobject wanted
to stop the process for some reason.
This reason it might have written to stdout/stderr.

Therefore probably you can still retrieve this logging.
From the "Sun 2023-01-08 13:36:08 GMT" I assume it happend at 14:36
your local time? Then following might possibly show related output.
If there is some could you provide the related parts?

journalctl --user --since="2023-01-08 14:34" --until="2023-01-08 14:38"

Unfortunately there might also be some programs writing to ~/.xsession-errors,
there the lines are not prefixed with the date and time ...
So it might be difficult to find them there.

Was this just a "one-time" crash, or do you get that regularly?

Kind regards,
Bernhard