Bug 649670 - [abrt] glabels-2.2.8-2.fc13: Process /usr/bin/glabels was killed by signal 11 (SIGSEGV)
Summary: [abrt] glabels-2.2.8-2.fc13: Process /usr/bin/glabels was killed by signal 11...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: glabels
Version: 13
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Peter Gordon
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:132e47e746f7f0787fa9a656583...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-04 08:54 UTC by Patrick C. F. Ernzer
Modified: 2011-06-28 10:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-28 10:52:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (42.41 KB, text/plain)
2010-11-04 08:54 UTC, Patrick C. F. Ernzer
no flags Details

Description Patrick C. F. Ernzer 2010-11-04 08:54:37 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: glabels
component: glabels
crash_function: IA__g_type_check_instance_cast
executable: /usr/bin/glabels
kernel: 2.6.34.7-61.fc13.x86_64
package: glabels-2.2.8-2.fc13
rating: 4
reason: Process /usr/bin/glabels was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1288860476
uid: 500

comment
-----
How reproducible:
rarely (around 10% of the time)

How to reproduce
-----
0. have at least one label open before starting at step 1 (so that glabels does not quit in step 4)
1. open a label from the recent files menu
2. make some changes
3. save
4. close the newly modified label (with window decoration close box)
5. select recent items in the other label window
6. select the just saved label

Actual results:
glabels crashes

Expected results:
no crash

Comment 1 Patrick C. F. Ernzer 2010-11-04 08:54:40 UTC
Created attachment 457735 [details]
File: backtrace

Comment 2 Fedora Admin XMLRPC Client 2011-03-16 11:18:26 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Bug Zapper 2011-05-30 14:14:15 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

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

Comment 5 Bug Zapper 2011-06-28 10:52:34 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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