Hugh, ok, so nothing unusual in your logs. This bug became horribly
complicated since all sorts of different bugs got amalgated into this
one, so let's clear up a bit.
This thread begun with hal-device-manager not starting, which was fixes
ages ago.
The hang due to having samba shares is already known as bug 44874. Folks
who have this problem, please have a look at that bug.
If anyone still has the problem of a non-existing 'haldaemon' user
(check that 'id haldaemon' prints an error), please file a new bug. It
works well when upgrading breezy to dapper, or installing dapper from
scratch here.
So let's devote this bug to the kernel oops produced by starting dbus, as shown
in
https://launchpad.net/distros/ubuntu/+source/dbus/+bug/31517/comments/33Hugh,
ok, so nothing unusual in your logs. This bug became horribly complicated since
all sorts of different bugs got amalgated into this one, so let's clear up a
bit.
This thread begun with hal-device-manager not starting, which was fixes
ages ago.
The hang due to having samba shares is already known as bug 44874. Folks
who have this problem, please have a look at that bug.
If anyone still has the problem of a non-existing 'haldaemon' user
(check that 'id haldaemon' prints an error), please file a new bug. It
works well when upgrading breezy to dapper, or installing dapper from
scratch here.
So let's devote this bug to the kernel oops produced by starting dbus,
as shown in http://librarian.launchpad.net/3851218/dbus.log
Kernel gurus, can you make some head and tail of the oops trace?
** Changed in: dbus (Ubuntu)
Sourcepackagename: dbus = linux-source-2.6.15
Assignee: Martin Pitt = (unassigned)
** Changed in: dbus (upstream)
Importance: Unknown = Untriaged
Bugwatch: Freedesktop Bugzilla #6059 = None
Status: Fix Released = Unconfirmed
** Changed in: dbus (upstream)
Status: Unconfirmed = Rejected
** Summary changed:
- dbus does not start
+ starting hal causes kernel oops in sysfs_get_target_path()
** Description changed:
- In dapper (current as of about 14:00 UTC 2006-02-15) the hal-device-
- manager will not load properly.
+ Starting hal produces a kernel oops as shown in
- If I attempt to load it from a terminal then I get something about a
- gtk.Menu and that's it.
+ http://librarian.launchpad.net/3851218/dbus.log
+
+ and hal fails to start.
--
starting hal causes kernel oops in sysfs_get_target_path()
https://launchpad.net/bugs/31517
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
