Bug 177984
Summary: | Chooser fails silently (no message) without directory permissions | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Gianluca Cecchi <gianluca.cecchi> |
Component: | gnome-vfs2 | Assignee: | Alexander Larsson <alexl> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | bnocera, hdegoede, johnp, mattdm, mti, sundaram |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-04-07 12:01:01 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Attachments: |
Description
Gianluca Cecchi
2006-01-16 23:57:19 UTC
Created attachment 123273 [details]
sometimes I get the file attached when doble click dir without permissions
It seems a general file system navigation problem. I get the error also in gedit and gimp. Sorry. Is it possible to post the bug under another application? Which one? Gianluca Ok.. was able to reproduce this crash, looks like it the problem is in gnome-vfs. # as root mkdir /home/wmealing/test chown root.root /home/wmealing/test/ chmod 0000 /home/wmealing/test/ Attaching the crash data momentarily. Created attachment 123600 [details]
Console crash debug information, reproducing crash for this bug
Looks like a gnome-vfs problem , rather than a totem issue.
Created attachment 123601 [details]
Gimp crash, doing the same procedure.
Console debug output for gimp
[wmealing@localhost ~]$ rpm -qa | grep vfs gnome-vfs2-devel-2.13.3-3 gnome-vfs2-smb-2.13.3-3 gnome-vfs2-2.13.3-3 gnome-python2-gnomevfs-2.12.1-1.2 [wmealing@localhost ~]$ rpm -q gimp gimp-2.2.10-2 [wmealing@localhost ~]$ rpm -q totem totem-1.3.0-3 CC'ed bnocera and reassigned to Ray. That's a gnome-vfs crash, nothing to do with Totem. This looks like a bad free in the inotify code. Can anyone try this with debuginfo packages installed? Now with gimp and totem, you get no errors or crashes, but in my opinion the behaviour is not correct: you seem to navigate inside the directory where you have no rights for (es 700 and you are not the owner), and you see no files in it. You don't receive any permission denied error... [gcecchi@fedora ~]$ rpm -qa | grep vfs gnome-python2-gnomevfs-2.12.1-1.2 gnome-vfs2-devel-2.13.4-4 gnome-vfs2-2.13.4-4 gnome-vfs2-smb-2.13.4-4 [gcecchi@fedora ~]$ rpm -q totem totem-1.3.90-1 [gcecchi@fedora ~]$ rpm -q gimp gimp-2.2.10-2 with file explorer instead for example, when trying to go inside directory without r-x permission, you get pop up window with: "The folder contents could not be displayed. You do not have the permissions necessary to view the contents of "dirname"." hmm, the instructions in comment #3 don't crash for me. I do see crashes with a locally built old gnome-vfs, though. Wade, do you still see this ? hey, it's about one month from initial post and many versions of the various packages involved changed. See #10 and #11 where no more errors, but see also my comments about silent behaviour... this evening I will try with latest packages installed, in particular with gnome-vfs2-2.13.91-1 and totem-1.3.91-1 and gimp-2.2.10-2.2 and let know. the silent behaviour will be a bit more work to fix in the file chooser, not fc5blocker material. ok, in the mean time I confirmed the silent behaviour with the versions in #13 and overall packages updated as of "rawhide report: 20060216 changes" *** Bug 181053 has been marked as a duplicate of this bug. *** These bugs are being closed since a large number of updates have been released after the FC5 test1 and test2 releases. Kindly update your system by running yum update as root user or try out the third and final test version of FC5 being released in a short while and verify if the bugs are still present on the system .Reopen or file new bug reports as appropriate after confirming the presence of this issue. Thanks I haven't been able to reproduce the crash from the file chooser of nautilus when navigating to an unreadable folder with recent versions of gnome-vfs. Can anybody still reproduce this ? Unable to reproduce using method described in comment #3 using: gnome-vfs2-2.13.92-3 the situation is as detailed in #13 by me and #14 by Matthias Clasen. So the only problem is that one would expectd a permission denied problem when navigating inside a folder without permissions for, not the system entering in it without showing any files/dir and giving no error... As requested on fedora-devel I'm looking at FC5 blocker bugs as I understand, from above this one can be removed from the blocker list, shall I? yes indeed. Changing summary to something describing the current bug; i.e., if the user lacks permission to view a directory the file chooser fails silently, merely not showing files in that directory, rather than giving an informative error message. This occurs when browsing directories using gnome-vfs on, e.g., totem and gimp. Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer test releases. We're cleaning up the bug database and making sure important bug reports filed against these test releases don't get lost. It would be helpful if you could test this issue with a released version of Fedora or with the latest development / test release. Thanks for your help and for your patience. [This is a bulk message for all open FC5/FC6 test release bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.] I just tried this on a Fedora 7 test / rawhide system last update a couple of dasy ago and this still happens, bad BAD! I'll also file this upstream and add a bugzilla reference here. Okay, cool. At that point this can be closed as "upstream". Oh, hey, like you already did. Time for coffee for me! |