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 711033 - "Open recent" hangs when there's files on a missing network share
"Open recent" hangs when there's files on a missing network share
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: User Interface
2.8.6
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2013-10-28 19:16 UTC by Vladimir Hidalgo
Modified: 2018-05-24 14:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Hang screen (26.84 KB, image/png)
2013-10-28 19:16 UTC, Vladimir Hidalgo
Details

Description Vladimir Hidalgo 2013-10-28 19:16:18 UTC
Reproduce:
1. Make sure an element on the "open recent" menu belongs to a network share that has dissapeared.
2. Close and reopen GIMP
3. Try to access "open recent" menu -- it'll hang for like 30s

On GIMP 2.9.1 the debug console shows:
gimp_imagefile_icon_callback: Error al obtener la informaci¾n del archivo ½\\192
.168.1.25\scan\2013-10-25\Scan20032.JPG╗: No such file or directory

The first time GIMP will hang waiting for a timeout while verifying the resource in the non-existent network share.

After the first time, subsequent access to this menu are not affected (results cached I guess).

This is a common scenario for a laptop because you often open resources from network shares that later are not available.
Comment 1 Vladimir Hidalgo 2013-10-28 19:16:49 UTC
Created attachment 258336 [details]
Hang screen
Comment 2 Jehan 2013-10-28 23:03:37 UTC
Hmmm... That's strange. Normally this icon fetching is asynchronous in the code. It should not hang like this. I'll have a look, maybe in a few days, and see if I can reproduce.
Comment 3 Michael Natterer 2013-10-29 20:55:35 UTC
Don't we have a really old bug about the same?
Comment 4 Jehan 2016-09-07 22:36:10 UTC
Completely forgot about this. Sorry I don't have time to create a new VM and test this these days, but this kind of bug with error message and reproduction steps should be quite easy to debug for a Windows developer.
Adding the "newcomers" keyword.
Comment 5 LRN 2017-01-25 12:34:40 UTC
This doesn't happen for me with gimp 2.9.5 unstable 6790938
Comment 6 GNOME Infrastructure Team 2018-05-24 14:01:01 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/506.