Bug 633962 - [abrt] crash in k3b-1:1.91.0-2.fc13: QCommonStyle::styleHint: Process /usr/bin/k3b was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in k3b-1:1.91.0-2.fc13: QCommonStyle::styleHint: Process /usr/bi...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: k3b
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Radek Novacek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6337d251d066749569fbdb88f60...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-14 19:15 UTC by Samuel
Modified: 2016-12-01 00:29 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-02-14 08:08:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (217.13 KB, text/plain)
2010-09-14 19:15 UTC, Samuel
no flags Details

Description Samuel 2010-09-14 19:15:32 UTC
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/k3b
component: k3b
crash_function: QCommonStyle::styleHint
executable: /usr/bin/k3b
global_uuid: 6337d251d066749569fbdb88f605c3a92ad412f1
kernel: 2.6.31.6-166_1.cubbi_tuxonice.fc12.i686
package: k3b-1:1.91.0-2.fc13
rating: 4
reason: Process /usr/bin/k3b was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Go to the settings in k3b
2.let it crash
3.

Comment 1 Samuel 2010-09-14 19:15:37 UTC
Created an attachment (id=447305)
File: backtrace

Comment 2 Rex Dieter 2010-09-14 19:19:13 UTC
I'd recommend upgrading to something more recent, and see if the problem is reproducible, using kde-2.0.1 for example,
https://admin.fedoraproject.org/updates/k3b-2.0.1-1.fc13

Comment 3 Fedora Admin XMLRPC Client 2011-01-26 14:59:34 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Fedora Admin XMLRPC Client 2011-02-08 15:27:43 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Radek Novacek 2011-02-14 08:08:51 UTC
No reply from reported for almost a half year, so I'm closing this bug.


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