Failed to initialize HAL

Bug #106182 reported by Duso P
This bug report is a duplicate of:  Bug #25931: Failed to initalize HAL.. Edit Remove
2
Affects Status Importance Assigned to Milestone
hal (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Failed to initialize HAL

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. With which version of Ubuntu did you notice this issue? Some other things that would make your bug report more useful are the version of hal that you have installed (dpkg -l hal), when you received the error message, and if you have gotten the error message more than once. Thanks in advance.

Revision history for this message
Duso P (pikla) wrote : Re: [Bug 106182] Re: Failed to initialize HAL

Hi Brian,
my name is Julius,I'm novice in Linux. Thank you very
much for your interest.
I have Linux Mint (Bianca) installed on Compaq NX6110 notebook.
For the moment I dont know,where is possible to see the version
number of operating system installed in my computer. If is it important
information for you,can you help me,where is the information visible?
The version of installed HAL is 0.5.7.1-0ubuntu17. I see this information
in Synaptic.
Error message of HAL is visible on every system startup.

Thank you very much for your help.

Best regards,
Julius
<email address hidden>

Brian Murray wrote / napísal(a):
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. With which version of Ubuntu did you notice this issue? Some
> other things that would make your bug report more useful are the version
> of hal that you have installed (dpkg -l hal), when you received the
> error message, and if you have gotten the error message more than once.
> Thanks in advance.
>
> ** Changed in: Ubuntu
> Assignee: (unassigned) => Brian Murray
> Status: Unconfirmed => Needs Info
>
>

Revision history for this message
Brian Murray (brian-murray) wrote :

Executing the command 'cat /etc/lsb-release' should reveal the version of Ubuntu that you are using.

Revision history for this message
Duso P (pikla) wrote :

Hi Brian,
I have just checked the Ubuntu version by your instructions.
So,
distrib_id=Ubuntu
distrib_release=6.10
distrib_codename=edgy
distrib_description="Ubuntu 6.10"

Thank you very much. I'm waiting for next informations from you.
Best regards,
Julius

Brian Murray wrote / napísal(a):
> Executing the command 'cat /etc/lsb-release' should reveal the version
> of Ubuntu that you are using.
>
>

Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 106182] Failed to initialize HAL

Hi,

Duso P [2007-04-16 17:39 -0000]:
> Failed to initialize HAL

Can you please provide some more details? Which Ubuntu release are you
on? Does it happen every time, or just sometimes? Can you please give
me the output of

  dpkg -l hal
  ls -l /etc/rc*/*dbus

?

Thank you!

 status needsinfo

Changed in hal:
status: Confirmed → Needs Info
Revision history for this message
Martin Pitt (pitti) wrote : Fwd: Duso P Failed to initialize HAL

----- Forwarded message from Július Pikla <email address hidden> -----

X-Spam-Status: No, score=0.0 required=4.0 tests=BAYES_50 autolearn=no
 version=3.1.7-deb
Date: Tue, 17 Apr 2007 10:56:53 +0200
From: Július Pikla <email address hidden>
To: <email address hidden>, <email address hidden>
Subject: Duso P Failed to initialize HAL

Hi Martin,
here is my aswer for your request:

duso@duso-laptop:~$ dpkg -l hal |more

Požadovaný=Neznámy/Inštalovať/Odstrániť/Vyčistiť
| Stav=Nie/Inštalovaný/Konfig-súbory/Rozbalený/Zlý-konfig/Polo-inštalovaný
|/ Chyba?=(žiadna)/Podržať/Reinšt-vyžadovaná/X=oba-problémy (Stav,Chyba:
veľké písmeno=zle)
||/ Názov Verzia Popis
+++-==============-=================-============================================
ii hal 0.5.7.1-0ubuntu17 Hardware Abstraction Layer

duso@duso-laptop:~$ ls -l /etc/rc*/*dbus | more

