[Bug 25931] Re: Failed to initalize HAL.
The issue persists for me on Ubuntu 8.04. It occurs about %50 of the time after every reboot. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Forgot to mention: ja...@jacob-laptop:/etc$ ls -l /etc/rc?.d/*dbus* lrwxrwxrwx 1 root root 14 2008-04-29 03:54 /etc/rc1.d/K88dbus - ../init.d/dbus lrwxrwxrwx 1 root root 14 2008-04-29 03:54 /etc/rc2.d/S12dbus - ../init.d/dbus lrwxrwxrwx 1 root root 14 2008-04-29 03:54 /etc/rc3.d/S12dbus - ../init.d/dbus lrwxrwxrwx 1 root root 14 2008-04-29 03:54 /etc/rc4.d/S12dbus - ../init.d/dbus lrwxrwxrwx 1 root root 14 2008-04-29 03:54 /etc/rc5.d/S12dbus - ../init.d/dbus ja...@jacob-laptop:/etc$ ls -l /etc/rc?.d/*hal* lrwxrwxrwx 1 root root 14 2007-01-04 13:08 /etc/rc0.d/S90halt - ../init.d/halt lrwxrwxrwx 1 root root 13 2008-05-09 05:05 /etc/rc1.d/K16hal - ../init.d/hal lrwxrwxrwx 1 root root 13 2008-05-09 05:05 /etc/rc2.d/S24hal - ../init.d/hal lrwxrwxrwx 1 root root 13 2008-05-09 05:05 /etc/rc3.d/S24hal - ../init.d/hal lrwxrwxrwx 1 root root 13 2008-05-09 05:05 /etc/rc4.d/S24hal - ../init.d/hal lrwxrwxrwx 1 root root 13 2008-05-09 05:05 /etc/rc5.d/S24hal - ../init.d/hal ja...@jacob-laptop:/etc$ ls -l /etc/rc?.d/*gdm* lrwxrwxrwx 1 root root 13 2007-06-04 17:03 /etc/rc0.d/K01gdm - ../init.d/gdm lrwxrwxrwx 1 root root 13 2007-06-04 17:03 /etc/rc1.d/K01gdm - ../init.d/gdm lrwxrwxrwx 1 root root 13 2007-06-04 17:03 /etc/rc2.d/S13gdm - ../init.d/gdm lrwxrwxrwx 1 root root 13 2007-06-04 17:03 /etc/rc3.d/S13gdm - ../init.d/gdm lrwxrwxrwx 1 root root 13 2007-06-04 17:03 /etc/rc4.d/S13gdm - ../init.d/gdm lrwxrwxrwx 1 root root 13 2007-06-04 17:03 /etc/rc5.d/S13gdm - ../init.d/gdm lrwxrwxrwx 1 root root 13 2007-06-04 17:03 /etc/rc6.d/K01gdm - ../init.d/gdm -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
It seems like this is my issue, as mentioned above: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/227838 -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
** Changed in: hal (Ubuntu) Assignee: Martin Pitt (pitti) = (unassigned) -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I experienced this behaviour today (2009-01-19) on Ubuntu 8.10: everything worked for me after the dist-upgrade some time ago. But, today I accidentally disabled the 'dbus' service within the services-admin tool. The X server was restarted automatically and I was not able to login anymore. The cursor was blinking but no mouse or keyboard was usable. Switching to a shell by Alt+F6 was possible. Here I manaully started the dbus service and I could login again. So, I opened the services-admin tool to re-enable the dbus service, rebooted the machine...and was not able to login. Same thing as before. I tried re-installing dbus, hal, system-tools-backends...no results. I was able to fix the problem by changing the priority of the rc2.d/dbus script: after disabling dbus in GUI: u...@host:/etc$ ls -l /etc/rc*/*dbus* lrwxrwxrwx 1 root root 14 2008-04-28 18:11 /etc/rc1.d/K88dbus - ../init.d/dbus lrwxrwxrwx 1 root root 14 2009-01-19 22:38 /etc/rc2.d/S50dbus - ../init.d/dbus lrwxrwxrwx 1 root root 14 2008-04-28 18:11 /etc/rc3.d/S12dbus - ../init.d/dbus lrwxrwxrwx 1 root root 14 2008-04-28 18:11 /etc/rc4.d/S12dbus - ../init.d/dbus lrwxrwxrwx 1 root root 14 2008-04-28 18:11 /etc/rc5.d/S12dbus - ../init.d/dbus u...@host:/etc$ ls -l /etc/rc*/*hal* lrwxrwxrwx 1 root root 14 2008-04-28 18:11 /etc/rc0.d/S90halt - ../init.d/halt lrwxrwxrwx 1 root root 13 2008-05-09 17:36 /etc/rc1.d/K16hal - ../init.d/hal lrwxrwxrwx 1 root root 13 2008-05-09 17:36 /etc/rc2.d/S24hal - ../init.d/hal lrwxrwxrwx 1 root root 13 2008-05-09 17:36 /etc/rc3.d/S24hal - ../init.d/hal lrwxrwxrwx 1 root root 13 2008-05-09 17:36 /etc/rc4.d/S24hal - ../init.d/hal lrwxrwxrwx 1 root root 13 2008-05-09 17:36 /etc/rc5.d/S24hal - ../init.d/hal u...@host:/etc$ ls -l /etc/rc*/*gdm* lrwxrwxrwx 1 root root 13 2008-04-28 18:11 /etc/rc0.d/K01gdm - ../init.d/gdm lrwxrwxrwx 1 root root 13 2008-04-28 18:11 /etc/rc1.d/K01gdm - ../init.d/gdm lrwxrwxrwx 1 root root 13 2008-04-28 18:11 /etc/rc2.d/S30gdm - ../init.d/gdm lrwxrwxrwx 1 root root 13 2008-04-28 18:11 /etc/rc3.d/S30gdm - ../init.d/gdm lrwxrwxrwx 1 root root 13 2008-04-28 18:11 /etc/rc4.d/S30gdm - ../init.d/gdm lrwxrwxrwx 1 root root 13 2008-04-28 18:11 /etc/rc5.d/S30gdm - ../init.d/gdm lrwxrwxrwx 1 root root 13 2008-04-28 18:11 /etc/rc6.d/K01gdm - ../init.d/gdm Fix: u...@host:/etc$ sudo mv /etc/rc2.d/S50dbus /etc/rc2.d/S12dbus u...@host:/etc$ ls -l /etc/rc*/*dbus* lrwxrwxrwx 1 root root 14 2008-04-28 18:11 /etc/rc1.d/K88dbus - ../init.d/dbus lrwxrwxrwx 1 root root 14 2009-01-19 22:38 /etc/rc2.d/S12dbus - ../init.d/dbus lrwxrwxrwx 1 root root 14 2008-04-28 18:11 /etc/rc3.d/S12dbus - ../init.d/dbus lrwxrwxrwx 1 root root 14 2008-04-28 18:11 /etc/rc4.d/S12dbus - ../init.d/dbus lrwxrwxrwx 1 root root 14 2008-04-28 18:11 /etc/rc5.d/S12dbus - ../init.d/dbus Finally everything is working again - but somewhere weird things happen. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Ran into this bug when doing a dist-upgrade from Edgy to Hardy (yes. directly!). Since I'm using KDE, I've moved /etc/rc[1-5].d/S13kdm to S30kdm and then rebooted my system - It's running fine now. Maybe the S13 S30 wasn't even necessary... -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I confirm : on Hardy (8.04) I found /etc/rc2.d/S50dbus - after renaming to S12dbus (ie. must be less than gdm, pulseaudio and avahi), the system starts normally. Prior to that, there used to be a message after login 'Internal error : failed to initialize HAL' and NM and other things were not working. My system is https://wiki.ubuntu.com/LaptopTestingTeam/AcerAspire3023, with all recent updates. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I don't know if this is a different bug, but I have searched high and low and cannot find a similar bug. This one is the closest to the problems I am having. I have Hardy 64bit (haven't tested 32bit) with a Gateway MX6433 (There are many other similar laptops from Gateway 6000 series) which has a Turion64 single core cpu and and I upgraded to Hardy from Gutsy. I use the -rt kernel for multimedia editing. I tried to fix the problem using the notes above, but I run in KDE and kdm, not Gnome and my rc2.d links are all correct as noted above. Nothing changes it. Here is the problem and here is the dmesg log section that identifies what happened: [ 4233.202422] dbus-daemon[5257]: segfault at 7fe705dd18e0 rip 7fe704eedae2 rsp 7fff0daa4778 error 4 I will attach a full log. I have no idea what error 4 is, but this seems to happen randomly whether I am at my machine or not. When dbus fails networkmanger and the battery monitor fail to report properly in KDE and it says that network manager is not running and the battery is not present. It is this second notification that alerts me when dbus crashes since network manager doesn't tell me it isn't running unless I go to use it. This doesn't seem to interrupt my use of the internet or local LAN however so it isn't a total show stopper, but it does prevent me from using my DVD writer (which also doesn't burn properly since Hardy either). DBus worked fine in Gutsy so this is definitely a regression of some kind or maybe a conflict with the new ATI drivers. I haven't had a chance to check this. ** Attachment added: dmesg.log http://launchpadlibrarian.net/14661507/dmesg.log -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 25931] Re: Failed to initalize HAL.
hi, DaFlame [2008-05-22 17:53 -]: I don't know if this is a different bug It is. Can you please open a separate report? This issue is already closed. [ 4233.202422] dbus-daemon[5257]: segfault at 7fe705dd18e0 rip 7fe704eedae2 rsp 7fff0daa4778 error 4 Eww. Maybe you can enable the crash reporter again by setting enabled=1 in /etc/default/apport and have apport file the crash bug? Thanks! -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Thank you. I will do just that. It may also give me insight to it as well. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Manfred, Christian, Aleksander, as I already wrote, this is bug 227838, and it is in progress. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I had the similar problem. The problem appeared after I had upgraded from Ubuntu 7.10 to Ubuntu 8.04 (64bit, Intel Core-Duo) via the update manager. The system worked more or less fine for a couple of weeks. One of the glitches was that it took a 10-20 seconds after login to recognize the network connection. The problem became serious after I ha inserted a data DVD in the DVD drive. The DVD drive on my machine (Dell Optiplex 745) never worked correctly under Ubuntu 7.10. I had to change the BIOS setting at every fresh bootup of Ubuntu to be able to open it and insert a CD/DVD. This is probably an issue of Dell, not of Ubuntu. However, after having inserted the data DVD, it first displayed the contents. At a 2nd trial, it refused to display anything. Only the DVD was spinning for a few seconds. That was the point of time after which I could not boot without the message 'Failed to initialize HAL'. The problems spread over the days to other functions such as access to USB memory sticks. Later, I was no longer able to shutdown (system froze after pressing the power- off icon on the upper right corner of the Gnome display). Fiinally, I was no able to start Gnome (gdm). Only the recovery mode saved me from loosing the PC. The problem vanished after executing sudo mv /etc/rc.d/13gdm /etc/rc.d/30gdm as advised above. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
As Martin said above, Aleksander, your GDM is starting too early. It's S13 -- it should be S30. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I also get the failed to initilize hal error, but ONLY if autologin is enabled. I guess it logs in too quickly because of an incorrect priority list? rc0.d/K01gdm rc2.d/S13gdm rc4.d/S13gdm rc6.d/K01gdm rc1.d/K01gdm rc3.d/S13gdm rc5.d/S13gdm rc1.d/K88dbus rc2.d/S12dbus rc3.d/S12dbus rc4.d/S12dbus rc5.d/S12dbus rc1.d/K16hal rc2.d/S24hal rc3.d/S24hal rc4.d/S24hal rc5.d/S24hal rc0.d/K16dhcdbd rc2.d/S24dhcdbd rc4.d/S24dhcdbd rc6.d/K16dhcdbd rc1.d/K16dhcdbd rc3.d/S24dhcdbd rc5.d/S24dhcdbd This is a Thinkpad X40, running Hardy, which was upgraded from Fiesty. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 25931] Re: Failed to initalize HAL.
Hi Thomas, your rc* symlinks are correct, so hal fails for some other reason on your system. Your hal.log looks good, it doesn't seem to have crashed (I guess you used Control-C to stop it). Can you please file a new bug about this? I guess we have to debug that differently. Thanks! -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Ah, sorry. You still have gdm on level 13, but it shuold be at 30. I guess you did not change that manually, so it is an upgrade bug from Feisty. Can you please create a new bug report against gdm for that? Thank you! BTW, if you just wait a bit on the gdm prompt, it should work fine. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Thanks! I've changed the level of gdm to 30 and everything's fine now. I've created a new bug report against gdm which can be found at https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/227838 -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I just ran into this problem after updating to hal 0.5.11~rc2-1ubuntu8 (which was supposed to fix this bug for some people if I got the discussion right) on my Samung R20 running Hardy. Neither the subsequent update to 0.5.11~rc2-1ubuntu8.1 nor the downgrade to 0.5.11~rc2-1ubuntu7 did help. After logging in with gdm I get the infamous Failed to initialize HAL message. Wifi isn't working at first but comes up after about 30 seconds. $ ls -l /etc/rc*/*dbus* /etc/rc1.d/K88dbus - ../init.d/dbus /etc/rc2.d/S12dbus - ../init.d/dbus /etc/rc3.d/S12dbus - ../init.d/dbus /etc/rc4.d/S12dbus - ../init.d/dbus /etc/rc5.d/S12dbus - ../init.d/dbus $ ls -l /etc/rc*/*hal /etc/rc1.d/K16hal - ../init.d/hal /etc/rc2.d/S24hal - ../init.d/hal /etc/rc3.d/S24hal - ../init.d/hal /etc/rc4.d/S24hal - ../init.d/hal /etc/rc5.d/S24hal - ../init.d/hal $ ls -l /etc/rc*/*gdm* /etc/rc0.d/K01gdm - ../init.d/gdm /etc/rc1.d/K01gdm - ../init.d/gdm /etc/rc2.d/S13gdm - ../init.d/gdm /etc/rc3.d/S13gdm - ../init.d/gdm /etc/rc4.d/S13gdm - ../init.d/gdm /etc/rc5.d/S13gdm - ../init.d/gdm /etc/rc6.d/K01gdm - ../init.d/gdm ** Attachment added: hal.log http://launchpadlibrarian.net/14260848/hal.log -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
** Attachment added: lshal.txt http://launchpadlibrarian.net/14260858/lshal.txt -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
** Attachment added: kern.log http://launchpadlibrarian.net/14260875/kern.log -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
changing the priority of hal in rc2.d from 24 to 13 seems to fix the problem for me. by the way, my upgrade history is feisty - gutsy - hardy. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Copied to hardy-updates. ** Changed in: hal (Ubuntu) Status: Fix Committed = Fix Released ** Changed in: hal (Ubuntu Hardy) Status: Fix Committed = Fix Released ** Changed in: hal (Ubuntu) Status: Fix Released = Fix Committed -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
This bug was fixed in the package hal - 0.5.11~rc2-1ubuntu9 --- hal (0.5.11~rc2-1ubuntu9) intrepid; urgency=low * Add 03_increase_helper_timeout.patch: Increase helper timeout from 10 to 20 seconds. Some CD-ROMs are too slow to do all the detection in 10 seconds. (LP: #218834) hal (0.5.11~rc2-1ubuntu8) hardy-proposed; urgency=low * debian/hal.postinst: If hal has any start rc symlinks, force them back to 24. A lot of people end up with priority 12 for some reason, which races with dbus startup, especially with CONCURRENCY=shell. (LP: #25931) * Add 00upstream-fix-macbook-backlight.patch: Fix backlight control on MacBooks. Thanks to godlygeek! (LP: #206921) -- Martin Pitt [EMAIL PROTECTED] Wed, 30 Apr 2008 11:00:07 +0200 ** Changed in: hal (Ubuntu) Status: Fix Committed = Fix Released -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I'm experiencing the same problem. I tried many workaround but none seemed to work. Here are my rc2.d links: [...] S12dbus - ../init.d/dbus [...] S13hal - ../init.d/hal [...] S30gdm - ../init.d/gdm [...] I tried to reinstall hal, using #sudo aptitude reinstall hal but it not worked because hald cannot find the required file: /var/run/dbus/system_bus_socket indeed the directory is EMPTY!!! Any suggestion about how to solve this annoying problem? -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I just noticed that /var/run/dbus/system_bus_socket was hidden. By the way it cannot be found by the hal. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Ok, I resolved the problem. I would like to inform that the users whose are having the problem with: log_daemon_msg : Not found can try this workaround: $ sudo mv init-functions.old init-functions I tried to search the word: log_daemon inside init-functions but there was no match. Then I found it in the .old, so I renamed .old to init-functions and rebooted with: $ sudo reboot Now everything works fine. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
SRU ack for the fix from http://bazaar.launchpad.net/~ubuntu-core- dev/hal/ubuntu/revision/230. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Accepted into hardy-proposed. Please test the packages from the archive and give feedback here. Thank you! ** Changed in: hal (Ubuntu Hardy) Status: In Progress = Fix Committed ** Tags added: verification-needed -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Fixed in trunk, will upload to intrepid once the archive is open. ** Changed in: hal (Ubuntu) Status: In Progress = Fix Committed Target: ubuntu-8.04.1 = None -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
After upgrading from gutsy to hardy I experienced this problem of hald not starting and avahi-daemon also not starting. I redid the symlinks for hal (12-24) and gdm (13-30) but that didn't cure the problem. Starting hald manually indicated that it was failing while trying to open /usr/local/var/run/dbus/system_bus_socket. In desperation I symlinked /usr/local/var/run/dbus/system_bus_socket to /var/run/dbus/system_bus_socket. That seemed to cure my problem. I don't know why /usr/local/var/run/dbus/system_bus_socket is needed. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 25931] Re: Failed to initalize HAL.
hi finlay, finlay [2008-04-30 11:59 -]: Starting hald manually indicated that it was failing while trying to open /usr/local/var/run/dbus/system_bus_socket. Ugh, how weird. That's an entirely different issue then, can you please file a new bug with the hal log? Thank you! -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Martin, just tested the new version in hardy-proposed. Works like a charme. Good job! Thanks, Daniel -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I recreated the problem using hal package version 0.5.11~rc2-1ubuntu7 from Hardy. I then installed package version 0.5.11~rc2-1ubuntu8 from hardy-proposed and the symlinks were set properly. I did not use the CONCURRENCY=shell option as it wasn't clear to from the test case what to look for. ** Description changed: This seems to be a fairly common bug. However, none of the solutions I have come across in previous bug repors have helped me. When I run Ubuntu, just like everyone else, I get Failed to initalize HAL. I can continue to use the GUI for a few minutes, but eventually (especially when navigating the filesystem/CD-ROM,) the system hangs and I am forced to reboot. Though I am very new to Linux, I will help in the analysis in any way I can. TEST CASE: - Set the rc.d symlinks to start level 12, to get to the situation many bug reporters end up with for some reason: sudo update-rc.d -f hal remove - sudo update-rc.d hal start 12 2 3 4 5 . stop 12 1 + sudo update-rc.d hal start 12 2 3 4 5 . stop 12 1 . - (optional, since racy): Set CONCURRENCY=shell in /etc/init.d/rc, boot, and watch hal fail to load - upgrade to the new hardy-proposed version (0.5.11~rc2-1ubuntu8), check that the rc symlinks are now at S24, and that the system boots properly with CONCURRENCY=shell. ** Tags added: verification-done ** Tags removed: verification-needed -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 25931] Re: Failed to initalize HAL.
Hi Daniel, Daniel Rheinbay [2008-04-28 17:48 -]: Looking at hal's postinst script, I'm wondering why we don't invoke update-rc.d regardless of the hal version? Just to be on the safe side... Because forcibly removing and reinstalling the symlinks is already a gross violation of Policy. We just clobber an administrator's configuration without asking. So it should always be a last resort, and not be done with every upgrade. -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Uploaded, awaiting peer review in the queue now: hal (0.5.11~rc2-1ubuntu8) hardy-proposed; urgency=low * debian/hal.postinst: If hal has any start rc symlinks, force them back to 24. A lot of people end up with priority 12 for some reason, which races with dbus startup, especially with CONCURRENCY=shell. (LP: #25931) -- Martin Pitt [EMAIL PROTECTED] Mon, 28 Apr 2008 07:44:11 +0200 http://bazaar.launchpad.net/~ubuntu-core-dev/hal/ubuntu/revision/230 -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Hi, Mine was (probably) unusual, in that I upgraded a (newly installed and patched) 6.06 installation straight to 8.04. Did this because my father has a PC running 6.06, and he never receives the newer distribution available update notice when he runs the update manager. To see what might be going on, 6.06 got installed from CD into a VMware virtual machine, and then latest updates applied. Yep, he's right, there's no notification of a newer Ubuntu version being available. Instead, ran the command to check if there are any development versions that can be upgraded to, and it suggested 8.04 (pre release at the time). As this was a virtual machine I thought what the heck and let it proceed. Everything seemed ok afterwards except for the HAL initialisation failure error, that turned out to be because it wasn't in the rc levels after the upgrade. Hope that helps. :) -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Martin, your fix appears to do the job. Though I didn't actually build a new package, I just ran update-rc.d -f hal remove update-rc.d hal start 24 2 3 4 5 . stop 16 1 . which resulted in hal's priorities being deferred to S24. Everything's running smooth now. Looking at hal's postinst script, I'm wondering why we don't invoke update-rc.d regardless of the hal version? Just to be on the safe side... Glad we got this one squashed though :) And, just for the records: @Martin: Nope, haven't used Automatix. @Bruce: Thanks for your comment, but my Inspiron 6400n (aka e1505) came pre-installed with Ubuntu, all of its components are supported by Ubuntu and I don't have any peripheral devices attached to it. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Daniel, indeed the priorities are wrong for you. It should be S24, not S12 (that's too early and races with dbus). So far the upgrade only forces the symlinks to be correct for upgrades from dapper, not from gutsy. Seems we have to do that for those upgrades as well. ** Changed in: dbus (Ubuntu Hardy) Status: Fix Released = In Progress Target: ubuntu-8.04-beta = ubuntu-8.04.1 -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Argh, that was solved for dbus already. ** Description changed: This seems to be a fairly common bug. However, none of the solutions I have come across in previous bug repors have helped me. When I run Ubuntu, just like everyone else, I get Failed to initalize HAL. I can continue to use the GUI for a few minutes, but eventually (especially when navigating the filesystem/CD-ROM,) the system hangs and I am forced to reboot. Though I am very new to Linux, I will help in the analysis in any way I can. + + TEST CASE: + - Set the rc.d symlinks to start level 12, to get to the situation many bug reporters end up with for some reason: + sudo update-rc.d -f hal remove + sudo update-rc.d hal start 12 2 3 4 5 . stop 12 1 + - (optional, since racy): Set CONCURRENCY=shell in /etc/init.d/rc, boot, and watch hal fail to load + - upgrade to the new hardy-proposed version (0.5.11~rc2-1ubuntu8), check that the rc symlinks are now at S24, and that the system boots properly with CONCURRENCY=shell. ** Changed in: dbus (Ubuntu Hardy) Status: In Progress = Fix Released Target: ubuntu-8.04.1 = ubuntu-8.04 ** Also affects: hal (Ubuntu) Importance: Undecided Status: New -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
BTW, did you guys use automatix, or any other third-party tune your system application? I wonder how you ended up with those broken RC levels in the first place. ** Changed in: hal (Ubuntu Hardy) Importance: Undecided = High Status: New = In Progress Target: None = ubuntu-8.04.1 ** Changed in: hal (Ubuntu Hardy) Assignee: (unassigned) = Martin Pitt (pitti) -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
No longer occurs with definitive, 24th April Release, but please see #221953. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 25931] Re: Failed to initalize HAL.
I've make a new bug report, related to the current issue: https://bugs.launchpad.net/bugs/218528 On Wed, 2008-04-16 at 09:01 +, Martin Pitt wrote: Ripps818 [2008-04-16 0:52 -]: I'm having the same Fail to initialize Hal error in my Hardy 2.6.24-16. I can boot up correctly with 2.6.22-14 Can you please open a new bug about this, and do the steps in https://wiki.ubuntu.com/DebuggingHal, and include the logs? Thank you! -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
YES, for Ubuntu 8.04 Release Candidate, its kernel 2.6.24-16-generic lack of TV tuner drivers is causing HAL initialization failure or worse for my [A] rig E2160 with its AverTV A777 PCI card using a Zarlink MT352 DVB-T chip. There's also no driver for my [C] rig Northwood P4 AverTV A800 USB module and its DiBcom 3000MC/P chip, which only prevents Freeview reception but doesn't block installation. Indeed, my [C] rig gets so far as to confirm the absence of a suitable driver when configuring Kaffeine. Re-installing Ubuntu 7.10 on my [A] or [C] rigs confirms the presence of drivers in the slightly modified 2.6.22-14-generic kernel. It will probably take another hard days work to further confirm with my 'work in progress' E4600 rig, but I'm convinced, so thank you, Ripps818 -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I got this error when trying to boot the livecd of the RC on my computer, and therefore have no internet and sound; a releasecritical bug. Output from lspci: 00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2) 00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3) 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3) 00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3) 00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) 00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1) 00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2) 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 02:00.0 VGA compatible controller: ATI Technologies Inc RV516 XT Radeon X1600 Series (Primary) 02:00.1 Display controller: ATI Technologies Inc RV516 XT Radeon X1600 Series (Secondary) 03:05.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70) 03:08.0 Ethernet controller: Atheros Communications Inc. AR5413 802.11abg NIC (rev 01) 03:09.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder (rev d1) 03:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a) 03:0a.1 Input device controller: Creative Labs SB Live! Game Port (rev 0a) -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 25931] Re: Failed to initalize HAL.
Hi Åskar And I thought that my rigs were complex ! Mind you, I think that you will find it easier to tackle other problems if you can disable or even temporarily remove your Philips SAA7133/SAA7135 device. The lack of suitable chipset drivers in the Release Candidate kernel seems to be preventing installation or at least masking other problems. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Please follow Martin Pitt comment if you really want to tackle down the problem. Without proper debug information, we can't really now why hal failed to start. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 25931] Re: Failed to initalize HAL.
Sorry, but while you are gathering more detailed evidence, I am simply by-passing the problem. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
In my case it's the, only recently surfaced, connection Philips Tv-card. I read through this whole thread, noting down dif'rent fixes that didn't seem to make much sense, until I hit on the Philips-tv card thing. I have a ZOLID tv-card (from ALDI), wich has a Philips chip SAA 71-something. I removed it, rebooted and the bug was solved. What 'bugs' me is this: the problem didn't exist in the latest beta, until I did an update some weeks ago. before that, everything was fine. So it can't have to do with the kernel version (or maybe in some strange indirect way). Anyway, I just installed the RC, hoping not to get that threaded 'failed to initialise hal' message, and was mighty disappointed. I was about to reinstall my Gutsy (wich doesn't mind my tv-card, not even after the latest updates) until I tried removing the card. Think I'll stick with Hardy (I like my stuff cutting the edgez), but for how long I can't tell; I want to use my tv-card eventually... So, another day, another clue. If needed i'll post more details to my system, just ask. For now; hope this get fixed, lve ubuntu still, eventhough it's as hard as real love in the real world sometimes... -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 25931] Re: Failed to initalize HAL.
Leeuw a écrit : In my case it's the, only recently surfaced, connection Philips Tv-card. I read through this whole thread, noting down dif'rent fixes that didn't seem to make much sense, So these means that your bug is different than the original one. This bug report is really old and was cause by something simple : hal was started too late. It was fix a long time ago and it seams your bug is different. So you really should follow martin comment : open a new bug and please FOLLOW https://wiki.ubuntu.com/DebuggingHal TO GET REAL DEBUG INFORMATION. Thanks. And stop commenting on this fixed bug, you will not get the visibility you deserve. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Unfortuatanaly I've got the same problem in Hardy. I assume it happened after I update Ubuntu. When I boot into Hardy I got the message Failed to initialize Hal and my network doesn't work at all. Everything worked fine before. Is there a solution for this bug? -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I fixed my Hal problem by disabling all modules for my Tv Tuner. I read in a another HAL bug report that the newest round of kernel release caused this problem to people with TV Tuner cards. Modules I blacklisted: cx88xx cx8800 cx88_alsa -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
In Report #216159 I reported that that Kardy kernels -15 and -16 caused problems for my E2160 with its Zarlink MT352 DBV-T (Aver A777) PCI card identified as the likely cause, the card being happier with -12 and perfectly happy with 7.10's kernel. Now, Release Candidate 8.04 won't even install or run a LiveCD session on my E2160/Zarlink rig, let alone raise a HAL initialization failure. So, in view of Ripps818 comment, I will next try Release Candidate installation on my 3.0GHz Nothwood rig, with and without its USB2 DibCom tuner attached before trying it out on a 'work in progress' E4600 rig which has NO tuner module (yet) and then report back. (But first I'll add a comment to Bug Report #217726.) -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 25931] Re: Failed to initalize HAL.
Ripps818 [2008-04-16 0:52 -]: I'm having the same Fail to initialize Hal error in my Hardy 2.6.24-16. I can boot up correctly with 2.6.22-14 Can you please open a new bug about this, and do the steps in https://wiki.ubuntu.com/DebuggingHal, and include the logs? Thank you! -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I'm having the same Fail to initialize Hal error in my Hardy 2.6.24-16. I can boot up correctly with 2.6.22-14, but I lose my fglrx ogl libraries and my keryring daemon crashes (yet it still seems to work). I've tried all the reconfiguring/reinitialize of hald and dbus, as well as messing with rc configs; still nothing. After looking at some of my log files, the only error I can find in concern to HAL comes when pulseaudio is first initializing. I'm not sure if it's the cause, and I don't know how to stop it from starting to see if it's the cause. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
The same issue on kernel 2.6.24-16-generic. After the long-long boot process. PS Lets postpone final release, I have never met so much bugs in ubuntu. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Ubuntu 8.04 pre-release - 11 April 2008 Having just successfully applied the latest series of Partial Updates to my 3.0GHz Northwood rig, tried with my E2160 rig, first with its second Vista drive connected and then disconnected unless that was the problem, but no joy, 'Internal error' 'failed to initialise HAL!' with crash report failing exactly as before. Once again, restored image of Gutsy installation performing without problems. Tomorrow, after my blood pressure has gone down, I'll try HardyBeta installation on an E4600 rig, similar to the E2160 rig. AS you will gather from the attached partial screen shot, some functionality is present, like the GIMP, but ICONS are only displaying Linux, not former NTFS nomenclatures, plus some of the error messages. The screen is locked up, not responding to Quit, needing a hard reset. (Picture acquired from a drive after GRUB re-start into Windows XP ** Attachment added: PartialScreenshot-11apr2008.jpg http://launchpadlibrarian.net/13362942/PartialScreenshot-11apr2008.jpg -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Later on, I tried another re-install on my E2160 rig, which took two hours, consisted of 509 packages and included new kernel 2.6.24-16-generic, removed kernel 2.6.24-15-generic and left kernel 2.6.24-12-generic. Normal re-start into kernel 2.6.24-16-generic after a very slow re-boot, produced Linux, non-NTFS drive icons and very slow response before locking up and needing a hard reset, so selected kernel 2.6.24-12-generic which seems to be working well. It's been another long day, not good for my blood pressure. After a nights rest, I'll finish checking functionality and package interactions. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Having failed to re-install Ubuntu 8.04 on my E2160 [A] rig, I then succeeded on my Northwood P4 [B] rig. Re-trying with my [A] rig, it was happy to re-install Ubuntu 7.10 but once again wouldn't take 8.04 (now withx483 updates !) After Updates application and a very slow, reluctant re-start it failed to display normal drive icons and displayed an 'Internal error' 'failed to initialise HAL !' message. Not being a Linux expert I nevertheless tried Justin Clift's entry in Terminal, to no avail. I will now try again, substituting $15hal for S15hal (Don't know what I'm doing but I know that the slightest typo screws up command line instructions.) -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Sorry, should have made it clear that I'm talking about 8.04 Beta. The re-type didn't work either and needed a hard reset, System, Quit no longer working. (Note that 'crash report detected', then slowly reported - Sorry, the program gnome-keyring-daemon closed unexpectedly, etc, but Report Problem enentually said - Could not upload report to crash database: urlopen error (-5, 'No address associated with hostname') Whilst waiting for a revised, complex set of Updates or further 8.04 releases, I'll have to revert to 7.10, pity, it was getting there ! -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I think this has to do with my cd rom. It has always been a bit of a problem in that it won't recognise burnt cd's when it is the first type of cd I open. If I try factory made cd's first then I can try a burnt cd. But today I got the above error when I booted with the cd in the drive. I just closed the error box and i was able to do everything else except open and cd rom files. None of my usual tricks are working now. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Hi, I'm getting the Failed to initialize HAL error message after upgrading to 8.04 alpha last week. Running this in a VMware Workstation virtual machine for testing. Happens on every boot. Investigated a few options people mention on the forums, but nothing worked. Then looking at the /etc/rc2.d directory I noticed hal wasn't even listed! S12dbus - ../init.d/dbus S13gdm - ../init.d/gdm and no hal at all. Did a: $ sudo ln -s ../init.d/hal S15hal And rebooted, and now everything seems to start up properly. The CONCURRENCY level in /etc/init.d/rc hasn't been touched, it was already at none when I checked. Hope this helps. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Had the same problem on my eeepc with Gutsy. Wireless wouldn't work nor would my ethernet device be detected. I could do a quick 'sudo /etc/init.d/hal start' and it my networking would work fine including the wireless auto starting. I would also have to manually mount my external cdrom and HD, even after I started HAL. After researching extensively on this site and others, I tried changing my CONCURRENCY=none in /etc/init.d/rc. Now, no error, and my wireless, wired and external cdrom and external HD mount and initialize without issue. Thanks fellas. -- Decaffeinated coffee is kinda like kissing your sister. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
This bug was fixed in the package dbus - 1.1.20-1ubuntu1
---
dbus (1.1.20-1ubuntu1) hardy; urgency=low
* New upstream release: Tons of bug fixes, a security fix (CVE-2008-0595),
and two small new features:
- inotify support (to replace previous dnotify implementation); can be
disabled with configure switch if it causes trouble
- Add matching support for program binaries in dbus policy rules.
* Merge with Debian unstable; remaining changes:
- debian/patches/81-session.conf-timeout.patch: Raise the service startup
timeout from 25 to 60 seconds. It may be too short on the live CD with
slow machines.
- Add consolekit (= 0.2.3-3ubuntu2) dependency, which provides
pam_console compatible stamps in /var/run/console. This keeps
at_console policies working until we get rid of them completely.
(See policykit-integration spec)
- debian/dbus.{postinst,prerm}: Do not restart dbus on upgrades, since it
breaks too many applications. Instead, trigger a reboot required
notification. Since this cancels the postinst early, add an explicit
update-rc.d call to the symlink migration.
- debian/rules: Do not install /etc/X11/Xsession.d/75dbus_dbus-launch, we
do not need it for Gnome, KDE, and XFCE, and it causes trouble.
(LP #62163)
- debian/dbus.preinst: Remove obsolete conffile
/etc/X11/Xsession.d/75dbus_dbus-launch on upgrades. This needs to be
kept until after Hardy's release.
* Debian's forceful way of RC symlink migration should finally fix all the
previous upgrade issues with wrong priorities. (LP: #25931)
dbus (1.1.20-1) unstable; urgency=medium
[ Loic Minier ]
* Forcefully remove old init script symlinks on upgrades to this version to
properly reinstall the init script when using insserv or file-rc; thanks
Petter Reinholdtsen; closes: #466503.
[ Michael Biebl ]
* New upstream release.
dbus (1.1.4-1) unstable; urgency=low
[ Loic Minier ]
* Merge patch from Ubuntu to build a devhelp file; thanks Martin Pitt;
closes: #454142.
- Build-dep on xsltproc.
- New patch, dbus-1.0.1-generate-xml-docs, enables generation of XML docs
which serve as source for the devhelp generation.
- Add a XSLT file from the Fedora package, debian/doxygen_to_devhelp.xsl.
- Generate the devhelp file from the XML files thanks to the XSL file via
xsltproc in build/dbus-1-doc::.
- Install the devhelp index in dbus-1-doc and move the HTML documentation
around; add a symlink from the gtk-doc dir.
* Misc smallish whitespace cleanups.
* Start dbus at runlevel priority 12 and stop at priority 88. This
eliminates the race condition of starting the X session before hal is
running. Migrate rc?.d symlinks from 20 to 12/88 on upgrades. This need
to be kept until after lenny is released.
* Set LSB Default-Stop section to 1 and only install a shutdown script for
runlevel 1 to only stop dbus when going down to single user mode; dbus can
simply be killed like everything else on shutdown or reboot by sendsigs;
drop rc0 and rc6.d symlinks on upgrades.
* Bump up dbus-x11 conflicts/replaces to 1.1.2 to match the transition
version in Ubuntu and reduce the delta.
* Cleanup trailing whitespace.
* Drop superfluous exit 0 at the end of dbus' init script which is set -e.
* Add ${shlibs:Depends} to libdbus-1-dev.
* Simplify dbus.postinst.
* Rename patch dbus-1.0.1-generate-xml-docs to
10_dbus-1.0.1-generate-xml-docs to reflect current patch stack order.
* Set shlibs via DEB_DH_MAKESHLIBS_ARGS_ALL instead of libdbus-1-3.shlibs
and extract libdbus-1-3 package name from control to avoid hardcoding the
SONAME and package name.
[ Michael Biebl ]
* New upstream release.
* Deprecate the ENABLED option and remove it from /etc/default/dbus. Print a
warning message in the init script if this option is still used.
* debian/patches/03_uuid_nul.patch
- Removed, merged upstream.
* debian/patches/04_dbus_launch.patch
- Removed, merged upstream.
* debian/control
- Bump Standards-Version to 3.7.3. No further changes required.
* debian/dbus.init
- Fix LSB init header. Use $remote_fs instead of $local_fs as the
daemon requires /usr to be mounted.
Remove S from Should-Stop. (Closes: #459473)
- Use mountpoint to check if /proc is mounted. (Closes: #458392)
- Decrease retry-time to 5 secs on stop. (Closes: #462182)
-- Martin Pitt [EMAIL PROTECTED] Thu, 28 Feb 2008 15:08:15
+0100
** Changed in: dbus (Ubuntu Hardy)
Status: Fix Committed = Fix Released
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2008-0595
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
[Bug 25931] Re: Failed to initalize HAL.
We should forcefully remove all old RC symlinks and reinstall them at level 12 at this stage, to fix this once and for all. ** Changed in: dbus (Ubuntu Hardy) Status: New = In Progress ** Changed in: dbus (Ubuntu Hardy) Target: None = ubuntu-8.04-beta -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
This is fixed in the proposed 1.1.20 packages in my PPA. Hardy upload pending approval in bug 196568. ** Changed in: dbus (Ubuntu Hardy) Status: In Progress = Fix Committed -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Today's updates fixed this for me. thanks, you can close the bug as it relates to me. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
** Tags added: hardyheronalpha4 -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Added My Info ** Changed in: dbus (Ubuntu Hardy) Status: Incomplete = New -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Hardy Heron Alpha 4 I have had this error for a couple or few days after an update. My computer starts up, then an error message pops up Internal Error Failed to initialize HAL!. U.S.B. Wireless adapter does not work quite right. Ethernet connect is not stable. Icon in notify window has ! exclamation point inside an orange triangle below the network status icon. Shutdown takes a long long time, minutes and really slows everything down. ** Attachment added: screenshot of Error Message http://launchpadlibrarian.net/11987404/Screenshot.png -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
[EMAIL PROTECTED]:~# ps -p $( /var/run/dbus/pid) PID TTY TIME CMD 4941 ?00:00:00 dbus-daemon [EMAIL PROTECTED]:~# pidof hald [EMAIL PROTECTED]:~# ls -l /etc/rc2.d/*dbus* lrwxrwxrwx 1 root root 14 2008-02-06 02:53 /etc/rc2.d/S12dbus - ../init.d/dbus [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# sudo /etc/init.d/dbus start * system message bus already started; not starting. [EMAIL PROTECTED]:~# ps -p $( /var/run/dbus/pid) PID TTY TIME CMD 4941 ?00:00:01 dbus-daemon [EMAIL PROTECTED]:~# pidof hald [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# sudo mv /etc/rc2.d/S20dbus /etc/rc2.d/S12dbus mv: cannot stat `/etc/rc2.d/S20dbus': No such file or directory [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# sudo ln -s ../init.d/dbus /etc/rc2.d/S12dbus ln: creating symbolic link `/etc/rc2.d/S12dbus': File exists [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# locate S??dbus /etc/rc5.d/S12dbus /etc/rc3.d/S12dbus /etc/rc4.d/S12dbus /etc/rc2.d/S12dbus [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# sudo dbus-daemon --system Failed to start message bus: The pid file /var/run/dbus/pid exists, if the message bus is not running, remove this file [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# sudo dpkg-reconfigure hal * Stopping Hardware abstraction layer hald [ OK ] * Reloading system message bus config...[ OK ] * Starting Hardware abstraction layer hald invoke-rc.d: initscript hal, action start failed. [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# sudo mkdir /var/run/dbus mkdir: cannot create directory `/var/run/dbus': File exists [EMAIL PROTECTED]:~# sudo chown messagebus:messagebus /var/run/dbus [EMAIL PROTECTED]:~# sudo dbus-daemon --system Failed to start message bus: The pid file /var/run/dbus/pid exists, if the message bus is not running, remove this file [EMAIL PROTECTED]:~# sudo dpkg-reconfigure hal * Stopping Hardware abstraction layer hald [ OK ] * Reloading system message bus config...[ OK ] * Starting Hardware abstraction layer hald invoke-rc.d: initscript hal, action start failed. [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# ls -1 /etc/rc?.d/*dbus /etc/rc1.d/K20dbus /etc/rc2.d/S12dbus /etc/rc3.d/S12dbus /etc/rc4.d/S12dbus /etc/rc5.d/S12dbus [EMAIL PROTECTED]:~# ls -1 /etc/rc?.d/*dbus /etc/rc1.d/K20dbus /etc/rc2.d/S12dbus /etc/rc3.d/S12dbus /etc/rc4.d/S12dbus /etc/rc5.d/S12dbus [EMAIL PROTECTED]:~# ls -1 /etc/rc?.d/*dhcdbd /etc/rc0.d/K16dhcdbd /etc/rc1.d/K16dhcdbd /etc/rc2.d/S24dhcdbd /etc/rc3.d/S24dhcdbd /etc/rc4.d/S24dhcdbd /etc/rc5.d/S24dhcdbd /etc/rc6.d/K16dhcdbd [EMAIL PROTECTED]:~# I did not use Automatix because it doesn't work on this version. Not sure about other 3rd Party apts changing global stuff. [EMAIL PROTECTED]:~# sudo mv /etc/rc2.d/S12hal /etc/rc2.d/S13hal mv: cannot stat `/etc/rc2.d/S12hal': No such file or directory [EMAIL PROTECTED]:~# Things are pretty sluggish. System Administration Network Settings experience. Dialog is greyed out for about 90 seconds. Then populates. Was able to set-up ethernet and wireless connections, but had to use manual settings. Navigating in this dialog takes plenty of patience. Often over a minute between actions. Does anybody have Compiz Fusion turned on? no, I don't think so, not sure what it is. [EMAIL PROTECTED]:~# /etc/init.d/dbus start * system message bus already started; not starting. [EMAIL PROTECTED]:~# /etc/init.d/dhcdbd start * Starting DHCP D-Bus daemon dhcdbd [ OK ] [EMAIL PROTECTED]:~# /etc/init.d/hal start * Starting Hardware abstraction layer hald [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# sudo mv /var/cache/hald/fdi-cache~ /var/cache/hald/fdi-cache mv: cannot stat `/var/cache/hald/fdi-cache~': No such file or directory [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# sudo /usr/lib/hal/hald-generate-fdi-cache 04:37:17.254 [E] create_cache.c:635: Unable to open fdi cache '/var/cache/hald/fdi-cache~' file for writing: No such file or directory 04:37:17.255 [E] create_cache.c:704: Error generating fdi cache [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# sudo mv /etc/rc2.d/S50dbus /etc/rc2.d/S12dbus mv: cannot stat `/etc/rc2.d/S50dbus': No such file or directory [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# sudo mv /var/cache/hald/fdi-cache~ /var/cache/hald/fdi-cache mv: cannot stat `/var/cache/hald/fdi-cache~': No such file or directory [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# ls /etc/rc2.d | sort K20hotkey-setup K74bluetooth README S01policykit S05vbesave S10acpid S10powernowd.early S10sysklogd S10xserver-xorg-input-wacom S11klogd S12dbus S18avahi-daemon S19cupsys S20apmd S20apport S20bootlogd S20clamav-freshclam S20hdparm S20nvidia-kernel S20powernowd S20rsync S20wifi-radar S23ntp S24dhcdbd S24hal S25pulseaudio S30gdm S50alsa-utils S89anacron S89atd
[Bug 25931] Re: Failed to initalize HAL.
[EMAIL PROTECTED]:~# gdb dbus 21 | tee gdb-dbus.txt GNU gdb 6.7.1-debian Copyright (C) 2007 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu... dbus: No such file or directory. (gdb) handle SIG33 pass nostop noprint SignalStop Print Pass to program Description SIG33 NoNo Yes Real-time event 33 (gdb) set pagination 0 (gdb) run Starting program: No executable file specified. Use the file or exec-file command. (gdb) -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
[EMAIL PROTECTED]:~# pidof dbus [EMAIL PROTECTED]:~# pidof /etc/init.d/dbus [EMAIL PROTECTED]:~# -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
[EMAIL PROTECTED]:~# strace -Ff -tt /etc/init.d/dbus 21 | tee strace-dbus.log
05:10:08.270937 execve(/etc/init.d/dbus, [/etc/init.d/dbus], [/* 31 vars
*/]) = 0
05:10:08.273015 brk(0) = 0x805e000
05:10:08.273395 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
05:10:08.273742 mmap2(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7f6f000
05:10:08.274064 access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or
directory)
05:10:08.274369 open(/etc/ld.so.cache, O_RDONLY) = 3
05:10:08.274659 fstat64(3, {st_mode=S_IFREG|0644, st_size=64796, ...}) = 0
05:10:08.274999 mmap2(NULL, 64796, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7f5f000
05:10:08.275277 close(3)= 0
05:10:08.314090 access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
05:10:08.314547 open(/lib/tls/i686/cmov/libc.so.6, O_RDONLY) = 3
05:10:08.314856 read(3,
\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260e\1..., 512) = 512
05:10:08.315179 fstat64(3, {st_mode=S_IFREG|0755, st_size=1364388, ...}) = 0
05:10:08.315490 mmap2(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7f5e000
05:10:08.315857 mmap2(NULL, 1369712, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7e0f000
05:10:08.316154 mmap2(0xb7f58000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x149) = 0xb7f58000
05:10:08.316493 mmap2(0xb7f5b000, 9840, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7f5b000
05:10:08.316824 close(3)= 0
05:10:08.317151 mmap2(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7e0e000
05:10:08.317448 set_thread_area({entry_number:-1 - 6, base_addr:0xb7e0e6b0,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
seg_not_present:0, useable:1}) = 0
05:10:08.318002 mprotect(0xb7f58000, 4096, PROT_READ) = 0
05:10:08.318375 munmap(0xb7f5f000, 64796) = 0
05:10:08.318749 getpid()= 8794
05:10:08.319027 rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0
05:10:08.319325 geteuid32() = 0
05:10:08.319941 brk(0) = 0x805e000
05:10:08.320248 brk(0x807f000) = 0x807f000
05:10:08.320558 getppid() = 8792
05:10:08.320867 stat64(/home/root, {st_mode=S_IFDIR|0700, st_size=4096, ...})
= 0
05:10:08.321207 stat64(., {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
05:10:08.321563 open(/etc/init.d/dbus, O_RDONLY) = 3
05:10:08.321868 fcntl64(3, F_DUPFD, 10) = 10
05:10:08.322125 close(3)= 0
05:10:08.322373 fcntl64(10, F_SETFD, FD_CLOEXEC) = 0
05:10:08.322636 rt_sigaction(SIGINT, NULL, {SIG_DFL}, 8) = 0
05:10:08.322907 rt_sigaction(SIGINT, {0x8055a20, ~[RTMIN RT_1], 0}, NULL, 8) = 0
05:10:08.330491 rt_sigaction(SIGQUIT, NULL, {SIG_DFL}, 8) = 0
05:10:08.330849 rt_sigaction(SIGQUIT, {SIG_DFL}, NULL, 8) = 0
05:10:08.331114 rt_sigaction(SIGTERM, NULL, {SIG_DFL}, 8) = 0
05:10:08.331375 rt_sigaction(SIGTERM, {SIG_DFL}, NULL, 8) = 0
05:10:08.331669 read(10, #! /bin/sh\n### BEGIN INIT INFO\n#..., 8192) = 4312
05:10:08.332235 stat64(/usr/bin/dbus-daemon, {st_mode=S_IFREG|0755,
st_size=273972, ...}) = 0
05:10:08.332689 geteuid32() = 0
05:10:08.332972 open(/lib/lsb/init-functions, O_RDONLY) = 3
05:10:08.333274 fcntl64(3, F_DUPFD, 10) = 11
05:10:08.333523 close(3)= 0
05:10:08.333767 fcntl64(11, F_SETFD, FD_CLOEXEC) = 0
05:10:08.334034 read(11, # /lib/lsb/init-functions for De..., 8192) = 8021
05:10:08.335468 stat64(/etc/lsb-base-logging.sh, {st_mode=S_IFREG|0644,
st_size=3820, ...}) = 0
05:10:08.335951 open(/etc/lsb-base-logging.sh, O_RDONLY) = 3
05:10:08.336251 fcntl64(3, F_DUPFD, 10) = 12
05:10:08.336504 close(3)= 0
05:10:08.336750 fcntl64(12, F_SETFD, FD_CLOEXEC) = 0
05:10:08.337022 read(12, # Default init script logging fu..., 8192) = 3820
05:10:08.346337 read(12, , 8192) = 0
05:10:08.347061 close(12) = 0
05:10:08.347226 read(11, , 8192) = 0
05:10:08.347361 close(11) = 0
05:10:08.347565 stat64(/etc/default/dbus, {st_mode=S_IFREG|0644, st_size=377,
...}) = 0
05:10:08.347841 open(/etc/default/dbus, O_RDONLY) = 3
05:10:08.348063 fcntl64(3, F_DUPFD, 10) = 11
05:10:08.348195 close(3)= 0
05:10:08.348322 fcntl64(11, F_SETFD, FD_CLOEXEC) = 0
05:10:08.348457 read(11, # This is a configuration file f..., 8192) = 377
05:10:08.348664 read(11, , 8192) = 0
05:10:08.348800 close(11) = 0
05:10:08.349470 fcntl64(1, F_DUPFD, 10) = 11
05:10:08.349620 close(1)= 0
05:10:08.349746 fcntl64(11, F_SETFD, FD_CLOEXEC) = 0
05:10:08.349879 dup2(2, 1) = 1
05:10:08.350024 write(1, Usage: /etc/init.d/dbus {start|s..., 65Usage:
/etc/init.d/dbus {start|stop|reload|restart|force-reload}
) = 65
05:10:08.350202 dup2(11, 1) = 1
05:10:08.350325 close(11) = 0
05:10:08.350489 exit_group(2) = ?
Process 8794 detached
[EMAIL
[Bug 25931] Re: Failed to initalize HAL.
** Tags added: qa-hardy-desktop ** Tags removed: qa-hardy-list -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I just reinstalled Hardy A4 after struggling an effort to recover broken packages dbus and hal without success. Sorry but now I can't give any more feedbacks to solve this bug. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
When I try to reinstall dbus and hal I got the following errors ... ** Attachment added: dbus_hal_install http://launchpadlibrarian.net/11890209/dbus_install.txt -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
[EMAIL PROTECTED]:~$ sudo dpkg-reconfigure dbus /usr/sbin/dpkg-reconfigure: dbus está quebrado ou não completamente instalado [EMAIL PROTECTED]:~$ sudo dpkg-reconfigure hal /usr/sbin/dpkg-reconfigure: hal está quebrado ou não completamente instalado [EMAIL PROTECTED]:~$ ** Attachment added: dmesg http://launchpadlibrarian.net/11890584/dmesg.txt -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I would like to know how to change message bus to start from /var/run/dbus instead of /usr/local/var/run/dbus [EMAIL PROTECTED]:/etc/init.d$ sudo dbus-daemon --system Failed to start message bus: Failed to bind socket /usr/local/var/run/dbus/system_bus_socket: No such file or directory [EMAIL PROTECTED]:/etc/init.d$ Dbus and Hal are broken and I can't reinstall them because dependency problems with hwdb-client-common and hwdb-client-gnome -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
After last GDM upgrade (version 2.20.3-0ubuntu3) on Hardy Alpha 4 I got this error on a Compaq Proliant 400 with AGP video card ATI Rage 3D. Tried to reinstall or downgrade Hal to a prior version was impossible due to dependency issues. Packages with dependency related are: gnome-mount gnome-power-manager gnome-volume-manager hwdb-client-common hwdb-client-gnome network-manager network-manager-gnome sound-juicer ubuntu-desktop update-notifier -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I had exactly the same after few weeks of use of a fresh Gutsy install, with apparently no reason. I tried everything listed here and elsewhere: - concurrency set to none (this never changed) - reordered /etc/rc2.d/ levels (S12dbus and S13hal) - installed/reinstalled packages - reconfigured all packages but still dbus was up, hald refused to start. Then I checked: less /etc/default/hal and output was DAEMON_OPTS= Then I changed it with: sudo nano /etc/default/hal into: DAEMON_OPTS=--retain-privileges then save, and rebooted. I'm not sure if the above tried procedures were somehow useful or just wasted time, but the problem is now solved. Hope this helps. -E- -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I encountered this error on a Debian Etch installation on a MacBook, dist upgrading to the Testing version. * Reloading system message bus config... Failed to open connection to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory invoke-rc.d: initscript dbus, action force-reload failed. Repeated retries at apt-get dist-upgrade failed with the same error until I manually restarted dbus by: /etc/init.d/dbus restart Then, the dist-upgrade worked fine. And the machine works as expected without any dbus/hal issues there after. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Another report for gutsy, with upstart concurrency enabled. I fixed this with mv /etc/rc2.d/S12hal /etc/rc2.d/S13hal. Is there any chance hal and dbus could have different startup numbers for hardy? -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Another report for gutsy, with upstart concurrency enabled. I fixed this with mv /etc/rc2.d/S12hal /etc/rc2.d/S13hal. Is there any chance hal and dbus could have different startup numbers for hardy? -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I was able to fix this problem by installing all new updates. Because I was unable to use WLAN I had to do the following steps: 1. Boot from the Ubuntu CD 2. Connecto to your WLAN (i.e. make sure that you have an internet connection) 3. Mount your linux partition (on my computer it got mounted at /media/disk) 4. Open the terminal 5. Do binding mounts sudo mount --bind /dev /media/disk/dev sudo mount --bind /proc /media/disk/proc sudo mount --bind /sys /media/disk/sys 6. chroot into your linux sudo chroot /media/disk 7. Update your system apt-get update apt-get dist-upgrade 8. Reboot Now your system should be alive again. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
worked thanks but what is the fix -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I also got the HAL notification after changing my concurrency to 'shell', renamed of S12hal to S13hal was all I needed to do. AMD turion dual @1.6 MHz. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
wups, make that Ghz -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I too have the same problem Kubuntu Hardy 2.6.24-4 kernel my error as follows on apt-get upgrade... Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. After this operation, 0B of additional disk space will be used. Setting up hal (0.5.10-5ubuntu5) ... * Reloading system message bus config... Failed to open connection to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory invoke-rc.d: initscript dbus, action force-reload failed. polkit-auth: This operation requires the system message bus and ConsoleKit to be running polkit-auth: AuthorizationAlreadyExists: An authorization for uid 107 for the action org.freedesktop.policykit.read with constraint '' already exists dpkg: error processing hal (--configure): subprocess post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of hwdb-client-common: hwdb-client-common depends on hal; however: Package hal is not configured yet. dpkg: error processing hwdb-client-common (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of hwdb-client-kde: hwdb-client-kde depends on hwdb-client-common; however: Package hwdb-client-common is not configured yet. dpkg: error processing hwdb-client-kde (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of kde-guidance-powermanager: kde-guidance-powermanager depends on hal; however: Package hal is not configured yet. dpkg: error processing kde-guidance-powermanager (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of kubuntu-desktop: kubuntu-desktop depends on hal; however: Package hal is not configured yet. kubuntu-desktop depends on hwdb-client-kde; however: Package hwdb-client-kde is not configured yet. dpkg: error processing kubuntu-desktop (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of network-manager: network-manager depends on hal (= 0.5.7.1); however: Package hal is not configured yet. dpkg: error processing network-manager (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of network-manager-kde: network-manager-kde depends on network-manager (= 0.6.2); however: Package network-manager is not configured yet. dpkg: error processing network-manager-kde (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: hal hwdb-client-common hwdb-client-kde kde-guidance-powermanager kubuntu-desktop network-manager network-manager-kde E: Sub-process /usr/bin/dpkg returned an error code (1) [EMAIL PROTECTED]:~# Hope this helps! Cary -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Moving the hal init.d script fixed it for me. I got the error on a newly installed 64bits Gutsy setup, after I changed the init rc setting to concurrency and changed gdm to autologin. The thing is, I didn't get the race condition with my old harddrive which is slower; I went from a WD raptor to a Mtron 7000 pro. That might be why the race is hard to reproduce. Some one should split this bug into more defined bug reports or something. I feel like there are atleast 3-4 other issues which causes the same error, which isn't all that related to the init.d boot order. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Correction; it does'nt matter if I have GDM autologin on or off. I still get the error if I turn on concurrent boot. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I have the same problem on same release. I'm running old Pentium-3 system. since then, no network. I'm not a Linux expert but lot of debugging experience. let me know what to check and I'll send the results. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I have the same problem. I attached the output of sudo hald --verbose=yes --daemon=no ** Attachment added: Output of hald while trying to start it manually http://launchpadlibrarian.net/11488257/err.log -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Same problem as Paul, on Macbook Pro 1st gen with Hardy alpha 3. Most of the proposed solutions didn't work. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Also started to happen for me after some updates in alpha 3. Bad thing is wireless no longer works, so no internet there. Didn't happen in fresh alpha 3 -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
Just did a fresh install of Hardy Alpha 3 everything was fine. Ran apt- get update and apt-get upgrade, rebooted and how have the same error. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I had the exact same problem as Paul Belanger, except I used aptitude update. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I had a clean install of Gutsy on an AMD 2800+. No problems. I then manually started tuning for boot speed and changed the /etc/init.d/rc file and made CONCURRENCY=shell. Upon reboot, I immediately received this issue. I did the ls -l /etc/rc?.d/*hal *dbus and they had a S12 (everything as it should be). I manually changed the rc file back and made CONCURRENCY=none. Upon reboot, I no longer experienced this problem. Just thought I would add this experience to the list in case someone has forgotten something they have tweaked and started getting this issue. I don't reboot often, so when I did get this, it took me a while to figure out what I had done. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I am running Hardy Heron with kernel 2.6.22-14-generic on an Dell Inspiron 6400 and having this problem since I installed kernel 2.6.24. Now it does not matter wich kernel I boot, I am getting the error message on my desktop. When starting hal on the command line there's no problem. If you would like to have information or logs, just ask. I will be glad to help. Peter -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
I just upgraded to Gutsy and am seeing this problem too. With all due appreciation for the benefits of free software (really!) I find it incredible that this bug has persisted through so many ubuntu releases, has been _refused_ for Gutsy, and that no Ubuntu developer has described a definitive and reliable workaround in this bug entry. -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25931] Re: Failed to initalize HAL.
** Tags added: qa-hardy-list -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
