GNOME Bugzilla – Bug 332245
handle unreadable directories better
Last modified: 2015-10-02 10:59:49 UTC
With the gnome-vfs backend, unreadable directories are silently displayed as if they were empty. With the unix backend, we get an error dialog, since get_folder returns an error. It would be nice if a) the async code should result in the error dialog, too b) we could decorate the directory icon with an emblem marking it as unreadable (nautilus already does that...)
This has been reported long ago in RedHat's bugzilla too, see: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177984 This is jusy FYI, there is no new information there. Why hasn't this been fixed by now? Seems like a bad bug from a usability pov.
*** Bug 400558 has been marked as a duplicate of this bug. ***
Bug 400558 mentions another way to reproduce the bug: ---8<--- 1. Add a non-working entry to your ~/.gtk-bookmarks $ gnomevfs-ls smb://192.168.2.1/ Error opening: Timeout reached $ echo smb://192.168.2.1/ >> ~/.gtk-bookmarks 2. Open a gnome-vfs aware application, and go to its Open dialogue 3. Double-click on the "/ on 192.168.2.1" bookmark 4. See an empty right pane (after a little while), instead of getting an error message ---8<--- Moving to libgnomeui, as it's where the backend code lies.
What to do now that the backends are gone from libgnomeui again? :-)
If it still happens, it's a GTK+ bug.
We're getting an error dialog nowadays, after the timeout. And a busy cursor before.