Bug 969676

Summary: types.py:113: Warning: invalid (NULL) pointer instance return info.invoke(*args, **kwargs)
Product: [Fedora] Fedora Reporter: Michael Catanzaro <mcatanzaro>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 19CC: anaconda-maint-list, awilliam, dshea, g.kaviyarasu, jonathan, mcatanzaro, mkolman, robatino, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-05 00:43:33 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
anaconda.log
none
anaconda 19.30-1 exception report none

Description Michael Catanzaro 2013-06-01 14:50:52 EDT
Created attachment 755606 [details]
anaconda.log

Description of problem: I cannot install Fedora 19 Beta (using the default GNOME live CD). When I click "install now," no window opens for anaconda, but the anaconda process starts and begins to eat away my CPU.

When run as root in a terminal, there are tons of errors:

Starting installer, one moment...
anaconda 19.30-1 for anaconda bluesky (pre-release) started.
No protocol specified

** (anaconda:2720): WARNING **: Could not open X display
No protocol specified
No protocol specified

(anaconda:2720): Gdk-CRITICAL **: gdk_screen_get_root_window: assertion `GDK_IS_SCREEN (screen)' failed
No protocol specified
An unknown error has occured, look at the /tmp/anaconda-tb* file(s) for more details

<related warnings, massive snip>

(anaconda:2720): Gtk-CRITICAL **: _gtk_css_rgba_value_get_rgba: assertion `rgba->class == &GTK_CSS_VALUE_RGBA' failed
Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=fedora-bluesky&arch=x86_64 error was 
No repomd file
Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=updates-testing-fbluesky&arch=x86_64 error was 
No repomd file
Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=updates-released-fbluesky&arch=x86_64 error was 
No repomd file
^C

Probably more helpful errors are in anaconda.log (attached). Note that I ran (and killed) anaconda three times.

Version-Release number of selected component (if applicable): 19.30-1.fc19


How reproducible: Always


Steps to Reproduce:
1. Run anaconda :(

Actual results: No window opens and anaconda process uses large amount of CPU


Expected results: anaconda opens


Additional info:
Comment 1 Michael Catanzaro 2013-06-01 14:54:33 EDT
Created attachment 755607 [details]
anaconda 19.30-1 exception report
Comment 2 Michael Catanzaro 2013-06-04 23:06:40 EDT
Probably a blocker under release criteria "The installer must run when launched normally from the release-blocking images."
Comment 3 Adam Williamson 2013-06-04 23:21:48 EDT
You don't run 'anaconda' directly if you want to run it from a console on a live image, you run 'liveinst'.

I'm going to take a guess that this is likely https://bugzilla.redhat.com/show_bug.cgi?id=679486 . Can you check if that matches up?
Comment 4 Michael Catanzaro 2013-06-05 00:43:33 EDT
I'll look more at this tomorrow, but as the stack trace in my exception report is so similar to the one in Bug #928279, it's clearly the same bug. Thanks.

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