Red Hat Bugzilla – Bug 866434
DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.0 was not provided by any .service files
Last modified: 2012-10-16 07:49:38 EDT
Description of problem:
I just started F18 Beta TC4 DVD i386 installation. The language selection was not even shown, the black screen went straight into an exception dialog.
Version-Release number of selected component:
libreport version: 2.0.14
cmdline: /usr/bin/python /sbin/anaconda
:The following was filed automatically by anaconda:
:anaconda 18.16 exception report
:Traceback (most recent call first):
: File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking
: message, timeout)
: File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 145, in __call__
: File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 70, in __call__
: return self._proxy_method(*args, **keywords)
: File "/usr/lib/python2.7/site-packages/pyanaconda/isys/__init__.py", line 369, in isWirelessDevice
: devlist = nm.get_dbus_method("GetDevices")()
: File "/usr/lib/python2.7/site-packages/pyanaconda/network.py", line 424, in createMissingDefaultIfcfgs
: if not isys.isWirelessDevice(iface):
: File "/usr/lib/python2.7/site-packages/pyanaconda/network.py", line 892, in networkInitialize
: File "/sbin/anaconda", line 962, in <module>
:DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.0 was not provided by any .service files
Created attachment 627304 [details]
Created attachment 627305 [details]
Created attachment 627306 [details]
Created attachment 627307 [details]
Created attachment 627308 [details]
Created attachment 627309 [details]
Created attachment 627310 [details]
Created attachment 627311 [details]
Created attachment 627312 [details]
Created attachment 627313 [details]
Created attachment 627314 [details]
Created attachment 627315 [details]
Created attachment 627316 [details]
*** Bug 866438 has been marked as a duplicate of this bug. ***
This is a race condition, in 5 boots I managed to see this twice. All in VM.
Proposing as Beta blocker:
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 a USB stick with any of the officially supported methods
There is a new NM in TC4, might be NM bug 865009. Getting jklimes's help.
11:12:04,476 NOTICE dbus: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
11:12:04,488 INFO systemd: Started Network Manager Wait Online.
11:12:04,489 INFO systemd: Starting Network.
11:12:04,489 INFO systemd: Reached target Network.
11:12:04,489 INFO systemd: Startup finished in 3s 191ms 461us (kernel) + 5s 156ms 38us (initrd) + 6s 678ms 239us (userspace) = 15s 25ms 738us.
11:12:04,503 INFO dbus-daemon: dbus: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
11:12:04,503 NOTICE dbus: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
11:12:04,667 INFO dbus-daemon: /etc/NetworkManager/dispatcher.d/04-iscsi: line 14: /sbin/chkconfig: No such file or directory
11:12:06,708 WARNING kernel:[ 17.246672] show_signal_msg: 3 callbacks suppressed
11:12:06,708 INFO kernel:[ 17.246677] NetworkManager: segfault at ffffffff ip b70d0ce0 sp bfa22a40 error 4 in libglib-2.0.so.0.3400.0[b706d000+129000]
11:12:06,716 NOTICE systemd: NetworkManager.service: main process exited, code=killed, status=11
11:12:06,716 NOTICE systemd: Unit NetworkManager.service entered failed state.
*** Bug 866454 has been marked as a duplicate of this bug. ***
Created attachment 627490 [details]
log messages from i686 desktop from bug 865009
*** Bug 866449 has been marked as a duplicate of this bug. ***
Jirka, do you think we are hitting bug 865009?
Can we get NetworkManager-0.9.7.0-6.git20121004.fc18 with fix for it in next compose/TC?
Discussed at 2012-10-15 QA meeting acting as a blocker review meeting: http://meetbot.fedoraproject.org/fedora-meeting/2012-10-15/fedora-qa.2012-10-15-15.00.log.txt . Agreed it'd be good to see if other configurations hit this - so far all results from kparal (though we should check recently-reported bugs for any other apparent dupes). By Wednesday (next official blocker meeting) we should have a better idea whether anyone else hits this and will be able to make a determination.
I'm not sure if this crash is the same as in bug 865009, because we don't have a NM backtrace here. Hopefully it's the same.
Anyway, bug 865009 is fixed by NetworkManager-0.9.7.0-6.git20121004.fc18, see
*** Bug 866876 has been marked as a duplicate of this bug. ***
In bug 866876 I reproduced the issue on a bare metal machine. It does not happen when booting from PXE, but it happened when booting DVD over USB (dd).
Radek Vykydal confirmed he also saw this error. But it is highly erratic, on some computers we can't trigger it, on some we can.
Ok, I managed to reproduce the crash on Live Fedora-18-Beta-TC4 CD. It took some time as NM only crashed sometimes (once in 20 tries while activating a network).
Nonetheless, fortunately it appeared the issue is the same as in fixed bug 865009, so duping.
*** This bug has been marked as a duplicate of bug 865009 ***
Jirka, thanks a lot!