Bug 606779 - [abrt] crash in virt-manager-0.8.4-1.fc13: pango_layout_run_get_extents: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in virt-manager-0.8.4-1.fc13: pango_layout_run_get_extents: Proc...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: pango
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6569bb63b2a9169cc34f1bbed65...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-22 13:41 UTC by Jiri Pirko
Modified: 2015-05-05 01:20 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 18:44:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (45.10 KB, text/plain)
2010-06-22 13:41 UTC, Jiri Pirko
no flags Details

Description Jiri Pirko 2010-06-22 13:41:10 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: python /usr/share/virt-manager/virt-manager.py
comment: I was just creating a new kvm machine, selected iso method and added iso image located on nfs -> boom
component: virt-manager
crash_function: pango_layout_run_get_extents
executable: /usr/bin/python
global_uuid: 6569bb63b2a9169cc34f1bbed65c195935f01b7d
kernel: 2.6.33.5-124.fc13.x86_64
package: virt-manager-0.8.4-1.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 Jiri Pirko 2010-06-22 13:41:12 UTC
Created attachment 425921 [details]
File: backtrace

Comment 2 Cole Robinson 2011-03-23 21:38:08 UTC
I'm guessing this a pango issue? Not sure what we could be doing wrong here.

Comment 3 Behdad Esfahbod 2011-03-28 18:28:10 UTC
No idea how run can be null there.

Comment 4 Bug Zapper 2011-06-01 15:55:34 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 5 Bug Zapper 2011-06-27 18:44:20 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.