Bug 434664

Summary:	kdeinit5 crash
Product:	[Plasma] plasmashell	Reporter:	medin <med.medin.2014>
Component:	generic-crash	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	justin.zobel, nate
Priority:	NOR
Version:	5.21.3
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description medin 2021-03-20 13:23:42 UTC

After updating to 5.21.3, kdeinit5 started to crash at random times and often after login.

Operating System: Manjaro Linux
KDE Plasma Version: 5.21.3
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.4.105-1-MANJARO
OS Type: 64-bit
Graphics Platform: X11


Backtrace :

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `thumbnail.so [kdeinit5] thumbna'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f15281e1f30 in __memcpy_ssse3 () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7f1524c4ecc0 (LWP 48497))]
(gdb) bt
#0  0x00007f15281e1f30 in __memcpy_ssse3 () from /usr/lib/libc.so.6
#1  0x00007f15290db492 in ?? () from /usr/lib/qt/plugins/kf5/kio/thumbnail.so
#2  0x00007f15248866ef in KIO::SlaveBase::dispatch(int, QByteArray const&) () from /usr/lib/libKF5KIOCore.so.5
#3  0x00007f1524887016 in KIO::SlaveBase::dispatchLoop() () from /usr/lib/libKF5KIOCore.so.5
#4  0x00007f15290d9026 in kdemain () from /usr/lib/qt/plugins/kf5/kio/thumbnail.so
#5  0x000055dc40bd45bd in ?? ()
#6  0x000055dc40bd5a59 in ?? ()
#7  0x000055dc40bd6237 in ?? ()
#8  0x000055dc40bd1b54 in ?? ()
#9  0x00007f15280cab25 in __libc_start_main () from /usr/lib/libc.so.6
#10 0x000055dc40bd26be in ?? ()

Comment 1 Justin Zobel 2021-03-20 22:59:26 UTC

Thank you for the crash report. In order to diagnose this issue as quickly as possible can you please ensure you have all debug symbols installed.

Instructions on how to do this for several distributions are provided at https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Install_debugging_packages

Once you have all the debug symbols installed (see lines where it has "in ?? () from" for hints on which packages are needed) please reproduce the crash and upload the new backtrace, thank you.

I've set this bug to NEEDSINFO. Once you have added the required information please change the bug back to REPORTED so we know it's ready for investigation or RESOLVED/WORKSFORME if the issue is now resolved.

Comment 2 medin 2021-03-20 23:09:58 UTC

(In reply to Justin Zobel from comment #1)
> Thank you for the crash report. In order to diagnose this issue as quickly
> as possible can you please ensure you have all debug symbols installed.
> 
> Instructions on how to do this for several distributions are provided at
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Install_debugging_packages
> 
> Once you have all the debug symbols installed (see lines where it has "in ??
> () from" for hints on which packages are needed) please reproduce the crash
> and upload the new backtrace, thank you.
> 
> I've set this bug to NEEDSINFO. Once you have added the required information
> please change the bug back to REPORTED so we know it's ready for
> investigation or RESOLVED/WORKSFORME if the issue is now resolved.


I'm using Manjaro so there is no way to install those debugging packages. That backtrace was extracted using coredumpctl after running bt. This crash occurs for many times, since before yesterday upgrade to now I have almost 43 crash of kdeinit5.

Comment 3 Justin Zobel 2021-03-20 23:15:10 UTC

You can install debug packages, you just have to compile them first. Sadly Arch and Manjaro do not supply them like every other distro. It does make debugging on those distros far more challenging but it is possible.

Comment 4 Nate Graham 2021-03-20 23:57:58 UTC

Actually I can tell from just what's available that it's Bug 430862.

For future reference, I recommend using a distro that offers easy installation of debug symbols. Without them, many crash reports are useless and un-actionable, which wastes everyone's time--yours included.

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