http://bugs.winehq.org/show_bug.cgi?id=15878
Summary: Dogfood: Gimp 2.6 will not open images. Product: Wine Version: 1.1.7 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: loader AssignedTo: wine-bugs@winehq.org ReportedBy: true.bugman@gmail.com
Created an attachment (id=17033) --> (http://bugs.winehq.org/attachment.cgi?id=17033) Gimp start up messages
When using gimp 2.6, image files will not load making the program unusable. Instead lots of "err:module:import_dll Library ..." messages are printed. The problem is visible on program start up as well. Hence, as Mandriva 2008.1 comes with gimp 2.4.5, I can't use this newer version to replace the old version that came with the distribution.
http://bugs.winehq.org/show_bug.cgi?id=15878
--- Comment #1 from Edward d'Auvergne true.bugman@gmail.com 2008-11-01 14:37:10 --- Created an attachment (id=17034) --> (http://bugs.winehq.org/attachment.cgi?id=17034) Gimp image loading messages (trying to load a JPG image).
http://bugs.winehq.org/show_bug.cgi?id=15878
--- Comment #2 from Edward d'Auvergne true.bugman@gmail.com 2008-11-01 14:48:22 --- The exact gimp version tested is 2.6.1. A quick link for downloading the latest Windows version is http://gimp-win.sourceforge.net/stable.html.
http://bugs.winehq.org/show_bug.cgi?id=15878
Edward d'Auvergne true.bugman@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |true.bugman@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=15878
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #17033|application/octet-stream |text/plain mime type| | Attachment #17033|gimp_2.6_startup |gimp_2.6_startup.txt filename| |
--- Comment #3 from Austin English austinenglish@gmail.com 2008-11-01 16:58:45 --- (From update of attachment 17033) Please use plain text extension
http://bugs.winehq.org/show_bug.cgi?id=15878
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |http://downloads.sourceforge | |.net/gimp-win/gimp-2.6.2- | |i686-setup.exe Status|UNCONFIRMED |RESOLVED Keywords| |download, source Resolution| |INVALID
--- Comment #4 from Austin English austinenglish@gmail.com 2008-11-01 17:21:13 --- Invalid. cd to the directory first.
http://bugs.winehq.org/show_bug.cgi?id=15878
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Austin English austinenglish@gmail.com 2008-11-01 17:21:19 --- Closing invalid.
http://bugs.winehq.org/show_bug.cgi?id=15878
Edward d'Auvergne true.bugman@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #17034|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=15878
Edward d'Auvergne true.bugman@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|INVALID |
--- Comment #6 from Edward d'Auvergne true.bugman@gmail.com 2008-11-01 19:20:33 --- Changing to the gimp installation directory (.../Program Files/Gimp-2.0/bin) and then running the program fixes the problem. However this is clumsy when editing images starting from the console - if you found the image and you are sitting in that directory, then you have to switch to the Gimp installation directory and then navigate back from the Gimp file dialog. Also using an alias to run the gimp through wine will not work. And I am trying to run this from the wine gimp menu entry, hence running the gimp in this way - the normal way for most users - always fails! In MS Windows 2000 SP4, the gimp runs both from the menu and from the command line without being in the gimp installation directory. So this is a real bug. This issue is a problem if you want to run the program for everyday use - and you don't have to do that directory jumping for the native Linux binary or the native Windows binary within Windows.
http://bugs.winehq.org/show_bug.cgi?id=15878
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #7 from Dmitry Timoshkov dmitry@codeweavers.com 2008-11-02 02:06:00 --- http://wiki.winehq.org/FAQ#head-60c5de309a53bb8ed07d8af1ca26db129334cb43
http://bugs.winehq.org/show_bug.cgi?id=15878
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Dmitry Timoshkov dmitry@codeweavers.com 2008-11-02 02:06:11 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=15878
--- Comment #9 from Edward d'Auvergne true.bugman@gmail.com 2008-11-02 05:13:10 --- Hmmm, well, so much for using the gimp as dogfood. And this one was getting so close too.
http://bugs.winehq.org/show_bug.cgi?id=15878
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|loader |-unknown
--- Comment #10 from Dmitry Timoshkov dmitry@codeweavers.com 2008-11-02 06:05:22 --- Probably you didn't get it, but that's not a Wine limitation, this is a bug in Gimp, report it to Gimp developers.
http://bugs.winehq.org/show_bug.cgi?id=15878
--- Comment #11 from Edward d'Auvergne true.bugman@gmail.com 2008-11-02 06:13:20 --- Please see comment six. I've tested this and this problem doesn't exist when running the Windows binary in Windows (Gimp-2.6.2 + MS Windows 2000 SP4). And it doesn't exist when running the Linux binary in Linux (Gimp-2.4.5 + Mandriva 2008.1). This is not a Gimp bug as the problem only exists within Wine! Therefore if dogfood is to be serious - i.e. you run the program for everyday use - then this is a bug. Otherwise, please ignore my comments.
http://bugs.winehq.org/show_bug.cgi?id=15878
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|INVALID |
--- Comment #12 from Alexandre Julliard julliard@winehq.org 2008-11-03 04:33:41 --- If it works on Windows from the command line it's a valid bug.
http://bugs.winehq.org/show_bug.cgi?id=15878
--- Comment #13 from Austin English austinenglish@gmail.com 2008-11-03 12:49:01 --- Haven't tested yet, but looking at a box at work with an older Gimp installed, I see: %GTK_BASEPATH%\bin
is in $PATH. I didn't see this in Wine. This was on older Gimp version, but worth a look.
http://bugs.winehq.org/show_bug.cgi?id=15878
--- Comment #14 from Edward d'Auvergne true.bugman@gmail.com 2008-11-03 14:50:39 --- All registry keys containing the word 'gimp' in Windows and in Wine appear to be identical, well all except for the user. Adding the Gimp installation path to the Wine \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\Path registry key doesn't help either.
http://bugs.winehq.org/show_bug.cgi?id=15878
--- Comment #15 from Edward d'Auvergne true.bugman@gmail.com 2008-11-03 16:20:09 --- Could the problem be that the Windows DLL loader searches the path of the binary for the libraries as a last resort (they are located in C:\Program Files\Gimp-2.0\bin if installed in the default location), whereas the Wine DLL loader does not?
This is a bit hard to test out, as getting wine to compile on a 64-bit system is a nightmare. From first looks, the calls to the fixup_imports() function in dlls/ntdll/loader.c doesn't seem to be right or at least it doesn't seem to be exactly as described at http://msdn.microsoft.com/en-us/magazine/cc301727.aspx. I would guess that following the exact order in this documentation doesn't matter too much. Or maybe this documentation of the loader from Win2000 is a bit old. Anyway, should there be a LdrpCheckForLoadedDll or LdrCheckForLoadedDll function used here to resolve this path issue? Or does fixup_imports() do this work?
http://bugs.winehq.org/show_bug.cgi?id=15878
Xavier Vachon xvachon@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xvachon@gmail.com
--- Comment #16 from Xavier Vachon xvachon@gmail.com 2009-06-03 14:30:47 --- With latest git (1.1.22) and GIMP 2.6.6, I am able to open images without problems. Edward, could you double-check?
http://bugs.winehq.org/show_bug.cgi?id=15878
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #17 from Ken Sharp kennybobs@o2.co.uk 2009-06-05 17:39:08 --- Works fine here too with 2.6.2.
http://bugs.winehq.org/show_bug.cgi?id=15878
--- Comment #18 from Edward d'Auvergne true.bugman@gmail.com 2009-06-06 07:31:40 --- Just tested 32 bit Gimp-2.6.2 with wine-1.1.22 and a fresh '.wine' directory (Mandriva 2009.1 x86-64). This bug still is present. Please try one of the following to trigger it:
Launch Gimp from the KDE, Genome, etc. menu.
Or from any directory other than that in which Gimp is installed, run:
$ wine ~/.wine/drive_c/Program\ Files/Gimp-2.0/bin/gimp-2.6.exe
Then once Gimp is running, open any image.
With Gimp-2.6.6, the bug appears different - no images are displayed in the file dialogs. When launching from the ~/.wine/drive_c/Program\ Files/Gimp-2.0/bin/ directory with "$ wine gimp-2.6.exe" the bug is no uncovered.
Messages which might be important when launching the gimp using the second method are:
fixme:font:ExtTextOutW flags ETO_NUMERICSLOCAL | ETO_NUMERICSLATIN | ETO_PDY unimplemented err:module:import_dll Library libgimpui-2.0-0.dll (which is needed by L"C:\Program Files\Gimp-2.0\lib\gimp\2.0\plug-ins\script-fu.exe") not found err:module:import_dll Library libgimp-2.0-0.dll (which is needed by L"C:\Program Files\Gimp-2.0\lib\gimp\2.0\plug-ins\script-fu.exe") not found err:module:import_dll Library libgimpbase-2.0-0.dll (which is needed by L"C:\Program Files\Gimp-2.0\lib\gimp\2.0\plug-ins\script-fu.exe") not found err:module:import_dll Library libgimpcolor-2.0-0.dll (which is needed by L"C:\Program Files\Gimp-2.0\lib\gimp\2.0\plug-ins\script-fu.exe") not found err:module:import_dll Library libgimpwidgets-2.0-0.dll (which is needed by L"C:\Program Files\Gimp-2.0\lib\gimp\2.0\plug-ins\script-fu.exe") not found err:module:import_dll Library libglib-2.0-0.dll (which is needed by L"C:\Program Files\Gimp-2.0\lib\gimp\2.0\plug-ins\script-fu.exe") not found err:module:import_dll Library libgobject-2.0-0.dll (which is needed by L"C:\Program Files\Gimp-2.0\lib\gimp\2.0\plug-ins\script-fu.exe") not found err:module:import_dll Library libgtk-win32-2.0-0.dll (which is needed by L"C:\Program Files\Gimp-2.0\lib\gimp\2.0\plug-ins\script-fu.exe") not found err:module:import_dll Library intl.dll (which is needed by L"C:\Program Files\Gimp-2.0\lib\gimp\2.0\plug-ins\script-fu.exe") not found err:module:LdrInitializeThunk Main exe initialization for L"C:\Program Files\Gimp-2.0\lib\gimp\2.0\plug-ins\script-fu.exe" failed, status c0000135
http://bugs.winehq.org/show_bug.cgi?id=15878
--- Comment #19 from Austin English austinenglish@gmail.com 2009-06-06 14:12:18 --- (In reply to comment #18)
Just tested 32 bit Gimp-2.6.2 with wine-1.1.22 and a fresh '.wine' directory (Mandriva 2009.1 x86-64). This bug still is present. Please try one of the following to trigger it:
Launch Gimp from the KDE, Genome, etc. menu.
Or from any directory other than that in which Gimp is installed, run:
$ wine ~/.wine/drive_c/Program\ Files/Gimp-2.0/bin/gimp-2.6.exe
Then once Gimp is running, open any image.
With Gimp-2.6.6, the bug appears different - no images are displayed in the file dialogs. When launching from the ~/.wine/drive_c/Program\ Files/Gimp-2.0/bin/ directory with "$ wine gimp-2.6.exe" the bug is no uncovered.
Gimp is depending on being started from its directory. That's a gimp bug.
http://bugs.winehq.org/show_bug.cgi?id=15878
--- Comment #20 from Edward d'Auvergne true.bugman@gmail.com 2009-06-06 15:00:34 --- But only in Wine is this a problem. This is not a problem for native Gimp on any platform. Please see comment 6 (http://bugs.winehq.org/show_bug.cgi?id=15878#c6). Native gimp can execute from the Windows start menu or the Gnome/KDE/etc. menus in Linux. Installing Gimp with Wine generates entries in the wine menu subsection, but these are non-functional as Gimp run from here does not work. Surely this DLL resolution issue would also affect many other programs?
http://bugs.winehq.org/show_bug.cgi?id=15878
--- Comment #21 from Austin English austinenglish@gmail.com 2009-06-06 17:13:21 --- (In reply to comment #20)
But only in Wine is this a problem. This is not a problem for native Gimp on any platform. Please see comment 6 (http://bugs.winehq.org/show_bug.cgi?id=15878#c6). Native gimp can execute from the Windows start menu or the Gnome/KDE/etc. menus in Linux. Installing Gimp with Wine generates entries in the wine menu subsection, but these are non-functional as Gimp run from here does not work. Surely this DLL resolution issue would also affect many other programs?
Launching it from the start menu on windows changes the working directory. Wine uses the PATH variable in the xdg-desktop spec to accomplish this. Make sure your desktop is following that spec.
http://bugs.winehq.org/show_bug.cgi?id=15878
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #22 from Alexandre Julliard julliard@winehq.org 2009-06-19 11:01:14 --- Closing bugs fixed in 1.1.24.
-
wine-bugs＠winehq.org