After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 674482 - Nautilus doesn't show an error message when trying to open a directory without execute permission while logged in to a ssh server
Nautilus doesn't show an error message when trying to open a directory withou...
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: File and Folder Operations
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-04-20 16:43 UTC by Henrique Camargo
Modified: 2021-06-18 15:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Nautilus showing the slected pannel and the listing of the directory on the bottom (59.92 KB, image/png)
2012-09-05 18:18 UTC, Henrique Camargo
Details

Description Henrique Camargo 2012-04-20 16:43:43 UTC
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.

This bug was also reported in the Ubuntu Launchpad Bug Tracker in the URL: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/981127

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
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.nautilus.window-state geometry '800x550+126+367'
 org.gnome.nautilus.window-state sidebar-width 220
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)
Comment 1 William Jon McCann 2012-09-04 20:53:44 UTC
Confirmed.
Comment 2 William Jon McCann 2012-09-04 22:46:04 UTC
Maybe we could use an infobar to say the location can't be seen?
Comment 3 Henrique Camargo 2012-09-05 18:18:24 UTC
Created attachment 223573 [details]
Nautilus showing the slected pannel and the listing of the directory on the bottom
Comment 4 Henrique Camargo 2012-09-05 18:21:33 UTC
I've just re-run the testcase on a newer version of Nautilus (nautilus 1:3.4.2-0ubuntu4) and the panel now gets "selected" instead of empty. In my opinion, this is a better behavior than not showing anything at all. Although I would prefer to see an explanation on why Nautilus is not being able to list the directory. An infobar seems nice, but in other situations where Nautilus does not have permission it shows a popup, maybe we should follow the current way? 
 
I've attached a screenshot showing the "selected" panel at the top and a ls of the directory over ssh on a shell at the bottom. 
 
I did another test and followed the testcase locally instead of over ssh. Locally Nautilus is able to list the contents of the directory even without execute permission but it can't retrieve any other information other than the filenames. 
 
I don't know what changes for Nautilus when it's over ssh. Maybe it should be able to list the directory over ssh and another bug is preventing it from doing so. In that case we should investigate further. 
 
I'm willing to get my hands down into the nautilus code to find out what is happening. Can you provide me with some pointers?
Comment 5 André Klapper 2021-06-18 15:15:43 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of Files (nautilus), then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/

Thank you for your understanding and your help.