Bug 291587 - kde crash
Summary: kde crash
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2012-01-15 15:29 UTC by bkorb
Modified: 2018-10-27 02:41 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bkorb 2012-01-15 15:29:12 UTC
Version:           unspecified (using KDE 4.7.2) 
OS:                Linux

This time, I wasn't logging out, unlike the many, many, many other times.
This time, I was trying to restore the control panel that had mysteriously
disappeared.  I logged out and back in, but still no control panel, so
I decided to try to create a new one.  KDE crashed.

Reproducible: Didn't try

Steps to Reproduce:
1. boot into KDE and find the control panel missing
2. try to create the panel again from the desktop "cashew".

Actual Results:  
crash

Expected Results:  
success

KDE has been crashing regularly for a *YEAR* now.  This is very old.
Please do one of two things:

1. Fix it
2. Declare KDE to be unsupported

By the way, this is a manual report instead of automated one because
after spending 15 minutes loading debug packages, your crash handling
program kept saying more packages were needed, but did not install
more packages from the repos.  That was also quite a waste of time.
Comment 1 Christoph Feck 2012-01-15 15:57:55 UTC
Update to 4.7.4
Comment 2 bkorb 2012-01-15 16:55:20 UTC
No backtrace can be provided unless your gather-the-backtrace tool works correctly.

Please do not ask me to update to 4.7.4.  Ask the folks that maintain the rpm repos to do so.  (viz. the one for openSuSE, but Red Hat and Debian, too.)

By the way, does the "Update to 4.7.4" comment mean that the continual crash-on-shutdown bug has been fixed?  Or are you just asking me to use bleeding edge?
Comment 3 Andrew Crouthamel 2018-09-22 01:45:53 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:41:08 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!