The dbus postinst script is supposed to transition the dbus startup
script to S12 on upgrade, however it appears that for some systems this
is not the case if the system was upgraded from feisty->gutsy.
** Changed in: dbus (Ubuntu)
Sourcepackagename: None => dbus
** Summary changed:
- failed to
Hello,
tried the update-rc.d stuff but no joy for me the problem has been there
since install (amd64, tribes 5, alternative install)
I get these errors when I aptitude safe-upgrade, looks like the
postinstall script is borked some how will poke at it when I get the
chance and post my finding.
[E
I can confirm this bug on amd64 after upgrade (sudo update-manager -d) from
Feisty to Gutsy tribe 5.
I get this message every time on every boot after login.
Commands
$sudo update-rc.d -f dbus remove
$sudo update-rc.d dbus stop 20 0 . stop 20 1 . start 12 2 . start 12 3 . start
12 4 . start 12 5
Stevi,
I think that should work now (it works on my computer), so you can try
rebooting, but I'm not entirely sure what happens when 2 scripts have the same
priority.
If you want, move the hal script down the boot order (higher number=lower
priority) using the commands:
$sudo update-rc.d -f h
Thx. I followed your description but there's a S12dsbus AND a S12hald
symlink now!?!?
/etc/rc2.d$ ls
K74bluetooth S20apmd S30gdm
README S20hotkey-setup S89cron
S05vbesave S20makedevS95preload
S10acpid S
ok, I spent some time playing round so this isn't exactly what I did,
but I think it should work. In a terminal:
$sudo update-rc.d -f dbus remove
$sudo update-rc.d dbus stop 20 0 . stop 20 1 . start 12 2 . start 12 3 . start
12 4 . start 12 5 . start 20 6 .
The output of the second command shou
Could you give me a link or explain a little more detailed how to change
the boot process order with update-rc.d? Thx in advance.
--
failed to initialize HAL! (Gutsy 2007-07-18 i386)
https://bugs.launchpad.net/bugs/126810
You received this bug notification because you are a member of Ubuntu
Bugs,
I was seeing the same error every time on startup after I upgraded to Gutsy
tribe 5, plus a few extra things like the floppy drive wasn't being picked up.
I tried playing around with the boot process order, and found that having the
dbus daemon launch before hald made the warning disappear, but
>From time to time when I boot into Gutsy I get the same error (Failed to
initialize HAL!). Never had this error before on Edgy or Feisty. After
rebooting in most cases everything works fine!?!?
--
failed to initialize HAL! (Gutsy 2007-07-18 i386)
https://bugs.launchpad.net/bugs/126810
You receiv
[Gutsy] With latest update I get this error, as a warning dialog window,
on every boot after login...
HTH
--
failed to initialize HAL! (Gutsy 2007-07-18 i386)
https://bugs.launchpad.net/bugs/126810
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug conta
This error has disappeared for me with the tribe 4 release.
--
failed to initialize HAL! (Gutsy 2007-07-18 i386)
https://bugs.launchpad.net/bugs/126810
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
I can confirm it too, it happens since I upgraded yesterday.
And any sound is disappeared, I dont know if it is linked.
--
failed to initialize HAL! (Gutsy 2007-07-18 i386)
https://bugs.launchpad.net/bugs/126810
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can also confirm: I get this error when booting the live cd & hard
drive with tribe 3 i386. I dual boot with Vista Ultimate. Partitions:
NTFS, ext3, swap.
--
failed to initialize HAL! (Gutsy 2007-07-18 i386)
https://bugs.launchpad.net/bugs/126810
You received this bug notification because you a
does happen to me but I don't have NTFS drives, only ext3
--
failed to initialize HAL! (Gutsy 2007-07-18 i386)
https://bugs.launchpad.net/bugs/126810
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubun
And one weird thing, if I unplug/disconnect my IDE hard disk (formated
with NTFS, where WinXP is installed), I don't get this error. (I have 2
HDs, one IDE with XP/NTFS and one SATA with Ubuntu/Ext3/Fat32).
I need to unplug it to install Ubuntu (both Feisty and Gutsy), otherwise
the installation w
I can also confirm this bug on AMD64, gutsy-desktop-amd64.iso.
--
failed to initialize HAL! (Gutsy 2007-07-18 i386)
https://bugs.launchpad.net/bugs/126810
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I did not see this in Kubuntu. Don't know if that matters
--
failed to initialize HAL! (Gutsy 2007-07-18 i386)
https://bugs.launchpad.net/bugs/126810
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubu
confirming this as I can consistently get this dialog showing up at the
end of gnome's login on gutsy tribe3's liveCD.
** Changed in: Ubuntu
Status: New => Confirmed
--
failed to initialize HAL! (Gutsy 2007-07-18 i386)
https://bugs.launchpad.net/bugs/126810
You received this bug notificat
18 matches
Mail list logo
