*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
On a fresh install of feisty final, using no auto-login but instead
waiting until all init scripts are finished and then logging manually
in, I still get the error. I tried
# sudo dpkg-reconfigure hal
which gave me:
UUID file '/var/lib/dbus/machine-id' contains invalid hex data
[EMAIL PROTECTED]:/var/lib/dbus# cat machine-id
Name: adduser/homedir-permission
Right, this doesn't look like a hex value ;) I don't know where this
string comes from. I deleted machine-id and did
[EMAIL PROTECTED]:/var/lib/dbus# dbus-uuidgen --ensure
[EMAIL PROTECTED]:/var/lib/dbus# cat machine-id
8084dbe5dda580d55fa79e0046418245
This looks better.
[EMAIL PROTECTED]:/var/run/dbus# /etc/init.d/dbus restart
works now.
I'll try a reboot now to see if it still works or if my machine-id gets
overwritten with invalid data again.
--
failed to initialize HAL : gdm init script priority should be at least equal to
dbus one
https://bugs.launchpad.net/bugs/81670
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gdm in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
