Bug 478615 - Crash on exiting k3b.
Crash on exiting k3b.
Status: CLOSED CANTFIX
Product: Fedora
Classification: Fedora
Component: k3b (Show other bugs)
10
i686 Linux
low Severity low
: ---
: ---
Assigned To: Roman Rakus
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-02 02:48 EST by tony
Modified: 2014-01-12 19:08 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-01-02 08:28:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Copy of the crash handler report. (3.91 KB, application/octet-stream)
2009-01-02 02:49 EST, tony
no flags Details

  None (edit)
Description tony 2009-01-02 02:48:08 EST
Description of problem:
Crash on shutting down k3b

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

How reproducible:
Always

Steps to Reproduce:
1. Shut down k3b
2. Observe kde crash handler notification
3.
  
Actual results:
Something doesn't shutdown cleanly.

Expected results:
No errors on shutdown.

Additional info:
Minor bug. Doesn't seem to effect anything else.

Copy of the crash report attached.
Comment 1 tony 2009-01-02 02:49:46 EST
Created attachment 328057 [details]
Copy of the crash handler report.

Copy of the crash handler report.
Comment 2 Rex Dieter 2009-01-02 08:28:20 EST
Do you have k3b-extras-freeworld installed?  If so, that's likely it.  See also:
https://bugzilla.rpmfusion.org/show_bug.cgi?id=213
(closing->cantfix, as that is not distributed by fedora).  If this is not the case, please re-open.

And without any -debuginfo pkgs installed, the supplied crash dump isn't all that useful.
Comment 3 tony 2009-01-02 17:57:50 EST
Yes, I've got the freeworld packages installed. That will be it.

Didn't know about the debuginfo packages. Will utilise them in the future.

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