Bug 566851 - [abrt] crash in fbreader-0.12.1-1.fc12
Summary: [abrt] crash in fbreader-0.12.1-1.fc12
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: fbreader
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Michel Lind
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5536553b927b2b1ce9c76c2cd4d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-19 23:48 UTC by nakieb
Modified: 2010-03-08 20:39 UTC (History)
2 users (show)

Fixed In Version: fbreader-0.12.2-1.fc12
Clone Of:
Environment:
Last Closed: 2010-03-01 17:58:11 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (31.30 KB, text/plain)
2010-02-19 23:48 UTC, nakieb 		no flags Details
a more complete backtrace (32.45 KB, text/plain)
2010-02-25 23:18 UTC, nakieb 		no flags Details
Show Obsolete (1) View All

Description nakieb 2010-02-19 23:48:16 UTC 
abrt 1.0.6 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: FBReader
component: fbreader
executable: /usr/bin/FBReader
kernel: 2.6.31.12-174.2.3.fc12.i686
package: fbreader-0.12.1-1.fc12
rating: 3
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)

comment
-----
Same steps can be used to reproduce  Bug 557968 -  [abrt] crash in fbreader-0.10.7-4.fc12  .
Updating fbreader from version 0.10.7-4 to 0.12.1-1did not solve the problem

How to reproduce
-----
1.press add to library button
2.Browse and select a compiled HTML file (.chm)
3.
Comment 1 nakieb 2010-02-19 23:48:26 UTC 
Created attachment 395198 [details]
File: backtrace
Comment 2 nakieb 2010-02-25 23:18:13 UTC 
Created attachment 396426 [details]
a more complete backtrace

ABRT 1.0.7 says the first backtrace is incomplete . To fix this, I have reproduced crash and I am attaching  the new backtreace .
Comment 3 nakieb 2010-03-01 17:58:11 UTC 
This bug 
exist on fbreader 0.10.1 , 0.12.1 with qt 4.5
doesn't exist on fbresder 0.12.2  with qt 4.6
solved in current release .
Note You need to log in before you can comment on or make changes to this bug.