After upgrade I get "Failed to Load HAL" - nothing works

Bug #215713 reported by clay3482
8
Affects Status Importance Assigned to Milestone
Mythbuntu
Incomplete
Undecided
Unassigned

Bug Description

Testing mythbuntu 8.04

Desktop - Gateway

Have been using it for about 16 months as a Myth setup

After using the automatic-update today I am getting a
"Failed to open HAL" command

Myth loads but there is nothing just the default blue screen - but no icons for the myth setup

I can exit myth and use the terminal and other things on the desktop however

Revision history for this message
Kees Cook (kees) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

Revision history for this message
Mario Limonciello (superm1) wrote :

Where does this Failed to open HAL popup?

Changed in mythbuntu:
status: New → Incomplete
Revision history for this message
Peter Schachte (schachte-csse) wrote :

I'm not the original poster, but I get the same error. The error appears as a popup on the xfce desktop screen after mythfrontend crashes (a separate problem), and everything that relies on HAL doesn't work, eg the network is down. This is after upgrade to kernel 2.6.24.15 and .16 (both do it). Selecting .14 (which I still have installed) from the boot menu avoids the problem.

I did some googling, and this error appears to be a common one caused by different things over the years. The latest explanation was that upstart now tries to boot things in parallel, and there's a race condition between HAL and dbus (as I recall). But I tried the suggested fix (to change the boot order forcing HAL to start after dbus), but it didn't help.

BTW, this is on an Athlon64 box, but I'm running the generic kernel, as that's what the 64 bit mythbuntu 8.04 beta installed.

Revision history for this message
Mario Limonciello (superm1) wrote : Re: [Bug 215713] Re: After upgrade I get "Failed to Load HAL" - nothing works
  • unnamed Edit (2.0 KiB, text/html; charset=ISO-8859-1)

Interesting bug. I've seen similar things filed in normal ol' Ubuntu I
believe. Can you post some logs from /var/log/, probably daemon.log, dmesg
and friends?

On Sat, Apr 12, 2008 at 11:21 AM, Peter Schachte <
<email address hidden>> wrote:

> I'm not the original poster, but I get the same error. The error
> appears as a popup on the xfce desktop screen after mythfrontend crashes
> (a separate problem), and everything that relies on HAL doesn't work, eg
> the network is down. This is after upgrade to kernel 2.6.24.15 and .16
> (both do it). Selecting .14 (which I still have installed) from the
> boot menu avoids the problem.
>
> I did some googling, and this error appears to be a common one caused by
> different things over the years. The latest explanation was that
> upstart now tries to boot things in parallel, and there's a race
> condition between HAL and dbus (as I recall). But I tried the suggested
> fix (to change the boot order forcing HAL to start after dbus), but it
> didn't help.
>
> BTW, this is on an Athlon64 box, but I'm running the generic kernel, as
> that's what the 64 bit mythbuntu 8.04 beta installed.
>
> --
> After upgrade I get "Failed to Load HAL" - nothing works
> https://bugs.launchpad.net/bugs/215713
> You received this bug notification because you are a member of
> Mythbuntu, which is a direct subscriber.
>

--
Mario Limonciello
<email address hidden>

Revision history for this message
Peter Schachte (schachte-csse) wrote :

Sure. I'm attaching dmesg, daemon.log, and messages from the moments after boot. Please let me know if you need anything else.

Revision history for this message
Peter Schachte (schachte-csse) wrote :
Revision history for this message
Peter Schachte (schachte-csse) wrote :
Revision history for this message
Mario Limonciello (superm1) wrote :

Ohhh this bug. I bet it's related to the cx88-alsa debacle that broke everything. This is already known about. I'll find the original and get you it.

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.