As far as I can see this issue (and 1006704 and probably more) is all about mount tools that read /etc/mtab or /proc/mounts and find a mountpoint that is inaccessable due to user access rights: The app is running as user A and finds this mountpoint belonging to user B, clearly stated in the /etc/mtab and /proc/mounts.
>From my legacy unix ideas, I'd say the mounting application should mount this user-specific mountpoint using the '-n' option that it is not listed in /etc/mtab. The accessing tools like `mount`, `df`, `rsync` and others, should only use the mountpoints from /etc/mtab if they are run without root-rights. This avoids the listing problem. With current knowledge and cases where /etc/mtab is linked to /proc/mounts, I'd say the accessing tools (`mount`, `df`etc) should check the "user" flag in the mount line and if the found uid does not match the current or active uid, the mount errors should silently be ignored (or the entire mount can be skipped). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/867806 Title: df -h permission denied error To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/867806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
