Bug 596869 - [abrt] crash in glabels-2.2.7-1.fc13: gl_view_text_init: Process /usr/bin/glabels was killed by signal 8 (SIGFPE)
Summary: [abrt] crash in glabels-2.2.7-1.fc13: gl_view_text_init: Process /usr/bin/gla...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: glabels
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Peter Gordon
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3644989db431ae0acfb3725de8e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-27 16:54 UTC by Michael Cronenworth
Modified: 2010-05-28 21:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-28 18:46:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (24.20 KB, text/plain)
2010-05-27 16:54 UTC, Michael Cronenworth
no flags Details

Description Michael Cronenworth 2010-05-27 16:54:43 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: glabels
comment: Also invoking "glabels document.glabels" from a terminal causes an instant core dump.
component: glabels
crash_function: gl_view_text_init
executable: /usr/bin/glabels
global_uuid: 3644989db431ae0acfb3725de8e52e1f2ebcbee5
kernel: 2.6.33.4-95.fc13.x86_64
package: glabels-2.2.7-1.fc13
rating: 4
reason: Process /usr/bin/glabels was killed by signal 8 (SIGFPE)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Opened glabels
2. Browsed to a glabels document file.
3. Clicked Open and glabels crashed without showing my label document.

Comment 1 Michael Cronenworth 2010-05-27 16:54:45 UTC
Created attachment 417306 [details]
File: backtrace

Comment 2 Michael Cronenworth 2010-05-28 15:19:18 UTC
It appears glabels crashes even on a brand new label. As soon as I attempt to add a text block or a picture glabels crashes.

Downgrading to glabels-2.2.6-1.fc12.x86_64 allows me to bring up labels and print them successfully.

Comment 3 Jef Spaleta 2010-05-28 18:05:40 UTC
Does the build of 2.2.8 in F13 updates-testing fix this for you? Actually in should be in updates stable now.  



-jef

Comment 4 Michael Cronenworth 2010-05-28 18:46:03 UTC
(In reply to comment #3)
> Does the build of 2.2.8 in F13 updates-testing fix this for you? Actually in
> should be in updates stable now.  
> 


2.2.8 was not in my updates-testing mirror nor in my updates mirror.

I pulled it from koji and 2.2.8 does indeed work. Thanks. I will investigate why my mirror is not giving me 2.2.8. Sorry for the noise.

Comment 5 Jef Spaleta 2010-05-28 21:27:00 UTC
no problem. The fix was made on release day...so the report isn't untimely.  I didn't mark this one as a dupe initially because it was a different crash trigger and i wanted to be sure.



-jef


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