Its working now. Sorry about that; I think I updated it before the
latest version had actually reached the repo. Thanks!
--
Latest update for hal on Karmic causes failure to start completely
https://bugs.launchpad.net/bugs/375169
You received this bug notification because you are a member of Ub
** Changed in: dbus (Ubuntu)
Status: Confirmed => Fix Released
--
Latest update for hal on Karmic causes failure to start completely
https://bugs.launchpad.net/bugs/375169
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
Out of frustration I ‘apt-get remove hal’ and reinstalled it. Now,
thanks to the ‘--background’-hack in /etc/init.d/hal at least the
computer boots. But since I removed hal, all the packages that depended
on it went as well, and the computer only boots to the command prompt -
not the desktop.
Any
The last update (1.2.14-2ubuntu5) fix it.
--
Latest update for hal on Karmic causes failure to start completely
https://bugs.launchpad.net/bugs/375169
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
This doesn't seem to fix it. I applied all the updates (in the failsafe
console, because HAL is necessary for Xorg to properly start), and hal
started once. I rejoiced, and rebooted the computer, but then it failed
again with exactly the same problem.
** Changed in: dbus (Ubuntu)
Status:
This bug was fixed in the package dbus - 1.2.14-2ubuntu4
---
dbus (1.2.14-2ubuntu4) karmic; urgency=low
* Refresh the previous patch set.
* debian/patches/50-timeout-01_null-for-pending-call.patch: Apply the
working version of the patch, the previous had code inside the if()
This is caused by a bug in the D-Bus timeout patches.
The HAL author was involved in the original discussions about those, so
had pre-empted the use of INT_MAX in pending call timeout arguments -
thus HAL was using code that had never been tested, since a version of
D-Bus that supported INT_MAX t
