Created attachment 61504 [details] gvfs-mount -li OLPC run / on a bind-mount for reasons described in http://lists.freedesktop.org/archives/devkit-devel/2012-May/001267.html udisks_mount_monitor_get_mountinfo() seems to ignore such mounts: /* ignore mounts where only a subtree of a filesystem is mounted */ if (g_strcmp0 (encoded_root, "/") != 0) continue; This means that when we boot, we get the partition containing the root fs mounted as a user partition at /run/media/users/olpc/OLPCRoot. As its confusing for users we'd like to get rid of this. Can udisks be made to understand this fs layout a little better?
Created attachment 61505 [details] udisksctl dump
Created attachment 61506 [details] /proc/self/mountinfo
Version info: Fedora 17 running on OLPC XO-1.75 (same problem seen on XO-1.5). libatasmart-0.18-2.fc17.armv7hl udisks2-1.94.0-1.fc17.armv7hl gvfs-1.12.2-1.fc17.armv7hl
First of all, I'm guessing the mount /run/media/olpc/OLPCRoot is done by some gvfs-using automounter exactly because MountsPoints is empty, right? (ie. if we fix the bug this shouldn't happen) I wonder what we _should_ be showing in MountPoints... there are two possibilities, ["/", "/home", "/versions"] or just ["/"] ... seems the former is more correct (for some values of correct) but the latter is fine too ... I think the latter (just "/") can be achieved by just removing the lines you quoted, e.g. /* ignore mounts where only a subtree of a filesystem is mounted */ if (g_strcmp0 (encoded_root, "/") != 0) continue; Any chance you can try this?
Created attachment 61654 [details] new dump Yes, OLPCRoot is auto-mounted by Nautilus in the above dumps. I removed the lines suggested and it solves the problem. The device appears with mountpoints which look reasonable, and Nautilus doesn't automount it in a strange place.
OK, I've removed those two lines - thanks for the bug report and testing! http://cgit.freedesktop.org/udisks/commit/?id=e0b8ffe3099735fefd64973e6575c67ac0759be2
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.