Bug 372266 - plasmashell crash (on resume from sleep)
Summary: plasmashell crash (on resume from sleep)
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.8.3
Platform: PCLinuxOS Linux
: NOR crash
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-11-09 22:29 UTC by Dean Schaf
Modified: 2018-10-27 02:06 UTC (History)
3 users (show)

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


Attachments
Text file with allegedly relevant info about the crash (189 bytes, text/plain)
2016-11-09 22:29 UTC, Dean Schaf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dean Schaf 2016-11-09 22:29:44 UTC
Created attachment 102153 [details]
Text file with allegedly relevant info about the crash

Application: plasmashell (5.8.3)

Qt Version: 5.6.2
Frameworks Version: 5.27.0
Operating System: Linux 4.8.6-pclos1 x86_64
Distribution: "PCLinuxOS"

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

The crash can be reproduced every time.

-- Backtrace:
A useful backtrace could not be generated

BUT HERE'S WHAT WAS HAPPENING WHEN THE CRASH OCCURRED:
I had put the computer on standby (sleep).  When I came back to use it
and woke it up, I was greeted with the notification that the plasmashell
had crashed.  And, I was given the chance to report the bug.

Tragically, the bug-report creation system is an epic failure, so I
put this silly blurb together just for Esses & Gees.

Report to https://bugs.kde.org/

Application: Plasma (plasmashell), signal: Segmentation fault
[Current thread is 1 (process 3452)]

Thread 1 (process 3452):
#0  0x00007fac7aa7467f in ?? ()
#1  0x0000000000000000 in ?? ()

About The System

SOFTWARE
KDE Framworks Version: 5.27.0
Qt Version: 5.6.2
Kernel Version: 4.8.6-pclos1
OS Type: 64-bit

HARDWARE
CPU: AMD Athlon(tm) X4 860K Quad-Core Processor
RAM: 16 GBs (2 x 8 GBs)
DISKS:
* sda Seagate ST3750528S   HDD
  ⱺ sda1 ..... Linux Swap
  ⱺ sda2 ..... ext4

* sdb Seagate ST3320620AS  HDD
  ⱺ sdb1 ..... ext4

* sdc SanDisk SDSSDA120G   SSD
  ⱺ sdc1 ..... ext4   /
  ⱺ sdc2 ..... ext4   /home

GRAPHICAL INFORMATION
Server Information
Name of the Display:		:0
Vendor String:			The X.Org Foundation
Vendor Release Number:		11,804,000
Version Number:			11.0

Display Adapter: nVidia GeForce GT 610 GC LP 2GB DDR3 64BIT

Motherboard: MSI A58M-E33
Comment 1 Christoph Feck 2016-11-11 17:52:54 UTC
Unfortunately, the backtrace lacks any indication about the cause for the crash. If this is reproducible, would it be possible to get a better backtrace with installed debugsymbols and/or with the gdb or valgrind tools?

For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 2 Marco Martin 2016-11-17 12:16:51 UTC
needs a more complete backtrace to be useful
Comment 3 Andrew Crouthamel 2018-09-26 22:11:41 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 set the bug status 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 4 Andrew Crouthamel 2018-10-27 02:06:18 UTC
Dear Bug Submitter,

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!