Bug 905909 - [abrt] anaconda-18.37.11-1.fc18: Gtk.py:1624:<module>:RuntimeError: Gtk couldn't be initialized
Summary: [abrt] anaconda-18.37.11-1.fc18: Gtk.py:1624:<module>:RuntimeError: Gtk could...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk3
Version: 18
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e041dd956f932e40e4f1d6b9c57...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-30 13:01 UTC by Anton Baklanov
Modified: 2014-02-05 18:41 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 18:41:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (8.25 KB, text/plain)
2013-01-30 13:01 UTC, Anton Baklanov
no flags Details
File: core_backtrace (811 bytes, text/plain)
2013-01-30 13:01 UTC, Anton Baklanov
no flags Details
File: dso_list (63 bytes, text/plain)
2013-01-30 13:01 UTC, Anton Baklanov
no flags Details
File: environ (854 bytes, text/plain)
2013-01-30 13:01 UTC, Anton Baklanov
no flags Details

Description Anton Baklanov 2013-01-30 13:01:06 UTC
Description of problem:
steps to reproduce:
1) run fedora 18 live kde in virtualbox
2) click "install to hard drive"
3) get this error instead of anaconda

Version-Release number of selected component:
anaconda-18.37.11-1.fc18

Additional info:
cmdline:        /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8
executable:     /sbin/anaconda
kernel:         3.6.10-4.fc18.i686
uid:            0

Comment 1 Anton Baklanov 2013-01-30 13:01:10 UTC
Created attachment 690370 [details]
File: backtrace

Comment 2 Anton Baklanov 2013-01-30 13:01:16 UTC
Created attachment 690371 [details]
File: core_backtrace

Comment 3 Anton Baklanov 2013-01-30 13:01:18 UTC
Created attachment 690372 [details]
File: dso_list

Comment 4 Anton Baklanov 2013-01-30 13:01:31 UTC
Created attachment 690373 [details]
File: environ

Comment 5 Anton Baklanov 2013-01-30 13:13:52 UTC
error was gone away after rebooting vm.

Comment 6 Chris Lumens 2013-01-30 14:48:53 UTC
I think I've seen one or two other reports with this, but given the rather transitory nature of them, I'm not hopeful we'll be able to get to the bottom of this.

Comment 7 Matthias Clasen 2013-01-30 17:34:43 UTC
Nothing for me to go on here, really.
Unless simple tk applications like gtk3-demo fail to start and you can get a stacktrace, I'd say this has be debugged on the anaconda side.

Comment 8 Gabriel M. Elder 2013-04-12 05:28:24 UTC
I've described a likely cause and temporary workaround in bug #913810.

Comment 9 Fedora End Of Life 2013-12-21 10:59:47 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Comment 10 Fedora End Of Life 2014-02-05 18:41:56 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.