Bug 803634 - KDE 4.7.4 crashes on logout (maybe even to times)
KDE 4.7.4 crashes on logout (maybe even to times)
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: kde-workspace (Show other bugs)
16
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Ngo Than
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-15 06:13 EDT by Vytas
Modified: 2012-03-15 18:36 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-03-15 16:21:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Vytas 2012-03-15 06:13:44 EDT
Description of problem:
KDE 4.7.4 crashes on logout (maybe even to times).
Crash reporter pops up asking to report this. I would report trough it, but it declares info useless and ask lots of downloads and KDE is completely down by then except crash reporter.
I this happens every time I logout.
It would be nice that crash reported would not try to report same thing every day.
It would be nice to get crash fixed. I can provide more info, but not ~~1 Gb debuginfo downloads.


Version-Release number of selected component (if applicable):
4.7.4

How reproducible:
100%

Steps to Reproduce:
1.logout from KDE
  
Actual results:
crash reporter

Expected results:
logout

Additional info:
Comment 1 Kevin Kofler 2012-03-15 16:21:34 EDT
Sorry, but without either a usable backtrace (which probably includes installing debugging information) or better steps to reproduce than "logout for KDE" (which works for us without crash), we probably cannot do anything about this.
Comment 2 Rex Dieter 2012-03-15 16:32:31 EDT
fwiw, the crash reporter should at least give a hint as to the program or component that is crashing.  that would be something to go on. 

But long term, Kevin's right, to go much further would require either someone able to reproduce the problem or in the least a backtrace to help identify what's going wrong.

Note You need to log in before you can comment on or make changes to this bug.