[Bug 106182] Re: Failed to initialize HAL
*** This bug is a duplicate of bug 25931 *** https://bugs.launchpad.net/bugs/25931 [Expired for hal (Ubuntu) because there has been no activity for 60 days.] -- Failed to initialize HAL https://bugs.launchpad.net/bugs/106182 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber (via bug 25931). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 106182] Re: Failed to initialize HAL
*** This bug is a duplicate of bug 25931 *** https://bugs.launchpad.net/bugs/25931 John, 1. A clean install from the Feisty beta CD (no bug then) 2. Updates after that installation (got HAL bug) That means that you get /etc/rc2.d/S12dbus in a clean Feisty install, but they remain at S20dbus after an upgrade? -- Failed to initialize HAL https://bugs.launchpad.net/bugs/106182 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber (via bug 25931). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 106182] Re: Failed to initialize HAL
*** This bug is a duplicate of bug 25931 *** https://bugs.launchpad.net/bugs/25931 Dear Martin, Thanks for your prompt reply. Elbereth log No, I get the symbolic links correctly set at S12dbus both before and after the upgrade. That's in /etc/rc3.d, rc4.d, rc5.d. Running processes did include dbus-launch and dbus-daemon after the upgrade. Yucchy - poo... the upgrade was 349 new packages, so it'll be a bit of a hassle finding out which one did the dirty deed. I've got a few spare partitions, so I'm gonna do another install upgrade, and let you know if anything significant comes up. John R = = = = = = = = = = = = = = = = = Martin Pitt [EMAIL PROTECTED] wrote: That means that you get /etc/rc2.d/S12dbus in a clean Feisty install, but they remain at S20dbus after an upgrade? - Ahhh...imagining that irresistible new car smell? Check outnew cars at Yahoo! Autos. -- Failed to initialize HAL https://bugs.launchpad.net/bugs/106182 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber (via bug 25931). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 106182] Re: Failed to initialize HAL
*** This bug is a duplicate of bug 25931 *** https://bugs.launchpad.net/bugs/25931 Short story: I was not able to reproduce the bug. Long story: I did a clean install from Feisty Desktop beta CD onto a spare partition, and did not see the HAL bug. Same as yesterday. I backed that installation up. I did the 349 updates (from saved archives -- goes faster), and rebooted as directed: No HAL bug. Yesterday, I did get the HAL bug after the updates. I restored from backup, repeated the upgrade: same, no HAL bug before or after upgrade. I did a clean install from CD onto an entire spare disk: /var/run/dbus/pid and /var/run/dbus/system_bus_socket were there, with correct owners and permissions. The parent directory /var/run/dbus was correctly owned by messagebus:messagebus. This directory was totally missing after yesterday's install from CD. Yesterday, after I manually created it and reconfigured dbus: sudo dbus-daemon –system sudo dpkg-reconfigure hal ... then the HAL bug went away. But I never saw it again today. -- Failed to initialize HAL https://bugs.launchpad.net/bugs/106182 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber (via bug 25931). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 106182] Re: Failed to initialize HAL
*** This bug is a duplicate of bug 25931 *** https://bugs.launchpad.net/bugs/25931 Thanks for your reply. This is fixed in Feisty, marking as duplicate. ** This bug has been marked a duplicate of bug 25931 Failed to initalize HAL. -- Failed to initialize HAL https://bugs.launchpad.net/bugs/106182 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for hal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 106182] Re: Failed to initialize HAL
*** This bug is a duplicate of bug 25931 *** https://bugs.launchpad.net/bugs/25931 Dear Martin, I wonder if this bug is really fixed in Feisty. I got it after: 1.A clean install from the Feisty beta CD (no bug then) 2.Updates after that installation (got HAL bug) John R - Ahhh...imagining that irresistible new car smell? Check outnew cars at Yahoo! Autos. -- Failed to initialize HAL https://bugs.launchpad.net/bugs/106182 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber (via bug 25931). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 106182] Re: Failed to initialize HAL
** Changed in: hal (Ubuntu) Sourcepackagename: None = hal Assignee: Brian Murray = (unassigned) Status: Needs Info = Confirmed -- Failed to initialize HAL https://bugs.launchpad.net/bugs/106182 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for hal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
