Activity log for bug #25931

Date Who What changed Old value New value Message
2006-03-28 11:18:09 Martin Pitt None: statusexplanation Bugzilla status=NEEDINFO, product=Ubuntu, component=UNKNOWN
2006-09-30 23:08:59 Andres Mujica bug added attachment 'dbus-start-bad' (strace for dbus with segmentation fault)
2006-09-30 23:11:31 Andres Mujica bug added attachment 'dbus-start-ok' (strace for dbus starting fine)
2007-03-08 12:18:44 Martin Pitt dbus: status Needs Info In Progress
2007-03-08 12:18:44 Martin Pitt dbus: statusexplanation dbus init.d priority needs to be set to 12, not 20, to avoid race condition with gdm.
2007-03-08 12:22:51 Martin Pitt dbus: importance Medium High
2007-03-08 12:22:51 Martin Pitt dbus: statusexplanation dbus init.d priority needs to be set to 12, not 20, to avoid race condition with gdm.
2007-03-08 12:58:32 Martin Pitt dbus: status In Progress Fix Released
2007-03-08 12:58:32 Martin Pitt dbus: statusexplanation dbus (1.0.2-1ubuntu3) feisty; urgency=low . * debian/rules: Start dbus at runlevel priority 12, so that it comes before gdm. This eliminates the race condition of starting the X session before hal is running. (LP: #25931 and two handfuls of dups) * debian/dbus.postinst: Migrate rc?.d symlinks from 20 to 12 on upgrades to this version. * debian/control: Set Ubuntu maintainer. * debian/rules: Clean up doc/*.html (they are generated from XML sources).
2007-07-23 15:57:18 Torsten Krah dbus: status Fix Released Incomplete
2007-07-23 15:57:18 Torsten Krah dbus: statusexplanation dbus (1.0.2-1ubuntu3) feisty; urgency=low . * debian/rules: Start dbus at runlevel priority 12, so that it comes before gdm. This eliminates the race condition of starting the X session before hal is running. (LP: #25931 and two handfuls of dups) * debian/dbus.postinst: Migrate rc?.d symlinks from 20 to 12 on upgrades to this version. * debian/control: Set Ubuntu maintainer. * debian/rules: Clean up doc/*.html (they are generated from XML sources).
2007-09-08 20:17:29 Alex Muntada dbus: status Incomplete New
2007-10-01 15:27:01 Martin Pitt dbus: status New Incomplete
2007-10-29 08:01:30 Massimo Cora' bug added attachment 'dbus_strace.log' (dbus strace log)
2008-01-22 22:54:49 Mark Junker bug added attachment 'err.log' (Output of hald while trying to start it manually)
2008-02-12 11:21:44 mabovo bug added attachment 'dbus_install.txt' (dbus_hal_install)
2008-02-12 11:47:43 mabovo bug added attachment 'dmesg.txt' (dmesg)
2008-02-15 11:52:08 miked bug added attachment 'Screenshot.png' (screenshot of Error Message)
2008-02-18 01:27:42 miked dbus: status Incomplete New
2008-02-28 13:49:54 Martin Pitt dbus: status New In Progress
2008-02-28 13:50:12 Martin Pitt dbus: milestone ubuntu-8.04-beta
2008-02-28 15:07:50 Martin Pitt dbus: status In Progress Fix Committed
2008-02-29 08:35:06 Launchpad Janitor dbus: status Fix Committed Fix Released
2008-04-11 18:31:23 Bruce R bug added attachment 'PartialScreenshot-11apr2008.jpg' (PartialScreenshot-11apr2008.jpg)
2008-04-28 05:33:31 Martin Pitt dbus: status Fix Released In Progress
2008-04-28 05:33:31 Martin Pitt dbus: milestone ubuntu-8.04-beta ubuntu-8.04.1
2008-04-28 05:39:11 Martin Pitt description 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 continue to use the GUI for a few minutes, but eventually (especially when navigating the filesystem/CD-ROM,) the system hangs and I am forced to reboot. Though I am very new to Linux, I will help in the analysis in any way I can. 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 continue to use the GUI for a few minutes, but eventually (especially when navigating the filesystem/CD-ROM,) the system hangs and I am forced to reboot. Though I am very new to Linux, I will help in the analysis in any way I can. TEST CASE: - Set the rc.d symlinks to start level 12, to get to the situation many bug reporters end up with for some reason: sudo update-rc.d -f hal remove sudo update-rc.d hal start 12 2 3 4 5 . stop 12 1 - (optional, since racy): Set CONCURRENCY=shell in /etc/init.d/rc, boot, and watch hal fail to load - upgrade to the new hardy-proposed version (0.5.11~rc2-1ubuntu8), check that the rc symlinks are now at S24, and that the system boots properly with CONCURRENCY=shell.
2008-04-28 05:39:30 Martin Pitt dbus: status In Progress Fix Released
2008-04-28 05:39:30 Martin Pitt dbus: milestone ubuntu-8.04.1 ubuntu-8.04
2008-04-28 05:39:41 Martin Pitt bug assigned to hal (Ubuntu)
2008-04-28 05:40:35 Martin Pitt hal: importance Undecided High
2008-04-28 05:40:35 Martin Pitt hal: status New In Progress
2008-04-28 05:40:35 Martin Pitt hal: milestone ubuntu-8.04.1
2008-04-28 05:40:44 Martin Pitt hal: assignee pitti
2008-04-28 06:13:32 Martin Pitt bug added subscriber Ubuntu Stable Release Updates Team
2008-04-30 09:20:17 Martin Pitt hal: status In Progress Fix Committed
2008-04-30 09:20:17 Martin Pitt hal: milestone ubuntu-8.04.1
2008-04-30 09:21:37 Martin Pitt hal: status In Progress Fix Committed
2008-04-30 09:21:59 Martin Pitt bug added subscriber SRU Verification
2008-04-30 21:17:51 Brian Murray description 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 continue to use the GUI for a few minutes, but eventually (especially when navigating the filesystem/CD-ROM,) the system hangs and I am forced to reboot. Though I am very new to Linux, I will help in the analysis in any way I can. TEST CASE: - Set the rc.d symlinks to start level 12, to get to the situation many bug reporters end up with for some reason: sudo update-rc.d -f hal remove sudo update-rc.d hal start 12 2 3 4 5 . stop 12 1 - (optional, since racy): Set CONCURRENCY=shell in /etc/init.d/rc, boot, and watch hal fail to load - upgrade to the new hardy-proposed version (0.5.11~rc2-1ubuntu8), check that the rc symlinks are now at S24, and that the system boots properly with CONCURRENCY=shell. 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 continue to use the GUI for a few minutes, but eventually (especially when navigating the filesystem/CD-ROM,) the system hangs and I am forced to reboot. Though I am very new to Linux, I will help in the analysis in any way I can. TEST CASE: - Set the rc.d symlinks to start level 12, to get to the situation many bug reporters end up with for some reason: sudo update-rc.d -f hal remove sudo update-rc.d hal start 12 2 3 4 5 . stop 12 1 . - (optional, since racy): Set CONCURRENCY=shell in /etc/init.d/rc, boot, and watch hal fail to load - upgrade to the new hardy-proposed version (0.5.11~rc2-1ubuntu8), check that the rc symlinks are now at S24, and that the system boots properly with CONCURRENCY=shell.
2008-05-05 07:02:48 Martin Pitt hal: status Fix Committed Fix Released
2008-05-05 07:03:01 Martin Pitt hal: status Fix Committed Fix Released
2008-05-05 07:03:10 Martin Pitt hal: status Fix Released Fix Committed
2008-05-05 07:15:06 Launchpad Janitor hal: status Fix Committed Fix Released
2008-05-06 16:29:07 Thomas Hammerl bug added attachment 'hal.log' (hal.log)
2008-05-06 16:29:39 Thomas Hammerl bug added attachment 'lshal.txt' (lshal.txt)
2008-05-06 16:30:08 Thomas Hammerl bug added attachment 'kern.log' (kern.log)
2008-05-22 17:53:16 Jeremy Wilkins bug added attachment 'dmesg.log' (dmesg.log)
2009-05-25 09:38:07 CHANIYARA hal (Ubuntu): assignee Martin Pitt (pitti)
2009-05-25 12:04:51 Srik removed subscriber Srik
2009-12-05 17:12:33 Launchpad Janitor branch linked lp:ubuntu/dbus