Description of problem: DeviceKit asks the desktop user to authenticate when a process running with root privileges is creating a filesystem on a (flat-file) disk image and/or loopmounts the filesystem. Version-Release number of selected component (if applicable): DeviceKit-003-1.x86_64 DeviceKit-disks-003-9.fc11.x86_64 DeviceKit-power-008-0.1.20090401git.fc11.x86_64 How reproducible: livecd-tools -c whatever.ks, or revisor Actual results: Authentication dialog appears, requesting the user authenticates as root Expected results: No dialog, no error, nothing whatsoever. Other applications are running here. Additional info:
First of all, there is really no good way to fix this; the same problem applies for partitioning programs, installers and so on. It's like having your cake and trying to eat. FWIW, the traditional way of working around this is to teach applications that use devices (such as anaconda, gparted and livecd-tools) to somehow "reserve" said devices to avoid policy like automounting happening. That's why we have things like "devkit-disks --inhibit" and D-Bus methods for the same. That said, I think in this case we should fix the desktop automounter to only automount file systems that reside on "real" disk drives; e.g. where the drive is from a known bus and not some virtual abstraction like device-mapper. Btw, filing this against DeviceKit-disks is about as meaningful as filing it against the mount(8) command. The right component would be Nautilus (since Nautilus is the policy component responsible for deciding whether a file system should be mounted) but I'm reassigning it to gvfs since the volume monitor is the one who sets the should_automount flag.
Fixed in gvfs-1.2.1-2.fc11. http://koji.fedoraproject.org/koji/taskinfo?taskID=1287838