Bug 591563

Summary: [abrt] crash in glade3-3.6.7-2.fc12: Process /usr/bin/glade-3 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Cole Robinson <crobinso>
Component: glade3Assignee: Adam Miller <maxamillion>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: hiemanshu, huzaifas, maxamillion, rpandit
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:c32db981040e61ac138534dbad12a8305513d6cf
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 14:46:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Cole Robinson 2010-05-12 14:53:18 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: glade-3 src/vmm-details.glade
comment: For some reason, a recently created ImageMenuItem didn't have an Image widget embedded after reopening the project. All the image UI fields were blank. I clicked the stock icon drop down and the app crashed. Can probably be reproduce by manually editting the glade XML and removing the <child internal-child="image"> block from an ImageMenuItem.
component: glade3
executable: /usr/bin/glade-3
global_uuid: c32db981040e61ac138534dbad12a8305513d6cf
kernel: 2.6.32.11-102.fc12.x86_64
package: glade3-3.6.7-2.fc12
rating: 4
reason: Process /usr/bin/glade-3 was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Cole Robinson 2010-05-12 14:53:23 UTC 
Created attachment 413451 [details]
File: backtrace
Comment 2 Bug Zapper 2010-11-03 15:00:40 UTC 
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 3 Bug Zapper 2010-12-03 14:46:35 UTC 
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.