Bug 398513

Summary: Plasmashell crash with memory access error
Product: [Plasma] plasmashell Reporter: Vignesh Kumar <xxvignesh>
Component: generic-crashAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash Keywords: triaged
Priority: NOR    
Version First Reported In: 5.13.5   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Vignesh Kumar 2018-09-11 17:51:31 UTC
plasmashell crashes frequently (5+ times per day) when doing seemingly random tasks. Haven't been able to pinpoint it.

relevant part from journalctl:

Sep 11 16:13:37 vigneshk systemd-coredump[2139]: Process 1260 (plasmashell) of user 1000 dumped core.
                                                 
                                                 Stack trace of thread 1260:
#0  0x00007f7bf7b97d7f n/a (n/a)


relevant part from coredump -> gdb -> bt

[New LWP 2240]
[New LWP 2209]
Cannot access memory at address 0x7f949c9640e8
Cannot access memory at address 0x7f949c9640e0
Failed to read a valid object file image from memory.
Core was generated by `/usr/bin/plasmashell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f9499694d7f in ?? ()
Comment 1 Christoph Feck 2018-10-04 23:17:33 UTC
Please ask for help in a forum of your distribution how to recompile Qt and Plasma with debug information. Crash reports without debug information cannot be fixed by developers.
Comment 2 Andrew Crouthamel 2018-10-21 05:00:40 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-11-12 16:05:07 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!