Bug 803634

Summary:	KDE 4.7.4 crashes on logout (maybe even to times)
Product:	[Fedora] Fedora	Reporter:	Vytas <vytautas1987>
Component:	kde-workspace	Assignee:	Than Ngo <than>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	16	CC:	jreznik, kevin, ltinkl, rdieter, rnovacek, than
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-15 20:21:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vytas 2012-03-15 10:13:44 UTC

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 20:21:34 UTC

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 20:32:31 UTC

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.