lrwxrwxrwx 1 root root 14 2007-03-23 12:43 /etc/rc0.d/K20dbus ->
../init.d/dbus
lrwxrwxrwx 1 root root 14 2007-03-23 12:43 /etc/rc1.d/K20dbus ->
../init.d/dbus
lrwxrwxrwx 1 root root 14 2007-03-23 12:43 /etc/rc2.d/S20dbus ->
../init.d/dbus
lrwxrwxrwx 1 root root 14 2007-03-23 12:43 /etc/rc3.d/S20dbus ->
../init.d/dbus
lrwxrwxrwx 1 root root 14 2007-03-23 12:43 /etc/rc4.d/S20dbus ->
../init.d/dbus
lrwxrwxrwx 1 root root 14 2007-03-23 12:43 /etc/rc5.d/S20dbus ->
../init.d/dbus
lrwxrwxrwx 1 root root 14 2007-03-23 12:43 /etc/rc6.d/K20dbus ->
../init.d/dbus
duso@duso-laptop:~$

I am communicating this issue wit Brian Murray, I suppose, you know it.

Thank you very much for your interest.

Best regards,
Julius

<email address hidden>

----- End forwarded message -----

--
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org

Revision history for this message
Martin Pitt (pitti) wrote :

Thanks for your reply. This is fixed in Feisty, marking as duplicate.

Revision history for this message
jmrasor (jmrasor) wrote : Re: [Bug 106182] Re: Failed to initialize HAL

Dear Martin,

    I wonder if this bug is really fixed in Feisty. I got it after:

1. A clean install from the Feisty beta CD (no bug then)
2. Updates after that installation (got HAL bug)

John R

---------------------------------
Ahhh...imagining that irresistible "new car" smell?
 Check outnew cars at Yahoo! Autos.

Revision history for this message
Martin Pitt (pitti) wrote :

John,

> 1. A clean install from the Feisty beta CD (no bug then)
> 2. Updates after that installation (got HAL bug)

That means that you get /etc/rc2.d/S12dbus in a clean Feisty install, but they remain at S20dbus after an upgrade?

Revision history for this message
jmrasor (jmrasor) wrote :

Dear Martin,

    Thanks for your prompt reply.

Elbereth log No, I get the symbolic links correctly set at S12dbus both before and after the upgrade. That's in /etc/rc3.d, rc4.d, rc5.d. Running processes did include dbus-launch and dbus-daemon after the upgrade.

    Yucchy - poo... the upgrade was 349 new packages, so it'll be a bit of a hassle finding out which one did the dirty deed.

    I've got a few spare partitions, so I'm gonna do another install & upgrade, and let you know if anything significant comes up.

John R

= = = = = = = = = = = = = = = = =

Martin Pitt <email address hidden> wrote:
That means that you get /etc/rc2.d/S12dbus in a clean Feisty install,
but they remain at S20dbus after an upgrade?

---------------------------------
Ahhh...imagining that irresistible "new car" smell?
 Check outnew cars at Yahoo! Autos.

Revision history for this message
jmrasor (jmrasor) wrote :

Short story: I was not able to reproduce the bug.

Long story: I did a clean install from Feisty Desktop beta CD onto a spare partition, and did not see the HAL bug. Same as yesterday. I backed that installation up.
I did the 349 updates (from saved archives -- goes faster), and rebooted as directed: No HAL bug. Yesterday, I did get the HAL bug after the updates.
I restored from backup, repeated the upgrade: same, no HAL bug before or after upgrade.
I did a clean install from CD onto an entire spare disk: /var/run/dbus/pid and /var/run/dbus/system_bus_socket were there, with correct owners and permissions. The parent directory /var/run/dbus was correctly owned by messagebus:messagebus. This directory was totally missing after yesterday's install from CD. Yesterday, after I manually created it and reconfigured dbus:

sudo dbus-daemon –system
sudo dpkg-reconfigure hal

... then the HAL bug went away. But I never saw it again today.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for hal (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.