inconsistent automounting on startup
Bug #396448 reported by
Martin Pitt
This bug affects 46 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs |
Fix Released
|
Medium
|
|||
obsolete |
Fix Released
|
Medium
|
|||
devicekit-disks (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Karmic |
Fix Released
|
High
|
Martin Pitt | ||
gvfs (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Karmic |
Fix Released
|
High
|
Martin Pitt |
Bug Description
Binary package hint: devicekit-disks
When starting a GNOME session without dk-disks running already, gvfs D-BUS activates dk-disks, which causes an automount attempt on internal hard disks. This doesn't happen if dk-disks is already running.
I suspect it's due to dk-disks sending out "new volume" events during coldplugging.
Reproducer:
ps ux|grep gvfs|awk '{print $2}'|xargs kill
gvfs-mount -l
This does not trigger automounting. However, if this spawns dk-disks it happens:
sudo killall devkit-disks-daemon
ps ux|grep gvfs|awk '{print $2}'|xargs kill
gvfs-mount -l
Changed in devicekit: | |
status: | Unknown → Confirmed |
summary: |
- internal partitions get automounted on startup + inconsistent automounting on startup |
Changed in gvfs: | |
status: | Unknown → Confirmed |
affects: | hundredpapercuts → null |
Changed in devicekit: | |
status: | Confirmed → Fix Released |
Changed in devicekit-disks (Ubuntu Karmic): | |
status: | Fix Released → Fix Committed |
tags: | added: iso-testing |
description: | updated |
Changed in devicekit: | |
importance: | Unknown → Medium |
Changed in gvfs: | |
importance: | Unknown → Medium |
status: | Confirmed → Fix Released |
Changed in devicekit: | |
importance: | Medium → Unknown |
Changed in devicekit: | |
importance: | Unknown → Medium |
no longer affects: | null |
To post a comment you must log in.
Created an attachment (id=27449)
debug output
This is the devkit-disks-daemon output when being d-bus activated through gvfs. The log shows that initially the internal hard disk partitions (sdaX) are added:
**** ADDING /sys/devices/ pci0000: 00/0000: 00:1f.1/ host0/target0: 0:0/0:0: 0:0/block/ sda/sda3 pci0000: 00/0000: 00:1f.1/ host0/target0: 0:0/0:0: 0:0/block/ sda/sda3
**** UPDATING /sys/devices/
This shouldn't emit events (device_add() gets called with emit_event==FALSE from devkit_ disks_daemon_ new()), but right after that I get change events as well:
**** CHANGING /sys/devices/ pci0000: 00/0000: 00:1f.1/ host0/target0: 0:0/0:0: 0:0/block/ sda/sda3 pci0000: 00/0000: 00:1f.1/ host0/target0: 0:0/0:0: 0:0/block/ sda/sda3
**** UPDATING /sys/devices/