Bug 351083

Summary:	KWheezy KDE crashes on most recent update
Product:	[I don't know] kde	Reporter:	Herman Wolff <drwolff007>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED WORKSFORME
Severity:	major	CC:	cfeck
Priority:	NOR	Keywords:	triaged
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Herman Wolff 2015-08-08 12:32:23 UTC

Recent KWheezy Update Crashes
Is anyone using KWheezy(Debian GNU/Linux 7.8)that could help me? I did a routine update today(8/07/15) that required a reboot. I have done this several times over the last year without problems. On reboot I get the pop up window: Plasma Desktop Shell-The KDE Crash Handler with the message: Plasma Desktop Shell closed unexpectedly. Details: Executable: plasma-desktop PID: 4749 Signal: Segmentation fault (11).

I was unable to use the automatic popup debugger since it is not installed. I tried to get to KDE debug site by clicking a link in the popup window and my Firefox browser opened to the site. The browser seemed to work normally but when it was closed I get the blank screen with the Debian logo in the right lower corner of the screen. Conky app. is working normally and the KDE desktop is absent.

I have done all KWheezy updates over time and this is the first time I have had a problem or totally lost the KDE interface. I am not knowlegable enough to know how to proceed. Can anyone help?

Hermie

Reproducible: Always

Steps to Reproduce:
1.On boot up I get a blank screen without KDE interface
2.
3.

Actual Results:  
No KDE interface due to "bug"

Expected Results:  
Boot up with functioning KDE interface

Comment 1 Christoph Feck 2015-08-13 00:38:49 UTC

Sorry, this is not a support forum, but a bug tracker. I suggest to use a forum of your distribution to ask for help. If the experts there identify a bug in KDE software, they can state the details of the bug.

Since you mention a crash, KDE developers need the backtrace of the crash. For more information, please see https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Comment 2 Andrew Crouthamel 2018-09-25 21:52:54 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 3 Andrew Crouthamel 2018-10-27 03:49:05 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!