[Bug 31517] Re: hal-device-manager does not load
Hugh: Can you please copy&paste the output of id hal id haldaemon here? Also, can you please attach /etc/fstab? ** Summary changed: - hal-device-manager does not load + dbus does not start -- dbus does not start https://launchpad.net/bugs/31517 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31517] Re: hal-device-manager does not load
I've had the same problem on 2 machines after upgrading from breezy. A fresh install on an AMD Athlon 1700 went ok and seems to be running well with 2.6.16-26-k7, but the fresh install of Dapper on the laptop - Intel Sonoma, running a 386 kernel still gets the dbus or HAL error messages, and won't recognise USB drives. If I resart dbus, avahi-daemon, hald and dbus shut down ok, then dbus, hald restart, but avahi-daemon takes ages in its attempt to restart, and eventually times out, and I've lost my desktop, both Gnome, AND xfce4. I can't find a user hal or haldaemon in the usual newbie user utility. Where do I look for such users on a console? -- hal-device-manager does not load https://launchpad.net/bugs/31517 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31517] Re: hal-device-manager does not load
I've finally found what was kicking this off, though I think it's more a symptom than a cause. I had SMB shares auto-mounting. Removing them from fstab fixed the problem, lshal now gives output and update-notifier now works. >From the variety of fixes that have worked for people it looks to me like something in the start-scripts for hal is being brittle... -- hal-device-manager does not load https://launchpad.net/bugs/31517 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31517] Re: hal-device-manager does not load
>Could I suggest that we raise the priority of this problem to High. Indeed, if anyone botherd to read my error log, they would see that the restart of dbus produses a kernel oops, and that is more a critical error then medium. [17602012.392000] Unable to handle kernel paging request at virtual address f800738f [17602012.392000] printing eip: [17602012.392000] c01bc870 [17602012.392000] *pde = [17602012.392000] Oops: [#14] I get this from two different mainboards, both amd64 but one with nforce3 and the other nforce4. I have testet on 4 other 32bit computers and none of them have this problem. -- hal-device-manager does not load https://launchpad.net/bugs/31517 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31517] Re: hal-device-manager does not load
I deeply, deeply regret to say that I was completely unable to find any workaround for this problem, other than to install open suse 10.1, which worked with the hardware flawlessly. Could I suggest that we raise the priority of this problem to High, as it completely precludes one from running Ubuntu with Gnomeh. Note that I have since installed 2 new systems with open suse, because I can't afford to play around with unstable systems that unexpectedly announce that they refuse to run Gnome. -- hal-device-manager does not load https://launchpad.net/bugs/31517 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31517] Re: hal-device-manager does not load
I should add that I am using the most current version of the kernel - 2.6.15-26-386 -- hal-device-manager does not load https://launchpad.net/bugs/31517 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31517] Re: hal-device-manager does not load
I too get the "error failed to initialize HAL" when starting up Gnome. When I change to KDE at startup, is "seems" to start normally, but if I try to use Konqueror to browse files, - i.e. by clicking on a folder - Konqueror hangs. Also, if I recall corrrectly, when I clicked on the KDE main menu, system complained that "system processes terminated prematurely" or something to that effect... -- hal-device-manager does not load https://launchpad.net/bugs/31517 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31517] Re: hal-device-manager does not load
hm. got something from dbus when I did a sudo /etc/init.d/dbus restart -- hal-device-manager does not load https://launchpad.net/bugs/31517 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31517] Re: hal-device-manager does not load
Same goes for me. I have a Asus A8N-E motherboard and run the 32 bit Kubuntu. Installed Dapper from scratch. -- hal-device-manager does not load https://launchpad.net/bugs/31517 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31517] Re: hal-device-manager does not load
Wrong status :/ Incidentally the user fix (delete 'hal' user and re-install didn't work for me) ** Changed in: dbus (Ubuntu) Status: Rejected => Confirmed -- hal-device-manager does not load https://launchpad.net/bugs/31517 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31517] Re: hal-device-manager does not load
I've re-opened this bug as people are still having the same symptoms. I'm presuming I'm *allowed* to re-open the bug as launchpad is letting me.. Sorry if I've misunderstood. ** Changed in: dbus (Ubuntu) Status: Fix Released => Rejected -- hal-device-manager does not load https://launchpad.net/bugs/31517 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31517] Re: hal-device-manager does not load
It seems that people shouldn't have to be manually creating and deleting user accounts to get HAL working. I also have this problem and I'm happy enough to fix it manually, but really the symptoms here should be fixed as well as the original problem. It takes about 10 minutes for my Dapper box to boot and once it does I get no auto-mounting of USB and whatnot. Some debug: [EMAIL PROTECTED]:~$ lshal error: libhal_ctx_init: (null): (null) Could not initialise connection to hald. Normally this mean the HAL daemon (hald) is not running or not ready. [EMAIL PROTECTED]:~$ sudo /etc/init.d/dbus restart Password: * Stopping Hardware abstraction layer hald [ ok ] * Stopping system message bus dbus [ ok ] * Starting system message bus dbus [ ok ] * Starting Hardware abstraction layer hald [ **Hangs here for ages** ] run-parts: /etc/dbus-1/event.d/20hal exited with return code 2 It really strikes me that as a fix has been released for this but people are still having the problem that it's not fixed, so I'm going to be cheeky and re-open it, sorry.. -- hal-device-manager does not load https://launchpad.net/bugs/31517 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31517] Re: hal-device-manager does not load
Yes, same here, deleting user 'hal' and reinstalling hal created new user called 'haldeamon' and now it seems to be working ok! -- hal-device-manager does not load https://launchpad.net/bugs/31517 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
