Bug 893218

Created attachment 675115 [details]
File: backtrace

Created attachment 675116 [details]
File: core_backtrace

Created attachment 675117 [details]
File: dso_list

Created attachment 675118 [details]
File: environ

Command-line:
$ qemu-kvm -m 2048 -hda f18-test-1.img -cdrom ~/xfr/fedora/F18/F18-Final/RC2/Fedora-18-x86_64-Live-Desktop.iso -usb -vga qxl -boot menu=on -usbdevice mouse

Created attachment 675119 [details]
anaconda.log

Created attachment 675120 [details]
program.log

Created attachment 675121 [details]
storage.log

ifcfg.log and packaging.log are empty.

*** Bug 896687 has been marked as a duplicate of this bug. ***

This seems to be reliable reproducer.

Start Live image:
$ qemu-kvm -m 2048 -cdrom ~/xfr/fedora/F18/F18-Final/Final/Fedora-18-x86_64-Live-Desktop.iso -vga qxl -usbdevice mouse

Click Live System User to login.
Click Try Fedora.
Click Close.
Click network icon in panel.
Click Wired to turn networking Off.
Click Activities in panel.
Click installer icon.

An ABRT notification appears.
Click Report.
There is no apparent response -- I believe this is because the exception is owned by root.

Click Activities.
Click Show Applications.
Click the ABRT icon.
Click Show all problems.

The Gtk.py ... RuntimeError exception is listed.

Testing is with an F17 host:
$ rpm -q qemu-kvm
qemu-kvm-1.0.1-2.fc17.x86_64

I've also encountered this issue a few times. I haven't tried to reproduce it consistently yet, but I've seen it happen two or three times already. What is notable for me is that it only occured so far when I had a network connection active instead of not having one like Steve.

Thanks Alex. Your comments in Bug 904014 helped me discover another reproducer for this one:

Start the Live image in a VM:
$ qemu-kvm -m 2048 -hda f18-test-2.img -cdrom ~/xfr/fedora/F18/F18-Final/Final/Fedora-18-x86_64-Live-Desktop.iso -vga qxl -boot menu=on -usbdevice mouse

Proceed to the desktop.
Start a terminal.

[liveuser@localhost ~]$ su
[root@localhost liveuser]# hostnamectl set-hostname f18-test-2
[root@localhost liveuser]# exit
exit
[liveuser@localhost ~]$ liveinst
No protocol specified
xhost:  unable to open display ":0"
Starting installer, one moment...
anaconda 18.37.11 for Fedora 18 started.
No protocol specified

** (anaconda:1940): WARNING **: Could not open X display
No protocol specified
Traceback (most recent call last):
  File "/sbin/anaconda", line 923, in <module>
    setupDisplay(anaconda, opts)
  File "/sbin/anaconda", line 585, in setupDisplay
    anaconda.initInterface()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/__init__.py", line 213, in initInterface
    from pyanaconda.ui.gui import GraphicalUserInterface
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/__init__.py", line 22, in <module>
    import meh.ui.gui
  File "/usr/lib/python2.7/site-packages/meh/ui/gui.py", line 23, in <module>
    from gi.repository import Gtk
  File "/usr/lib64/python2.7/site-packages/gi/importer.py", line 76, in load_module
    dynamic_module._load()
  File "/usr/lib64/python2.7/site-packages/gi/module.py", line 244, in _load
    overrides_modules = __import__('gi.overrides', fromlist=[self._namespace])
  File "/usr/lib64/python2.7/site-packages/gi/overrides/Gtk.py", line 1624, in <module>
    raise RuntimeError("Gtk couldn't be initialized")
RuntimeError: Gtk couldn't be initialized
[liveuser@localhost ~]$

seen with dd USB of Mate-live Cd :
 http://bitchx.ca/Image-FedoraMateCompiz.iso
:fails with this error if no network connection.
:Works fine if reboot with wired connection present.
:Liveinst (Install to Hard disk) Works in VirtualBox install as there is a wired connection

On a physical test machine here I was able to repeat this error several times in a row, where the installer on KDE live image would crash with the above GTK error.

I then turned off my machine, unplugged my network cable and it then worked several times in a row.

I then plugged my network cable back in without a power off, and it still continued to work.

Not particularly helpful but at least it's not confined to VMs, and in my case it was the opposite to above (fails with error with network plugged in).

Will try to gather more information.

Can someone please see if this works for them:

xhost +
liveinst

This might be a re-occurrence of an old F15 bug:
https://bugzilla.redhat.com/show_bug.cgi?id=679486

(In reply to comment #16)
> Can someone please see if this works for them:
> 
> xhost +
> liveinst

Chris,
yes, it works.

I thought one had to be # (su) for liveinst to work....It is that way in Soas spin- But this does not seem to apply in a live CD in Virtual Box with f19:
Testing with f19 TC5 live desktop x86_64 in Virtual Box
 2358 MB 16,00 GB HD
1-) network detached + Live System User/settings:Airplane mode on
 $su 
 #liveinst 
 localuser: root being added to access control list 
 Starting installer....
 "anaconda 19.16.1 for Fedora 19 ... started.
 Not asking for VNC beause we have don't have a network"
 Anaconda appears in 2nd window

2-)VirtualBox: [x]Enable Network Adapter: Bridged Adapter eth0
 $su 
 #liveinst 
 localuser: root being added to access control list 
 Starting installer....
 "anaconda 19.16.1 for Fedora 19 ... started.
 Anaconda appears in 2nd window

3-)VirtualBox: [x]Enable Network Adapter: Bridged Adapter eth0
 (try with-out root)
 $liveinst
 localuser: root being added to access control list 
 Starting installer....
 "anaconda 19.16.1 for Fedora 19 ... started.
 Anaconda appears in 2nd window

*** This bug has been marked as a duplicate of bug 679486 ***