[Bug 14495] udev sends multiple add/remove events in quick succession

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=14495
Ubuntu | linux





------- Additional Comments From martin.pitt at ubuntu.com  2005-09-29 22:01 UTC -------
(In reply to comment #64)

> Could it be an ordering problem in hal, maybe that's not taking as much care as
> udev to avoid running two events for the same device simultaneously?

Not really. The problem is rather that mounting and umounting go through
completely different paths:

  device addition -> udev -> hal -> g-v-m -> pmount
  device removal -> udev -> /etc/dev.d/block/hal-umount.dev

since the hal-umount.dev script is actually intented to clean up after the user
rips out a device without unmounting, and hal etc. does the automount magic.
Thus it's a race condition that is not easily solved. It's hard to tell from hal
whether a given removal event is real and when it is only a bouncing effect of
adding a device.

Andreas, it would be interesting to see how hal behaves. Can you please start
hald in debug mode as described in the second half of
http://wiki.ubuntu.com/DebuggingRemovableDevices and see how many events hal
actually receives, and in which order? Thanks!

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.