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
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 -
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.
--
** 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
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
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.
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
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
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
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
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
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
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
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
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
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
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
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
** 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
** 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
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
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.
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:
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
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
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
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
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
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
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
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
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
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.
**
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
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
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
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,
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
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
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
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
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
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
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)
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
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
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
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.
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
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.
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.
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
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
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
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,
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'
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,
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
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
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
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
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,
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
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.
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
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
** 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
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
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 !
[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
[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
[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
[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
** 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
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
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
[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:
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
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
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
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
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
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
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
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
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,
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
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
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
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.
--
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
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
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.
--
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,
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
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
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
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
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
** 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
1 - 100 of 187 matches
Mail list logo
