Nautilus doesn't show an error message when trying to open a directory without execute permission while logged in to a ssh server
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nautilus |
Confirmed
|
Medium
|
|||
nautilus (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
While logged to a ssh server using Nautilus and you double-click to open a directory that the current user doesn't have execute permissions, nautilus opens the directory and shows an empty directory instead of showing an error message. There's no way to tell if the directory is actually empty or if the user doesn't have the necessary permissions.
Steps to reproduce:
1) Log in to the remote server using ssh in a terminal
$ ssh username@server
1) Create a directory
$ mkdir test
2) Create a file inside that directory
$ cd test
$ touch file
3) Revoke the execute permission on that directory
$ cd ..
$ chmod -x test
4) Open the ssh server using Nautilus
File -> Connect to Server...
5) Open that directory using Nautilus
What I expected:
Nautilus should show some kind of visual clue that the user doesn't have the necessary permissions to open that directory.
What happened instead:
Nautilus didn't gave a warning or error message and showed me an empty directory which is misleading.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.4.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
Date: Fri Apr 13 16:26:39 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
org.gnome.
org.gnome.
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in nautilus: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Changed in nautilus (Ubuntu): | |
status: | New → Triaged |
Changed in nautilus: | |
status: | New → Confirmed |
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https:/ /wiki.ubuntu. com/Bugs/ Upstream/ GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.