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 306175 - Error message at gimp launch (start up and when looking for plugins)
Error message at gimp launch (start up and when looking for plugins)
Status: RESOLVED DUPLICATE of bug 170948
Product: GIMP
Classification: Other
Component: General
2.2.x
Other All
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2005-06-01 18:10 UTC by Marty
Modified: 2008-01-15 12:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Marty 2005-06-01 18:10:31 UTC
Please describe the problem:
I am running gimp 2.2.7 and gtk 2.6.7-1 for windows on win XP SP2.
When i start Gimp i have several (4) errors windows with this message (in 
french) "Pas de disque dans le lecteur", (something like : "there is no disk 
in device").
It happens each time i start Gimp. Twice at the very beginning of the 
launching process (before the splash window) and twice while looking for 
plugins (AlienMap2.exe). I just have to click on "continue" 4 times and 
eventually Gimp starts.
This problem happens with less up to date gimp and gtk.


Steps to reproduce:
1. Just start Gimp 2.2.7 (gtk 2.6.7-1) on win XP SP2
2. 
3. 


Actual results:
When i start Gimp i have several (4) errors windows with this message (in 
french) "Pas de disque dans le lecteur", (something like : "there is no disk 
in device").

Expected results:
No error message

Does this happen every time?
Yes

Other information:
I find on forums that it can be related with SD/Compact Flash card device. It 
seems that gimp or plugins are trying to read these devices even if there is 
no card... hope it could help :)

Thank you for your very good job
Comment 1 weskaggs 2005-06-02 15:09:34 UTC
Thanks for the report.  This problem has been solved, and should be fixed in
Gtk+ 2.6.8, when it is released.

*** This bug has been marked as a duplicate of 170948 ***