I think this is a Unity action, not Nautilus ** Package changed: nautilus (Ubuntu) => unity
** Summary changed: - Unable to open a folder for 10 GB Filesystem", "No application is registered as handling this file... Nautilus pops browser on bash partition mount + Unable to open a folder for 10 GB Filesystem", "No application is registered as handling this file... or Nautilus pops browser when partition is mounted in bash script ** Description changed: I first noticed this behaviour in Ubuntu 11.10. When I run my bash script that mounts partitions on my hard drive (e.g /dev/sda5), Nautilus pops up with a browser window. This is an illogical action, since I've not 'inserted a drive', it's already there, and it's just been manually mounted. This Nautilus action will interfere with the scripts operation since, when the script tries to unmount the drive (rapidly) it finds that Nautilus is still busy with it, producing it's browser window. If I run chmod 700 on the mountpoint prior to mounting (root only access), then I get a popup message stating: "Unable to open a folder for 10 GB Filesystem", "No application is registered as handling this file". This is because the mountpoint is not accessible to the logged in user. You wouldn't expect this if you mount a partition from the terminal - and for the most part this is correct (Nautilus does nothing), but not all the time. I've managed to trigger Nautilus to pop just with a simple terminal mount. I have a workaround in my bash script that creates a udev rule and runs udevadm trigger to hide the partition, but this seems extreme. I believe - it's a bug in Nautilus in how it responds to the signal that a partition - has been mounted. + it's a bug in Unity(?) (maybe Nautilus?) in how it responds to the + signal that a partition has been mounted. Please see this for complete details and discussion of possible solutions (and the bash script code): http://askubuntu.com/questions/121569/prevent-nautilus-showing- partition-mounted-in-bash-script I understand you can prevent Nautilus responding to inserted drives etc., but this is definitely not the case here - the drive is already there, just the partition is being mounted. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/986269 Title: Unable to open a folder for 10 GB Filesystem", "No application is registered as handling this file... or Nautilus pops browser when partition is mounted in bash script Status in Unity: New Bug description: I first noticed this behaviour in Ubuntu 11.10. When I run my bash script that mounts partitions on my hard drive (e.g /dev/sda5), Nautilus pops up with a browser window. This is an illogical action, since I've not 'inserted a drive', it's already there, and it's just been manually mounted. This Nautilus action will interfere with the scripts operation since, when the script tries to unmount the drive (rapidly) it finds that Nautilus is still busy with it, producing it's browser window. If I run chmod 700 on the mountpoint prior to mounting (root only access), then I get a popup message stating: "Unable to open a folder for 10 GB Filesystem", "No application is registered as handling this file". This is because the mountpoint is not accessible to the logged in user. You wouldn't expect this if you mount a partition from the terminal - and for the most part this is correct (Nautilus does nothing), but not all the time. I've managed to trigger Nautilus to pop just with a simple terminal mount. I have a workaround in my bash script that creates a udev rule and runs udevadm trigger to hide the partition, but this seems extreme. I believe it's a bug in Unity(?) (maybe Nautilus?) in how it responds to the signal that a partition has been mounted. Please see this for complete details and discussion of possible solutions (and the bash script code): http://askubuntu.com/questions/121569/prevent-nautilus-showing- partition-mounted-in-bash-script I understand you can prevent Nautilus responding to inserted drives etc., but this is definitely not the case here - the drive is already there, just the partition is being mounted. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/986269/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
