Discussion:
[Bug 25931] Failed to initalize HAL.
(too old to reply)
T. Wright
2006-03-13 05:05:32 UTC
Permalink
Public bug report changed:
https://launchpad.net/malone/bugs/25931

Comment:
Im having the same problem. My breezy was
a clean install. I ran the commands you listed
and these are the results

$ ps -p $(< /var/run/dbus/pid)
said the pid file was not found

pidof hald
just returned the command prompt

ls -l /etc/rc2.d/*dbus*
T. Wright
2006-03-13 05:09:28 UTC
Permalink
Public bug report changed:
https://launchpad.net/malone/bugs/25931

Comment:

ls -l /etc/rs2.d/*dbus* gave me this

lrwxrwxrwx 1 root 14 Mar 11 23:17 /ect/rc2.d
/s12dbus -> ../init.d/dbus

by the way this is from the post above.
Martin Pitt
2006-03-13 16:02:48 UTC
Permalink
Public bug report changed:
https://launchpad.net/malone/bugs/25931
/ect/rc2.d/s12dbus -> ../init.d/dbus
Is that indeed a small 's' before the 12? It should be a capital 'S'. Or
was this just a typo? (You can copy&paste from the terminal to the web
browser).

Can you please try this:

sudo /etc/init.d/dbus start
ps -p $(< /var/run/dbus/pid)
pidof hald

and copy&paste the outputs here? Thanks!
T. Wright
2006-03-26 06:03:06 UTC
Permalink
Public bug report changed:
https://launchpad.net/malone/bugs/25931

Comment:
***@TVOM:~# sudo /etc/init.d/dbus start
* Starting system message bus... [ ok ]
* Starting Hardware abstraction layer: [ ok ]
***@TVOM:~# ps -p $(< /var/run/dbus/pid)
PID TTY TIME CMD
8153 ? 00:00:00 dbus-daemon
***@TVOM:~# pidof hald
8166
***@TVOM:~#
Martin Pitt
2006-03-28 11:17:39 UTC
Permalink
Public bug report changed:
https://launchpad.net/malone/bugs/25931
/ect/rc2.d/s12dbus -> ../init.d/dbus
Is that indeed a small 's' before the 12? It should be a capital 'S'. Or was this just a typo? (You can
copy&paste from the terminal to the web browser).
If that's indeed a lower-case 's', then this would explain why dbus is not running (but I have no idea why it should be a small s, unless you manually changed this).
Martin Pitt
2006-03-28 11:18:10 UTC
Permalink
Public bug report changed:
https://launchpad.net/malone/bugs/25931

Task: ubuntu
Sourcepackagename: None => dbus
T. Wright
2006-03-31 00:47:06 UTC
Permalink
I looked in /etc/rc2.d and indeed the small s was a typo.

I read S12dbus.

The problem with hal started the first time the system started after the system install.
--
Failed to initalize HAL.
https://launchpad.net/malone/bugs/25931
Martin Pitt
2006-04-28 13:20:23 UTC
Permalink
Maybe it is an upgrade problem. Do you encounter this if you install a
clean dapper from scratch?
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
SEAQ - Andres Mujica
2006-09-30 21:14:25 UTC
Permalink
i having this issue i believe this is related somwhow with this bug
report

https://launchpad.net/distros/ubuntu/+source/libpam-
foreground/+bug/58165

this is the output from my system

sudo /etc/init.d/dbus start
Password:
* Starting system message bus dbus /etc/init.d/dbus: line 38: 6906 Fallo de segmentación start-stop-daemon --start --quiet --pidfile $PIDFILE --user $DAEMONUSER --exec $DAEMON -- --system $PARAMS


dbus is not running, so i'm having the failed to initialize HAL message.

this systems is an upgrade from breezy.
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
--
desktop-bugs mailing list
desktop-***@lists.ubuntu.com
https://list
SEAQ - Andres Mujica
2006-09-30 23:11:31 UTC
Permalink
i hope this helps to found this issue.


to be honest is truly hard to use a system with this trouble.

you cannot easily access cd nor usb pens,

i cannot believe it but mounting like the old days is really boring...

i would like to give this bug more priority.

please tell me how can i help to solve this issue

** Attachment added: "strace for dbus starting fine"
http://librarian.launchpad.net/4564613/dbus-start-ok
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
SEAQ - Andres Mujica
2006-09-30 23:08:59 UTC
Permalink
i'm attaching an strace from

dbus-daemon --system

in a good system (without the problem)

and another one from a bad system

in this there's a segmentation fault message


** Attachment added: "strace for dbus with segmentation fault"
http://librarian.launchpad.net/4564605/dbus-start-bad
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
Maxim Grechkin
2006-10-03 14:36:46 UTC
Permalink
I can confirm it too in edgy. If I login just after it is possible all
goes ok. But if I wait for some time I get such problem. On dapper I had
this problem too.
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
Martin Pitt
2006-10-06 13:58:53 UTC
Permalink
** Bug 62736 has been marked a duplicate of this bug
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
Sebastian Dröge
2006-11-13 06:22:29 UTC
Permalink
Instead of running dbus with strace could you please run dbus with gdb,
get it to segfault and attach the backtrace to this bugreport?
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
greymaiden
2006-11-13 06:30:09 UTC
Permalink
Please note: I have changed my e-mail address.

Please forward a copy of your message to greymaiden-***@public.gmane.org and update
your contacts.

This e-mail account will be closed in 90 days.

--------------------


Original Message:


X-Originating-IP: [82.211.81.139]
Return-Path: <bounces-Z7WLFzj8eWMS+***@public.gmane.org>
Authentication-Results: mta132.mail.re4.yahoo.com from=canonical.com; domainkeys=neutral (no sig)
Received: from 82.211.81.139 (EHLO adelie.ubuntu.com) (82.211.81.139)
by mta132.mail.re4.yahoo.com with SMTP; Sun, 12 Nov 2006 22:30:08 -0800
Received: from gangotri.ubuntu.com ([82.211.81.179])
by adelie.ubuntu.com with esmtp (Exim 4.60 #1 (Debian))
id 1GjVKa-0006OQ-5h
for <greymaiden-/***@public.gmane.org>; Mon, 13 Nov 2006 06:30:08 +0000
Received: from gangotri.ubuntu.com (localhost.localdomain [127.0.0.1])
by gangotri.ubuntu.com (Postfix) with ESMTP id 1EEF5318915
for <greymaiden-/***@public.gmane.org>; Mon, 13 Nov 2006 06:30:08 +0000 (GMT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: =?utf-8?q?Sebastian_Dr=C3=B6ge?= <slomo-Rt2hAepTLN8V/***@public.gmane.org>
Reply-To
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
satkata
2006-11-16 10:53:03 UTC
Permalink
Hi,

I have upgraded from Dapper to Edgy before a month or so and everything was running smoothly till week ago. When I am logging into Ubuntu, I got the same message as above described "Failed to initialize HAL". The Problem seems to be, that dbus is not being starting properly or at the right time ???. I checked all syslinks under /etc/rc2.d/ and everything is fine.
I just saw in the above messages though that others have 'dbus' with starting number 12
(/etc/rc2.d/S12dbus), but on my laptop it is 50 (/etc/rc2.d/S50dbus).

When I logout and switch to terminal console and run:
'sudo /etc/init.d/dbus start', it says that dbus is being already started.

Running:
'sudo /etc/ini.d/dbus restart' and then logging in again fixes everything.

Should i change that starting sequence number, but then why now.? It was
starting fine till week ago, and i haven't changed anything under the
system startup levels.

If you need any other information that can help you, just say, because I
have no idea. It's very strange.
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
Bordiga Giacomo
2007-01-19 18:59:20 UTC
Permalink
I confirm the existence of this bug in edgy. I notice it, after setting
the automatic startup login. Changing the priority number of the init
script to 12 resolves the problem.
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
greymaiden
2007-01-19 19:05:06 UTC
Permalink
Please note: I have changed my e-mail address.

Please forward a copy of your message to greymaiden-***@public.gmane.org and update
your contacts.

This e-mail account is no longer in use and I will not receive your
message.
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
mlind
2007-02-21 00:52:15 UTC
Permalink
I have this on Feisty sometimes. I think it's a race between hal/dbus
initializing and gnome desktop loading (apps that required dbus). When
I'm logged in to Gnome session and get the "Failed to initalize HAL"
error, I switch to tty1 and see that hal/dbus is still in middle of its
initialization-phase. Thanks to upstart and parallel start-up of init
scripts, my Ubuntu boots too fast for hal/dbus.
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
Martin Gustafsson
2007-02-24 16:24:56 UTC
Permalink
Have this bug in Feisty.
Receive three pop-up windows when logging to Gnome:

Power Manager.
HAL does not support power management!

Internal Error
failed to initialize HAL!

Power Manager
Either HAL or DBUS are not working

Running Ubuntu Feisty on a Via C3 laptop
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
greymaiden
2007-02-24 16:30:09 UTC
Permalink
Please note: I have changed my e-mail address.

Please forward a copy of your message to greymaiden-***@public.gmane.org and update
your contacts.

This e-mail account is no longer in use and I will not receive your
message.
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
Scott Bronson
2007-02-28 04:55:15 UTC
Permalink
Martin, I get this too when I have auto-login turned on in GDM. I get
the 3 error messages you mention, then hald leaks memory something
fierce (uses up all 3GB of my machine's memory in a few days).

When I turn off auto-login so I have to spend a few tens of seconds in
GDM before Gnome fires up, everything starts up without errors. I'm not
sure about the hald memory leak since I only just now figured out this
workaround.

Hopefully this will be fixed as Upstart matures.
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
Martin Pitt
2007-03-08 12:18:44 UTC
Permalink
dbus init.d priority needs to be set to 12, not 20, to avoid race
condition with gdm.

** Changed in: dbus (Ubuntu)
Status: Needs Info => In Progress
Target: None => ubuntu-7.04

** Changed in: dbus (Ubuntu)
Importance: Medium => High
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
Martin Pitt
2007-03-08 12:58:32 UTC
Permalink
dbus (1.0.2-1ubuntu3) feisty; urgency=low
.
* debian/rules: Start dbus at runlevel priority 12, so that it comes before
gdm. This eliminates the race condition of starting the X session before
hal is running. (LP: #25931 and two handfuls of dups)
* debian/dbus.postinst: Migrate rc?.d symlinks from 20 to 12 on upgrades to
this version.
* debian/control: Set Ubuntu maintainer.
* debian/rules: Clean up doc/*.html (they are generated from XML sources).


** Changed in: dbus (Ubuntu)
Status: In Progress => Fix Released
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
deuce
2007-03-11 14:11:16 UTC
Permalink
I filled a bug report about a similar problem, and I was forwarded here as my problem appeared to be similar and that I could find help here, but I cant!
The only thing I understood is to print here these:

***@flaptop:~$ sudo /etc/init.d/dbus start
Password:
* system message bus already started; not starting.
* Starting system message bus dbus ***@flaptop:~$ ps -p $(< /var/run/dbus/pid)
PID TTY TIME CMD
6108 ? 00:00:00 dbus-daemon
***@flaptop:~$ pidof hald
6123
***@flaptop:~$ ls -l /etc/rc2.d/*dbus*

lrwxrwxrwx 1 root root 14 2007-03-07 16:57 /etc/rc2.d/S20dbus ->
../init.d/dbus

Can someone help? I cant access my external HD and I have a project
due:( Thanks!
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
deuce
2007-03-11 15:36:54 UTC
Permalink
I've tried some of your solutions described here and now I cant even
login to gnome. I put my username and password and then it restarts the
session without login in. HELP!!!
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
Martin Pitt
2007-03-12 07:00:49 UTC
Permalink
deuce, if 'dbus start' fails that way, then it is already running. The
easiest workaround is to just wait for some seconds at the login screen
before logging in. The correct way is to rename /etc/rc2.d/S20dbus to
/etc/rc2.d/S12dbus (this was recently done in Feisty).

If it does not even log in, please get .xsession-errors from your home
directory and attach it here (you can log in on a text console after
pressing Ctrl+Alt+F1).
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
deuce
2007-03-13 00:25:32 UTC
Permalink
how can I do that?
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
Martin Pitt
2007-03-13 07:11:22 UTC
Permalink
Post by deuce
how can I do that?
In a terminal with 'sudo mv /etc/rc2.d/S20dbus /etc/rc2.d/S12dbus'.
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
roberto
2007-03-13 09:14:32 UTC
Permalink
I am following this as I am having the same problems. I have checked the
/etc/rc2.d folder and I don't have a S20dbus file, no dbus file in that
folder at all.

I do have an @20dsub file in the /rc3.d folder I changed this to S12dbus
with on effect.

This problem is getting to the stage where I might just reinstall
Windows, much as I don't want to do that. aghhhhhhhh
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
Martin Pitt
2007-03-13 12:54:57 UTC
Permalink
Hi,
Post by roberto
I am following this as I am having the same problems. I have checked the
/etc/rc2.d folder and I don't have a S20dbus file, no dbus file in that
folder at all.
Please try

sudo ln -s ../init.d/dbus /etc/rc2.d/S12dbus
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
roberto
2007-03-13 20:29:34 UTC
Permalink
I have solved my problem. I copied the S20dbus file from /etc/rc3.d
folder to /etc/rc2.d folder and renamed it to S12dbus and I now log in
with no Hal error and my thumb rive working fine.

Hope this helps someone else.
--
Failed to initalize HAL.
https://launchpad.net/bugs/25931
Aktiwers
2007-04-20 01:52:29 UTC
Permalink
Got the same error.

Internal error

failed to initialize HAL!


Im on Feisty.. I dont have a S20dBus file in my /etc/rc3.d only a S12DBUS.
And nothing dbus in my /etc/rc2.d

Any fix for this?
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
jmrasor
2007-04-23 17:31:22 UTC
Permalink
Aktiwers,

Quick way to see what runlevels have dbus set up:

# locate S??dbus

I ran into this HAL bug not long ago, and found that re-configuring HAL
got rid of it. Short story: make sure /var/run/dbus exists, and is owned
by messagebus:messagebus. You can make that directory and chown it over
to the proper owner:group if it does not exist. Then do

# sudo dbus-daemon --system
# sudo dpkg-reconfigure hal

Long story: same thing, but with more gory details, in my post to bug
#81670.

HTH.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Aktiwers
2007-05-09 01:47:36 UTC
Permalink
Hi jmrasor,

Thanks for the reply.

***@HAL:~$ locate S??dbus
/etc/rc4.d/S12dbus
/etc/rc3.d/S12dbus
/etc/rc5.d/S12dbus
***@HAL:~$

***@HAL:~$ sudo dbus-daemon --system
Failed to start message bus: Failed to bind socket "/var/run/dbus/system_bus_socket": No such file or directory
***@HAL:~$

***@HAL:~$ sudo dpkg-reconfigure hal
* 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.
* Starting Hardware abstraction layer hald
***@HAL:~$

Thats what happends.. and the error is still there.

Any Ideas?

Thanks!
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Torsten
2007-07-23 15:58:54 UTC
Permalink
Addition:

I set the status to incomplete, because the bug is still there - the
proposed fix does not solve the issue (in all cases, as i think i've got
a new one).
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Torsten
2007-07-23 15:54:57 UTC
Permalink
I got a "new" addition to this.

If the user is taken from AD through pam_winbind, the same does happen.

User on local passwd file -> All ok.
Delete the user from passwd/shadow and take the one from AD -> Auth & Co does work but the HAL bug does happening.

I got no idea whats wrong - the same configuration does work on Gentoo
for example.

PS: Did post this in a duplicate, sorry - ignore it there, this is the
bug for the problem.

** Changed in: dbus (Ubuntu)
Status: Fix Released => Incomplete
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
hindukush
2007-07-25 07:01:37 UTC
Permalink
Hi Guys,
I have the same problem aswell.
i get the following output
I also have a little red cross over the network icon that appears on the system tray, I think this has some connection with the HAL error.

***@ubuntu:~$ sudo /etc/init.d/dbus start
* system message bus already started; not starting.
* Starting system message bus dbus
***@ubuntu:~$ ps -p $(< /var/run/dbus/pid)
PID TTY TIME CMD
5758 ? 00:00:00 dbus-daemon
***@ubuntu:~$ pidof hald

(after typing the last command i.e pidof hald, i do not get any output,
just get the command prompt.

Please help me guys, this is veyyyy frustratingggggggggg
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Peter Enzerink
2007-08-22 23:30:12 UTC
Permalink
Summarising the workaround above by jmrasor, running the four commands
below then relogging fixes the problem temporarily. I have to do this on
every boot to get my USB attached harddrives to be recognised, which is
thankfully infrequent ;).

sudo mkdir /var/run/dbus
sudo chown messagebus:messagebus /var/run/dbus
sudo dbus-daemon --system
sudo dpkg-reconfigure hal
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Peter Enzerink
2007-08-22 23:40:02 UTC
Permalink
Yay! Thanks to this thread I've just noticed that /etc/rc2.d/S12dbus was
missing.

After copying it from /etc/rc3.d/S12dbus I no longer get this error on
my up to date Breezy->Feisty->Gutsy machine.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Torsten
2007-08-23 07:24:14 UTC
Permalink
I still have the error like mentioned above, although i tried all fixes
which are told here - no success yet. Peters "way" doesn't help either.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Alex Muntada
2007-09-08 20:17:29 UTC
Permalink
Can someone else review whether my fix solves their problems with hal?

** Changed in: dbus (Ubuntu)
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
Desktop Bugs, which is a direct subscriber.
Alex Muntada
2007-09-08 20:14:34 UTC
Permalink
/var/lib/dpkg/info/dbus.postinst assumes that old priorities were always
20:

# fix rc symlink priorities for upgrades from older versions
if [ "$1" = configure ] && dpkg --compare-versions "$2" lt-nl 1.0.2-1ubuntu3; then
echo "Fixing up startup script priorities..."
for l in 2 3 4 5; do
old=/etc/rc$l.d/S20dbus
new=/etc/rc$l.d/S12dbus
if [ -e $old ] && ! [ -e $new ]; then
mv $old $new
fi
done
fi

However, in my case the rc2.d priority was 50 (don't ask me why), so I
removed all the dbus symlinks:

localhost# update-rc.d -f dbus remove
Removing any system startup links for /etc/init.d/dbus ...
/etc/rc0.d/K20dbus
/etc/rc1.d/K20dbus
/etc/rc2.d/S50dbus
/etc/rc3.d/S12dbus
/etc/rc4.d/S12dbus
/etc/rc5.d/S12dbus
/etc/rc6.d/K20dbus

Then, I just remade them using the command from the last section of
dbus.postinst:

localhost# update-rc.d dbus multiuser 12 20
Adding system startup for /etc/init.d/dbus ...
/etc/rc1.d/K20dbus -> ../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

Then rebooted and now all the troubles about hal, dhcdbd, etc. are gone.

So I guess that dbus.postinst should not assume the old priority value.

HTH
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
pjohnson6
2007-09-10 06:14:36 UTC
Permalink
hi paul j here.

i am running gutsy tribe 5. my startup would run and then drop into text
mode at Starting system tools backends system tools backends. machine
would then hang for 2-3 minutes gdm would start and as soon as desktop
loaded Failed to initialize HAL. i looked around and found dbus and hal
starting as S12dbus and S12hal in /etc/rc2.d/. i also saw in upstart
info that hal is dependent on dbus so i changed hal to S13hal and gdm to
S14gdm in /etc/rc2.d/ by deleting links and relinking. everything is
fine now. i dont know if this helpful or correct. i hope it is helpful
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Tim Davis
2007-09-13 14:42:56 UTC
Permalink
I did an upgrade from Feisty to Gutsy Tribe 5, my installation is
actually through WABI. Alex, your fix didn't work on my installation and
neither did Paul's. I'm still getting hald not started.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Tim Davis
2007-09-13 15:21:57 UTC
Permalink
Checking the systems logs I see:
***@ubuntu:/var/log$ tail syslog Sep 13 11:06:07 ubuntu hald[6990]: 11:06:07.838 [I] hald_dbus.c:4807:
local server is listening at
unix:abstract=/var/run/hald/dbus-CEFHnlshb0,guid=49f595eaaa554420a5c33c0046e951df
Sep 13 11:06:07 ubuntu hald[6990]: 11:06:07.888 [I] hald_runner.c:299:
Runner has pid 6991
Sep 13 11:06:07 ubuntu hald[6990]: 11:06:07.889 [W] ci-tracker.c:200:
Could not get uid for connection:
org.freedesktop.DBus.Error.NameHasNoOwner Could not get UID of name
'org.freedesktop.DBus': no such name
Sep 13 11:06:07 ubuntu hald[6990]: 11:06:07.889 [E] hald_dbus.c:4462:
Cannot get caller info for org.freedesktop.DBus Sep 13 11:06:07 ubuntu hald[6990]: 11:06:07.892 [I] hald_runner.c:180:
runner connection is 0x8094ac8
Sep 13 11:06:07 ubuntu hald[6990]: 11:06:07.894 [I] mmap_cache.c:161:
Regenerating fdi cache..
Sep 13 11:06:17 ubuntu hald[6990]: 11:06:17.901 [I] mmap_cache.c:137: In regen_cache_cb exit_type=1, return_code=0 Sep 13 11:06:17 ubuntu hald[6990]: 11:06:17.902 [E] mmap_cache.c:190:
fdi cache regeneration failed!
Sep 13 11:06:17 ubuntu hald[6990]: 11:06:17.902 [I] mmap_cache.c:193:
fdi cache generation done
Sep 13 11:06:17 ubuntu hald[6990]: 11:06:17.902 [I] mmap_cache.c:251:
cache mtime is 1189629072
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Jean du Plessis
2007-09-21 08:02:26 UTC
Permalink
Just wanted to say I had the exact same problem as paul j and his
solution worked for me.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Vikrant
2007-09-29 07:46:31 UTC
Permalink
Same here , somehow(??!!) rc2.d,dbus priority was 50 on a feisty to gutsy beta.
Renaming it to S20dbus works for now ..
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
drumour
2007-09-29 10:18:39 UTC
Permalink
seemed to get same hal failure after large (100mb+) gutsy beta upgrade
today 29/9/07. Seems that reverting CONCURRENCY in /etc/init.d/rc back
to none from shell solved this for me
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Alex Muntada
2007-09-29 12:56:50 UTC
Permalink
Tim and other still suffering this, could you please check current
priorities of dbus, hal and dhcdbd? These are mine:

$ 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

$ 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

$ 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
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Gelke
2007-10-01 15:06:31 UTC
Permalink
drumour wrote on 2007-09-29: (permalink)

seemed to get same hal failure after large (100mb+) gutsy beta upgrade
today 29/9/07. Seems that reverting CONCURRENCY in /etc/init.d/rc back
to none from shell solved this for me.

I can confirm that this works. I had the same problem.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Martin Pitt
2007-10-01 15:27:01 UTC
Permalink
Do you guys use automatix, envy, or any other third-party application
that modifies Ubuntu in a global way? Priority 50 has never been a
default in Ubuntu proper.

** Changed in: dbus (Ubuntu)
Status: New => Incomplete
Target: ubuntu-7.04 => None
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Alex Muntada
2007-10-01 17:09:59 UTC
Permalink
Martin, I never used any of those and I actually had /etc/rc2.d/S50dbus. See my previous comment above:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/25931/comments/41
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Yousef Reda
2007-10-03 23:30:00 UTC
Permalink
I was trying to install Ubuntu on a friend's laptop.

Off of the live cd, both Feisty and Gutsy Beta work just fine. Once I
installed either, though, after restarting it a couple times, this error
would pop up.............

Laptop is a Sony Vaio VGN-S260. I received similar results to Alex
Muntada... (these are just copied off of his)

$ ls -1 /etc/rc?.d/*hal
/etc/rc1.d/K20dbus
/etc/rc2.d/S12dbus
/etc/rc3.d/S12dbus
/etc/rc4.d/S12dbus
/etc/rc5.d/S12dbus

$ 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

Tried making it so that hal was after dbus, shifting gdm to 14 and hal
to 13.. to no avail.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Chris
2007-10-06 23:50:51 UTC
Permalink
Gelke wrote on 2007-10-01: (permalink)
Post by Gelke
drumour wrote on 2007-09-29: (permalink)
seemed to get same hal failure after large (100mb+) gutsy beta upgrade today 29/9/07. Seems that reverting CONCURRENCY in /etc/init.d/rc back to >>none from shell solved this for me.
I can confirm that this works. I had the same problem.
Resolved my 'Failed to initialize HAL' error in Gutsy Beta. Never would
have figured that one out myself, thanks!
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Kyle Weller
2007-10-07 04:56:12 UTC
Permalink
CONCURRENCY=shell in /etc/init.d/rc caused the problem for me, I had to
set it back to CONCURRENCY=none and my problem was solved for gutsy beta
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
professordes
2007-10-11 08:41:55 UTC
Permalink
I can confirm that CONCURRENCY=shell in /etc/init.d/rc gives me the hal
problem here too (and that CONCURRENCY=none sorts it out), this on a
Core 2 Duo machine.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
LCID Fire
2007-10-11 13:05:26 UTC
Permalink
I, too have this problem on a Core 2 Duo machine - although CONCURRENCY
/etc/init.d/rc is set to none.

BTW: I, too have a S50dbus rc entry.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
LCID Fire
2007-10-11 13:18:03 UTC
Permalink
I tried recreating the rc entries as mentioned by Alex (https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/25931/comments/41) and it works like a charm.
Muchos gracias :)
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
JoeLinux
2007-10-11 14:18:49 UTC
Permalink
I tried the same thing that LCID Fire did, then I changed
CONCURRENCY=none back to CONCURRENCY=shell in /etc/init.d/rc, and
rebooted, but I'm still getting 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
Desktop Bugs, which is a direct subscriber.
LCID Fire
2007-10-11 14:54:53 UTC
Permalink
As a quick note - my CONCURRENCY is still set to none - I didn't change
that.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Gladstone
2007-10-13 18:57:37 UTC
Permalink
CONCURRENCY=none seems to have fixed the problem here.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Ubuntu QA Tracker
2007-10-15 10:25:09 UTC
Permalink
** Tags added: iso-testing
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
dsk
2007-10-16 20:46:56 UTC
Permalink
okay I had the problem with failed to initial Hal at startup.

After reading many posts here is what i did to fix it:

in /etc/rc2.d/

I changed S12hal to S13hal using the following in terminal

'sudo mv /etc/rc2.d/S12hal /etc/rc2.d/S13hal'

This was a fresh install of Gutsy RC1 64bit.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Srik
2007-10-20 10:17:24 UTC
Permalink
Yesterday i upgraded to gutsy. On the first reboot i had no problem!!
This morning i had the HAL error!!

When i click on the off button, nothing happens... The network applet
say that there is no network connection but it's not true... Other disks
are not mounted...

I followed all the suggestions in this page with no results:

- CONCURRENCY in /etc/init.d/rc was just set to none...

- renamed S12hal to S13hal and S13gdm to S14gdm in /etc/rc2.d (i tried
renaming them even in /etc/rc(3,4,5).d)

- "sudo update-rc.d -f dbus remove" and then "sudo update-rc.d dbus
multiuser 12 20" as suggested by Alex Muntada
(https://bugs.launchpad.net/~alex.muntada)

I have a core 2 duo machine.

" ps -p $(< /var/run/dbus/pid)" give -->
PID TTY TIME CMD
4969 ? 00:00:00 dbus-daemon

"pidof hald" and then "ls -l /etc/rc2.d/*dbus*" give -->
lrwxrwxrwx 1 root root 14 2007-10-20 11:37 /etc/rc2.d/S12dbus -> ../init.d/dbus


These are the current priorities of dbus, hal and dhcdbd:

$ 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

$ ls -1 /etc/rc?.d/*hal
/etc/rc1.d/K16hal
/etc/rc2.d/S12hal
/etc/rc3.d/S12hal
/etc/rc4.d/S12hal
/etc/rc5.d/S12hal

$ 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
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Srik
2007-10-20 11:00:48 UTC
Permalink
By now the problem disappeared with the reinstallation of the package
"hal" using synaptic! :)
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
st33med
2007-10-20 16:35:31 UTC
Permalink
I can also confirm setting CONCURRENCY=none or 'none' fixes the problem.
Side effect is a slower boot. Something must be wrong with the kernel
internally because this happened after I upgraded to the most recent
kernel. How odd...

Does the Concurrency function refer to something inside the kernel?

I am running an Intel Core Duo 1.66 GHz on Gutsy Gibbon.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
LCID Fire
2007-10-20 18:10:22 UTC
Permalink
It seems like it is only affecting Intel Core Duo machines!?
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Aktiwers
2007-10-20 18:28:28 UTC
Permalink
No my machine has an AMD athlon 2800+
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
H.Evers
2007-10-20 20:36:23 UTC
Permalink
I had the problem with HAL after upgrade from 7.04 to Gutsy (7.10) two
days ago. I found the file /etc/rc2.d/S50dbus, and after renaming it to
S12dbus, the problem was solved.

Reinstallation of HAL using synaptic solved some problems (missing suspend to ram and suspend to disk in Shutdown-Menu, no start of System->Settings->gnome-power-preferences), but the error occured again after next reboot.
My first Upgrade to 7.10 was interrupted (missing free disk), perhaps this is the reason for S50dbus?
My machine is Intel Pentium3, 667 Mhz.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
vnevoa
2007-10-21 10:15:28 UTC
Permalink
Same problem here, after Feisty to Gutsy upgrade.
No NetworkManager, hald won't start, exit menu options take well over 1 minute to pop up.
See complete description here: http://ubuntuforums.org/showthread.php?t=583940
Reinstalling Hal and Dbus makes no difference.
Reordering init script links also makes no difference.
Changing CONCURRENCY around also makes no difference.
Gutsy's HAL just won't start...

AMD64 dual core
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
pescio
2007-10-22 12:00:21 UTC
Permalink
Same behaviour here.
I tried to uninstall/reinstall hal dbus but nothing.
Seems like anyway that if I boot ubuntu in rescue mode [single mode] I'm able to run and start dbus and hal.
This *does not* happen instead with normal boot.

Right now the steps I do to have my working gnome desktop are:
1. boot in rescue mode
2. at prompt # I give 'gdm'
3. slowly my gdm appears and I can login.

this is a pain anyway, it would be great if someone could fix the hal problem.
Thanks and regards.

I'm on a 'hp compaq d330 dt'.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
pescio
2007-10-25 13:31:12 UTC
Permalink
After booting in single mode I tried to give a `strace /etc/init.d/dbus
start` and after a few seconds it stops in a "wait4 (-1, " message.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
peard33
2007-10-26 08:10:17 UTC
Permalink
HAL error message gone for me after change concurrency back to none from
shell in /etc/init.d/rc .

I'm running Gusty on an Intel Core 2 Duo e6550.

I changed the concurrency setting after reading an article on the net
saying that chaning the setting would speed up Ubuntu, especially on
dual core machines...apparently, that's not the case?
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Kloudy
2007-10-27 11:35:52 UTC
Permalink
I am another "Failed to initialize HAL" Gutsy user. My computer is a
Dell Inspiron 600m laptop. 1G RAM, 80G HD. I had no problems in
Fiesty. Did a network upgrade to get Gutsy. WUBI originally used to
install Fiesty.

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.

System > Preferences > Hardware Information Unpopulated dialog opens for about 5 seconds then closes.
System > Preferences > Power Management No dialog ever opens.

Concurrency setting in /etc/init.d/rc is set to 'none'.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
st33med
2007-10-27 21:34:08 UTC
Permalink
I have a theory...

Does anybody have Compiz Fusion turned on? What type of installation
(git, stable, or default Gutsy CF)? Can you turn off Compiz fusion or
turn off the Dbus plugin manually?

Also to note, Network manager is not telling me via bubble that I am
connected.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
3-M
2007-10-27 23:46:04 UTC
Permalink
I get this too.

Concurrency is set to 'none'.

# ls -l /etc/rc?.d/*dbus
/etc/rc1.d/K20dbus
/etc/rc2.d/S12dbus
/etc/rc3.d/S12dbus
/etc/rc4.d/S12dbus
/etc/rc5.d/S12dbus

# ls -l /etc/rc?.d/*hal
/etc/rc1.d/K16hal
/etc/rc2.d/S13hal
/etc/rc3.d/S12hal
/etc/rc4.d/S12hal
/etc/rc5.d/S12hal

#ls -l /etc/rc?.d/*dhcdbd
/etc/rc0.d/K16dhcdbd
/etc/rc1.d/S24dhcdbd
/etc/rc2.d/S24dhcdbd
/etc/rc3.d/S24dhcdbd
/etc/rc4.d/S24dhcdbd
/etc/rc5.d/S24dhcdbd
/etc/rc6.d/K16dhcdbd

By running the following commands, I was able to then start GDM and log
in without getting the error:

/etc/init.d/dbus start
/etc/init.d/dhcdbd start
/etc/init.d/hal start

Note that if you try starting hal before dhcdbd, hal will not start
properly. Also, after starting dhcdbd, you will not be given another
prompt. Rather, you will just be given a blank line. You can still
start hal. Also, after starting hal, there is constant output (You are
not given another command prompt). You can still start gdm like you
normally would from the command line.

Is there any way to start these things automatically, so I don't have to
boot into the command line every time?
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Kloudy
2007-10-28 00:36:44 UTC
Permalink
oh my...
I disabled dbus in 'services' to try what st33med suggested. Now my permissions are removed and I can't try you suggestions. I also cannot get into 'services'.

Do you know how I can get 'services' to open again. I'm a newbee as you
can figure.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Kloudy
2007-10-28 00:51:48 UTC
Permalink
I reinstalled dbus. I can try your recommendations now.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Kloudy
2007-10-28 01:13:48 UTC
Permalink
I tried you suggestions. Below is what I got. I am the admin of this
system, but I don't have the permissions I guess.

***@ubuntu:~$ /etc/init.d/dbus start
open: Permission denied
* Removing stale PID file /var/run/dbus/pid.
rm: cannot remove `/var/run/dbus/pid': Permission denied
***@ubuntu:~$ /etc/init.d/dhcdbd start
open: Permission denied
* Starting DHCP D-Bus daemon dhcdbd open: Permission denied
[ OK ]
***@ubuntu:~$ /etc/init.d/hal start
open: Permission denied
* Can't start Hardware abstraction layer - detected chrooted sessio
***@ubuntu:~$
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
paul
2007-10-28 02:15:44 UTC
Permalink
Kloudy you probably have to use the sudo command like sudo
/etc/init.d/dbus start


By the way I have exactly the same problems and for me 3-M's suggestions did not work
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
vnevoa
2007-10-28 12:44:57 UTC
Permalink
Just adding the output of hald that I found in my syslog (when doing
"sudo hald --daemon=yes --verbose=yes --use-syslog"):

Oct 21 16:46:39 thechair hald[10155]: 16:46:39.371 [i] hald.c:529: hal 0.5.9.1
Oct 21 16:46:39 thechair hald[10155]: 16:46:39.371 [i] hald.c:538: Will daemonize
Oct 21 16:46:39 thechair hald[10155]: 16:46:39.371 [i] hald.c:539: Becoming a daemon
Oct 21 16:46:39 thechair hald[10156]: 16:46:39.373 [i] hald_dbus.c:4807: local server is listening at unix:abstract=/var/run/hald/dbus-GDedVsW496,guid=1369e3dc8d0263f932971c0047
1b745f
Oct 21 16:46:39 thechair hald[10156]: 16:46:39.377 [i] hald_runner.c:299: Runner has pid 10157
Oct 21 16:46:39 thechair hald[10156]: 16:46:39.378 [W] ci-tracker.c:200: Could not get uid for connection: org.freedesktop.DBus.Error.NameHasNoOwner Could not get UID of name 'org.freedesktop.DBus': no such name
Oct 21 16:46:40 thechair hald[10156]: 16:46:39.378 [E] hald_dbus.c:4462: Cannot get caller info for org.freedesktop.DBus
Oct 21 16:46:40 thechair hald[10156]: 16:46:39.380 [i] hald_runner.c:180: runner connection is 0x6536b0
Oct 21 16:46:40 thechair hald[10156]: 16:46:39.382 [i] mmap_cache.c:161: Regenerating fdi cache..
Oct 21 16:46:49 thechair hald[10156]: 16:46:49.388 [i] mmap_cache.c:137: In regen_cache_cb exit_type=1, return_code=0
Oct 21 16:46:49 thechair hald[10156]: 16:46:49.388 [E] mmap_cache.c:190: fdi cache regeneration failed!
Oct 21 16:46:49 thechair hald[10156]: 16:46:49.388 [i] mmap_cache.c:193: fdi cache generation done
Oct 21 16:46:49 thechair hald[10156]: 16:46:49.388 [i] mmap_cache.c:251: cache mtime is 1192868046

Notice the error messages?... related to DBUS, I think...
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
vnevoa
2007-10-28 13:48:56 UTC
Permalink
Good news, folks!
Got my system working!
Did "sudo mv /var/cache/hald/fdi-cache~ /var/cache/hald/fdi-cache" and restarted the PC, and now it looks alright!!!
See bug #139155 for more info.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
vnevoa
2007-10-28 14:01:27 UTC
Permalink
Actualy, the correct way to do it seems to be:
sudo /usr/lib/hal/hald-generate-fdi-cache
(see bug #146812)
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Kloudy
2007-10-28 18:55:21 UTC
Permalink
Got my HAL working even through a complete power down and restart!

Here are the steps I took. (All are included above in previous posts.)

Compared my /etc/rc2.d filenames to those posted above. My rc2.d was
S50dbus instead of S12dbus

sudo mv /etc/rc2.d/S50dbus /etc/rc2.d/S12dbus

sudo mv /var/cache/hald/fdi-cache~ /var/cache/hald/fdi-cache

Restarted PC and all seems fine.

I still have CONCURRENCY in /etc/init.d/rc set to none from shell. Does
anyone think I should change it to shell to get faster boot-up speed, or
will that hose up my HAL fixes again? I am not running a dual core
machine.

Thanks to all the posters for your help and file comparisions.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
pescio
2007-10-29 08:01:30 UTC
Permalink
Hi,

I cannot have the system booting also giving '/usr/lib/hal/hald-generate-fdi-cache'.
It's dbus that doesn't start now... I attach a strace output.
If I boot normally I see the system blocked on a 'Starting dbus ...' of something like that.
I have to boot into rescue mode. Then at prompt 'strace /etc/init.d/dbus start' gives this the output in the attachment.
Is there some command to refresh the cache for dbus like for hald?

***@mybox:/etc/rc2.d# ls | sort
K08vmware
README
S05vbesave
S10acpid
S10powernowd.early
S10sysklogd
S12dbus
S13hal
S16openvpn
S16ssh


** Attachment added: "dbus strace log"
http://launchpadlibrarian.net/10203166/dbus_strace.log
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
nickless
2007-10-29 17:33:14 UTC
Permalink
Kloudy try using CONCURRENCY=shell and report if the HAL-Problem
reoccurs. I would be interested in the outcome :)
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Kloudy
2007-10-29 23:56:07 UTC
Permalink
I set the CONCURRENCY=shell and the HAL problem came back. rc2.d stayed at S12dbus this time, no S50dbus

Set CONCURRENCY=none, rebooted and HAL is working again.

The boot process is still slower than I remember in Feisty. I'll bet
there still is a tweek somewhere to fix the real problem.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Kloudy
2007-10-31 01:50:46 UTC
Permalink
Got my HAL working even with CONCURRENCY in /etc/init.d/rc set to shell.

Here are the steps I took. (All are included above in previous posts and
Bug #149881 link
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/149881 .)

Changed the CONCURRENCY setting by:

sudo gedit /etc/init.d/rc and editing CONCURRENCY=none to
CONCURRENCY=shell. Then saving.

Compared my /etc/rc2.d filenames to those posted above. My rc2.d was
S50dbus instead of S12dbus. Changed that by:

sudo mv /etc/rc2.d/S50dbus /etc/rc2.d/S12dbus

Saw in another thread that hal should be set to 13 so that it starts
after dbus is started. My HAL was 12. Fixed that by:

sudo mv /etc/rc2.d/S12hal /etc/rc2.d/13hal

Another post said to change the Hal cache. Did that by:

sudo mv /var/cache/hald/fdi-cache~ /var/cache/hald/fdi-cache

Restarted PC and all seems fine.

Thanks to the Ubuntu posters for your help. Gutsy still starts up
awlfully slow compared to Feisty.

Any other ideas are appreciated.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
pescio
2007-10-31 09:09:52 UTC
Permalink
Kloudy can you please post your `ls /etc/rc2.d | sort`? I'm wondering if
there's something missing on my box before dbus and hal starting..

thanks and regards
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Kloudy
2007-10-31 12:54:25 UTC
Permalink
Pescio, here is my ls /etc/rc2.d | sort :

README
S05vbesave
S10acpid
S10powernowd.early
S10sysklogd
S10xserver-xorg-input-wacom
S11klogd
S12dbus
S12sl-modem-daemon
S13gdm
S13hal
S19cupsys
S20apmd
S20apport
S20hotkey-setup
S20makedev
S20nvidia-kernel
S20powernowd
S20rsync
S22consolekit
S24avahi-daemon
S24dhcdbd
S89anacron
S89atd
S89cron
S90binfmt-support
S98usplash
S99acpi-support
S99laptop-mode
S99rc.local
S99rmnologin
S99stop-readahead
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
pescio
2007-10-31 15:58:23 UTC
Permalink
Good news guys, I fixed it!

Fixing the init scripts I saw that klogd was blocking the booting process. I googled for "starting kernel daemon" and came here
https://bugs.launchpad.net/ubuntu/+bug/150006

Simply changing something on ldap.conf solved my problem. I'm on a
ldap/AD managed lan.

Rebooted and voilà, the init process came to gdm.
I was wrongly thinking that it could be an hal/dbus problem because I removed the S11klogd script, which seemed to be bad.
Anyway thinking that it was a ldap timeout problem was really hard!

thanks.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing list
desktop-***@lists.ubuntu.com
https://l
st33med
2007-10-31 23:05:44 UTC
Permalink
That explains everything! I activated klogd (not knowing that it was
kernel log when I deactivated it O.o) and that problem came up. I will
try it later.

Thanks.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
nickless
2007-11-01 21:57:42 UTC
Permalink
Ok, I also got booting on Gutsy with CONCURRENCY=shell to work using
just

sudo mv /etc/rc2.d/S12hal /etc/rc2.d/S13hal
(Kloudy actually had a typo there moving "S12hal" to "13hal", which of course wouldn't work)
But shell didn't really speed up my boot. I still boot up in 25s, which isn't too bad either, but no improvement :)
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
tepe
2007-11-27 11:21:16 UTC
Permalink
This threat has been quiet for a while but I'm hoping there's still
people reading this.

I've got the same problem, obviously. This is what I've tried so far:

- CONCURRENCY in /etc/init.d/rc was and is set to none

- Renamed the S12hal to S13hal in /etc/rc2.d

- "sudo update-rc.d -f dbus remove" and then "sudo update-rc.d dbus
multiuser 12 20" as suggested by Alex Muntada
(https://bugs.launchpad.net/~alex.muntada)

- Reinstalled package "hal"

- Tried "sudo dbus-daemon –system" and then "sudo dpkg-reconfigure hal"

- "sudo mv /var/cache/hald/fdi-cache~ /var/cache/hald/fdi-cache" didn't
work since there was no "/var/cache/hald/fdi-cache~" so I did the " sudo
/usr/lib/hal/hald-generate-fdi-cache" instead

- Used the command "sudo sysv-rc-conf" and checked the taps for hal for
runlevels 2-5 as suggested in some other forum.

- I even added an endline to /etc/fstab as suggested in some other place

"ps -p $(< /var/run/dbus/pid)" gives ---->

PID TTY TIME CMD
4574 ? 00:00:00 dbus-daemon

Here are the current priorities of hal, dbus and dhcdbd

$ ls -1 /etc/rc?.d/*hal
/etc/rc1.d/K16hal
/etc/rc2.d/S13hal
/etc/rc3.d/S12hal
/etc/rc4.d/S12hal
/etc/rc5.d/S12hal

$ 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

$ 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
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing list
desktop-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
rafa
2007-12-04 11:24:22 UTC
Permalink
I also have the same problem. I do too the same things tape did in the
previous comment.

But when I tried

$ ls -1 /etc/rc?.d/*hal
ls: /etc/rc?.d/*hal: No such file or directory

$ 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

$ ls -1 /etc/rc?.d/*dhcdbd
ls: /etc/rc?.d/*dhcdbd: No such file or directory

Maybe there is something missing
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
tepe
2007-12-05 07:39:58 UTC
Permalink
I changed to older kernel and now it works fine. Except my Open Office
keeps freezing, but I expect this to be another bug.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
Henrik Nilsen Omma
2007-12-14 22:05:15 UTC
Permalink
** 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
Desktop Bugs, which is a direct subscriber.
DaveAbrahams
2007-12-17 00:11:24 UTC
Permalink
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
Desktop Bugs, which is a direct subscriber.
phoogkamer
2007-12-21 12:33:56 UTC
Permalink
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
Desktop Bugs, which is a direct subscriber.
Continue reading on narkive:
Loading...