Bug 848682

Dracut-initqueue error for me in X86_64 netinstall.iso, almost similar error as in TC1.

It seems that dbus-daemon failed to start:
# systemctl status dbus.service -o cat
dbus.service - D-Bus System Message Bus
	  Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
	  Active: active (running) since Thu, 16 Aug 2012 08:42:08 +0000; 10min ago
	Main PID: 480 (dbus-daemon)
	  CGroup: name=systemd:/system/dbus.service
		  ├ 480 /bin/dbus-daemon --system --address=systemd: --nof...
		  └ 510 /usr/sbin/modem-manager

modem-manager[510]: <info>  Loaded plugin 'Generic'
modem-manager[510]: <info>  Successfully loaded 20 plugins
[system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
dbus[480]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
dbus[480]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
[system] Successfully activated service 'org.freedesktop.nm_dispatcher'
grep: error while loading shared libraries: libpcre.so.1: cannot open shared object file: No such file or directory
grep: error while loading shared libraries: libpcre.so.1: cannot open shared object file: No such file or directory
Failed to issue method call: Unit chronyd.service is not loaded.
grep: error while loading shared libraries: libpcre.so.1: cannot open shared object file: No such file or directory

Vadim: This is a different bug, please file a separate one, thanks.

I found out that supplying 'console=ttyS0 graphical' allows me to intercept console output while forcing graphical mode instead of textual one.

The text displayed is:
> Starting installer, one moment...
> anaconda 18.5 for Fedora 18-Alpha-TC2 (pre-release) started.
> 08:58:38 X startup failed, falling back to text mode

So clearly this is a problem of X starting up. Unfortunately the screen stays black even if you try to switch TTYs, so a 'rescue text mode' doesn't help at all.

Attaching logs.

Created attachment 604835 [details]
anaconda.log

Created attachment 604836 [details]
program.log

Created attachment 604837 [details]
storage.log

Created attachment 604838 [details]
syslog

Created attachment 604839 [details]
X.log

Hmm, maybe comment #2 is related. It seems some important libraries are missing. Even grep can't be used:

# grep
grep: er: No such file or directorybraries: libpcre.so.1: cannot open shared object file

That can be also the reason why Xorg fails to start.

The previous was run in a VM with "console=ttyS0 graphical".

Now I have run it on a bare metal without any extra options, and it behaves a bit differently. Attaching logs.

Created attachment 604853 [details]
bare metal - anaconda.log

Created attachment 604854 [details]
bare metal - program.log

Created attachment 604855 [details]
bare metal - syslog

Created attachment 604856 [details]
bare metal - X.log

Same in a VirtualBox 4.1.18 VM, both DVD and netinst, both i386 and x86_64.

Created attachment 604862 [details]
bare metal - main VT

Same here with i386 on an older iMac with an nVidia G73 (GeForce 7300 GT)

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

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

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

(In reply to comment #10)
> Hmm, maybe comment #2 is related. It seems some important libraries are
> missing. Even grep can't be used:
> 
> # grep
> grep: er: No such file or directorybraries: libpcre.so.1: cannot open shared
> object file
> 
> That can be also the reason why Xorg fails to start.
Martin, any place in lorax where this library may be removed? Bare metal case fails on missing libgtk3.

Created attachment 604967 [details]
anaconda log

Created attachment 604968 [details]
X log

I think it's related to the current bug 845745
X doesn't start with the latest kernels on certain ATI GPUs

No, I don't think so. It appears that X startup fails on all systems, including virtual machines.

bcl believes https://admin.fedoraproject.org/updates/lorax-18.14-1.fc18 should fix this, or at any rate improve it.

We were removing some libs that Gtk is now depending on. lorax-18.14-1 will fix this.

lorax-18.14-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/lorax-18.14-1.fc18

Package lorax-18.14-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lorax-18.14-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-11979/lorax-18.14-1.fc18
then log in and leave karma (feedback).

Discussed at 2012-08-16 blocker review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-08-16/f18-alpha-blocker-review-3.2012-08-16-16.00.html . Accepted as a blocker per criterion "The installer must boot (if appropriate) and run on all primary architectures, with all system firmware types that are common on those architectures, from default live image, DVD, and boot.iso install media when written to an optical disc and when written to a USB stick with at least one of the officially supported methods".

TC3 fixes this. *important* note if you're testing in a VM: you may still run into problems at X start, but it is no longer this bug, there are two other known bugs in the most common KVM video adapter/driver combos. See https://bugzilla.redhat.com/show_bug.cgi?id=848930 (cirrus bug) and https://bugzilla.redhat.com/show_bug.cgi?id=844463 (qxl bug).

lorax-18.14-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.