Aktiwers,
Quick way to see what runlevels have dbus set up:
# locate S??dbus
I ran into this HAL bug not long ago, and found that re-configuring HAL
got rid of it. Short story: make sure /var/run/dbus exists, and is owned
by messagebus:messagebus. You can make that directory and chown it over
*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
Dear Martin,
Thanks for your prompt reply.
Elbereth log No, I get the symbolic links correctly set at S12dbus
both before and after the upgrade. That's in /etc/rc3.d, rc4.d, rc5.d.
Running processes
*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
Short story: I was not able to reproduce the bug.
Long story: I did a clean install from Feisty Desktop beta CD onto a spare
partition, and did not see the HAL bug. Same as yesterday. I backed that
*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
Dear Martin,
I wonder if this bug is really fixed in Feisty. I got it after:
1.A clean install from the Feisty beta CD (no bug then)
2.Updates after that installation (got HAL bug)
John R
*** This bug is a duplicate of bug 25931 ***
https://bugs.launchpad.net/bugs/25931
I got the same error with Feisty beta, after a clean install on its own
disk and an update (350 packages). After the clean install, no error,
and Feisty could see my usb camera. After the upgrade, the failed to
