Description of problem:
Trying pxe/kickstart text mode install of today's rawhide. Worked on one
laptop, on another I get:
File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 607, in
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The
anme org.freedesktop.Hal was not provided by any .service files
Main difference is that I'm trying to re-use the /boot, swap, and /export
partitions from an existing install.
Version-Release number of selected component (if applicable):
Hmm, removed a CD-ROM disc that was in the machine and it seems to get past that
If you can reproduce, does it look like hal is running when you get the traceback?
Very reproducible. hald has been running the whole time.
Gah, sorry - got this mixed up with another bug. I'll see if I can check - but
it crashes very quickly...
Created attachment 301844 [details]
Okay, with nokill I can still use VT2. hald is definitely running. Perhaps it
is taking too long to come up pinging the CDROM?
Is the cd being used for the kickstart as a source? Also, where is the dbus
call being made (ie, what's the rest of the traceback)
The cd just happened to be in the drive (though it is a Fedora CD). I'm doing a
PXE boot, http install. Rest of the traceback scrolls off the screen. Last
item in anaconda.log is:
09:58:11 INFO : Display mode = t
09:58:11 INFO : Method =
The only callers of it that I see in a quick grep are wrapped in try/except.
And shift-pgup should work to scrollback and see more of the traceback.
Ah, never knew about shift-pgup. cool.
/usr/bin/anaconda line 869 in probeHW
line 456 in xserver.probeHW
rhpxl/xserver.py line 84
rhpxl/videocard.py line 126
Hrmm -- definitely should be running at that point. Sticking on the blocker
list so that we can not lose track of this
Cool, I thought it was just me.... I saw this earlier with 220.127.116.11 also.
I also saw after the above:
/dbus/bus.py line 244 get_object
/dbus/proxies.py line 241 __init__
/dbus/bus.py line 183 activate_name_owner
/dbus/bus.py line 281 start_service_by_name
then /dbus/connection.py", line 607
hope it helps.
fixed with 18.104.22.168 for me.
And for me.. Looks like the new rhpxl package fixed it.