| 2006-02-15 15:17:46 |
Daniel Silverstone |
bug |
|
|
added bug |
| 2006-02-27 13:24:31 |
Martin Pitt |
hal: status |
Unconfirmed |
Confirmed |
|
| 2006-02-27 13:24:31 |
Martin Pitt |
hal: assignee |
|
pitti |
|
| 2006-02-27 13:24:31 |
Martin Pitt |
hal: statusexplanation |
|
|
|
| 2006-02-27 13:24:46 |
Martin Pitt |
bug |
|
|
assigned to hal (upstream) |
| 2006-02-27 13:25:50 |
Martin Pitt |
hal: statusexplanation |
|
Filed bug upstream.
AFAIK this is a deadlock between dbus and hal-device-manager waiting on each other until the request times out. |
|
| 2006-02-27 16:56:39 |
Martin Pitt |
hal: statusexplanation |
Filed bug upstream.
AFAIK this is a deadlock between dbus and hal-device-manager waiting on each other until the request times out. |
problem in the dbus python bindings |
|
| 2006-02-27 16:56:52 |
Martin Pitt |
hal: statusexplanation |
|
hal |
|
| 2006-03-03 10:23:16 |
Martin Pitt |
dbus: status |
Confirmed |
Fix Released |
|
| 2006-03-03 10:23:16 |
Martin Pitt |
dbus: statusexplanation |
hal |
dbus (0.60-6ubuntu4) dapper; urgency=low
.
* Add debian/patches/dbus-poll-hang.patch:
- Check to see if our data has already been read off the connection by
another blocking pending call before we block in poll.
(check_for_reply_and_update_dispatch_unlocked): Code taken from
_dbus_connection_block_pending_call - checks for an already read reply and
updates the dispatch if there is one.
- This fixes e. g. the long startup hang of hal-device-manager.
(Malone #31517)
- Patch taken from upstream CVS.
|
|
| 2006-03-03 10:23:34 |
Martin Pitt |
dbus: status |
Unconfirmed |
Fix Released |
|
| 2006-03-03 10:23:34 |
Martin Pitt |
dbus: statusexplanation |
problem in the dbus python bindings |
http://webcvs.freedesktop.org/dbus/dbus/dbus/dbus-connection.c?r1=1.115&r2=1.116&makepatch=1&diff_format=u |
|
| 2006-07-17 18:39:51 |
Slight Slightly |
dbus: status |
Fix Released |
Rejected |
|
| 2006-07-17 18:39:51 |
Slight Slightly |
dbus: statusexplanation |
dbus (0.60-6ubuntu4) dapper; urgency=low
.
* Add debian/patches/dbus-poll-hang.patch:
- Check to see if our data has already been read off the connection by
another blocking pending call before we block in poll.
(check_for_reply_and_update_dispatch_unlocked): Code taken from
_dbus_connection_block_pending_call - checks for an already read reply and
updates the dispatch if there is one.
- This fixes e. g. the long startup hang of hal-device-manager.
(Malone #31517)
- Patch taken from upstream CVS.
|
I've re-opened this bug as people are still having the same symptoms. I'm presuming I'm *allowed* to re-open the bug as launchpad is letting me.. Sorry if I've misunderstood. |
|
| 2006-07-17 18:40:47 |
Slight Slightly |
dbus: status |
Rejected |
Confirmed |
|
| 2006-07-17 18:40:47 |
Slight Slightly |
dbus: statusexplanation |
I've re-opened this bug as people are still having the same symptoms. I'm presuming I'm *allowed* to re-open the bug as launchpad is letting me.. Sorry if I've misunderstood. |
Wrong status :/
Incidentally the user fix (delete 'hal' user and re-install didn't work for me) |
|
| 2006-09-14 07:23:30 |
Martin Pitt |
title |
hal-device-manager does not load |
dbus does not start |
|
| 2006-09-14 22:40:06 |
Hugh |
bug |
|
|
added attachment 'debug.txt' (output of id hal, fstab etc) |
| 2006-09-15 07:48:09 |
Martin Pitt |
dbus: assignee |
pitti |
|
|
| 2006-09-15 07:48:09 |
Martin Pitt |
dbus: statusexplanation |
Wrong status :/
Incidentally the user fix (delete 'hal' user and re-install didn't work for me) |
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? |
|
| 2006-09-15 07:48:29 |
Martin Pitt |
dbus: status |
Unconfirmed |
Rejected |
|
| 2006-09-15 07:49:39 |
Martin Pitt |
description |
In dapper (current as of about 14:00 UTC 2006-02-15) the hal-device-manager will not load properly.
If I attempt to load it from a terminal then I get something about a gtk.Menu and that's it. |
Starting hal produces a kernel oops as shown in
http://librarian.launchpad.net/3851218/dbus.log
and hal fails to start. |
|
| 2006-09-15 07:49:39 |
Martin Pitt |
title |
dbus does not start |
starting hal causes kernel oops in sysfs_get_target_path() |
|
| 2008-08-28 16:31:41 |
Leann Ogasawara |
bug |
|
|
added subscriber Leann Ogasawara |
| 2008-11-13 22:10:42 |
Leann Ogasawara |
linux: status |
Confirmed |
Incomplete |
|
| 2008-11-13 22:10:42 |
Leann Ogasawara |
linux: statusexplanation |
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? |
This bug was reported a while ago and the last real comment made over 2 years ago. Please confirm if this is still an issue with the most recent Intrepid Ibex 8.10 release. Setting to Incomplete until we get further feedback. Thanks. |
|
| 2009-01-11 07:46:22 |
Javier Jardón |
linux: status |
Incomplete |
Invalid |
|
| 2009-01-11 07:46:22 |
Javier Jardón |
linux: statusexplanation |
This bug was reported a while ago and the last real comment made over 2 years ago. Please confirm if this is still an issue with the most recent Intrepid Ibex 8.10 release. Setting to Incomplete until we get further feedback. Thanks. |
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again! |
|
| 2010-05-11 19:30:10 |
Curtis Hovey |
removed subscriber Registry Administrators |
|
|
|
