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 437581 - Blocks while accessing slow/unresponsive remote share - must use async I/O
Blocks while accessing slow/unresponsive remote share - must use async I/O
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: menu
2.24.x
Other All
: Normal major
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 474586 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-05-10 23:29 UTC by Mikko Ohtamaa
Modified: 2020-11-06 20:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Mikko Ohtamaa 2007-05-10 23:29:22 UTC
Please describe the problem:
If there is a bookmark in Places menu which lead to a FTP site and one tries to open this bookmark when FTP is down, panel stops responding (Nautilus doesn't open the Window)

Steps to reproduce:
1. Bookmark FTP site in Nautilus
2. Shutdown FTP server
3. Try open bookmark through Places -> Bookmarks


Actual results:
Gnome-panel stops responding

Expected results:
An error dialog or Nautilus window telling that FTP is unreacable

Does this happen every time?
Yes

Other information:
Comment 1 simon80 2007-10-03 04:30:08 UTC
I can confirm this in both gnome-panel and nautilus.  An error dialog will eventually pop up, but it takes a long time, and the panel blocks throughout.  Opening with nautilus causes it to block as well.
Comment 2 Teppo Turtiainen 2007-12-29 22:05:28 UTC
*** Bug 474586 has been marked as a duplicate of this bug. ***
Comment 3 Teppo Turtiainen 2007-12-29 22:05:58 UTC
Confirming because of the duplicate.
Comment 4 Diego Escalante Urrelo (not reading bugmail) 2008-01-28 04:09:56 UTC
I can confirm this too. Happens with network places too. The panel locks until the site responds (and it's still happening in 2.21.x).
Comment 5 Cheba 2008-02-13 20:49:38 UTC
In my case panel stops responding and eats 100% on CPU. It happens when I'm trying to access menu.
Killing panel doesn't help. Panel restarts but it's unavailable from the start.
Comment 6 Cheba 2008-02-13 20:56:08 UTC
I believe that gnome-panel 2.21.90 was OK with my remote locations.
Currently I have 2.21.91.
Comment 7 Diego Escalante Urrelo (not reading bugmail) 2008-03-16 09:54:07 UTC
This recently got a bit worse. Doing some operation that uses gio (gvfs) and is somewhat cpu attractive makes the panel unresponsive.
Is this because it's trying to get a hold of an unresponsive gvfs daemon?

I'm raising severity in the name of all the cheap bastards like me that have no quick or reliable internet access.
Comment 8 Christian Kirbach 2008-12-21 11:37:20 UTC
I have seen this for a long time, too. See also Bug 523805 – Panel hang related to remote shares.
Christian Kellner states there that "obviously the panel is doing sync IO, which it shouldn't and you should really file another bug against the panel for that".

Hence retitling this bug. All remote share accesses that use gvfs seem to be affected.
Comment 9 Jakob Unterwurzacher 2009-04-27 13:41:18 UTC
bug 576274 and bug 328352 are duplicates of this.

Here http://launchpadlibrarian.net/26027899/gdb-gnome-panel.txt is another backtrace of trying to access a mounted but inaccessible ftp share.
Comment 10 Jakob Unterwurzacher 2009-04-27 13:42:03 UTC
Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/367879
Comment 11 Jakob Unterwurzacher 2009-04-29 11:44:40 UTC
Why does gnome-panel have to access the remote share anyway?
Why don't we just spawn a nautlius window an let that handle it? Nautilus seems to handle broken mounts quite well (there is stop button, it doesn't hang etc).
Comment 12 James 2010-10-26 12:26:36 UTC
Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=545244

Still in gnome-panel 2.30.

I note that the last comment on this bug was 18 months ago, has there been any progress on it since?
Comment 13 André Klapper 2020-11-06 20:25:16 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.