GNOME Bugzilla – Bug 795855
Require glib 2.56.2 or later (was: File chooser dialogs do not show folders or files for drive roots (e.g. C:\, D:\, ...))
Last modified: 2018-05-17 20:33:09 UTC
Created attachment 371756 [details] file for partition disk hd Hi my problem open images and save image in all partition for windows. attach file screen shot . Windows 10 April home 64 bit using gimp 2.10 update 1 64bit. Idea solution ?
*** Bug 795862 has been marked as a duplicate of this bug. ***
*** Bug 795809 has been marked as a duplicate of this bug. ***
*** Bug 795908 has been marked as a duplicate of this bug. ***
*** Bug 795902 has been marked as a duplicate of this bug. ***
*** Bug 795952 has been marked as a duplicate of this bug. ***
I have the same problem, but running on Windows 10 x64, no previous GIMP version was installed. If you click the C-drive, D-drive, etc. nothing shows up. But if you click the pencil to edit the path, and type a full path (or select from the folders that appear from the "preview list" after typing ex. C:\ ) then it works. If you click on the "pictures" or "documents" shortcuts below the drives, those do work. Seems like an error in the code? Noticed this error message appear when I enter "c:" (without the qoutes and a backslash) in the Location-entry: "GIMP Message Opening 'W:\work\documents\c:' failed: Error opening file W:\work\documents\c:: Input/output error" Seems that GIMP thinks that everything is in the "documents" directory, even if you type "c:"? Once you type C:\ en pick a directory in the list that appears, then it does work as intended as far as I notice (except for the root of the drives) Hope this helps somehow. :-)
*** Bug 795984 has been marked as a duplicate of this bug. ***
I'm having the same issue. Here is an animated gif to illustrate the problem: https://mega.nz/#!81VkgAyT!4VjM3LpIzrCeVFF2RqOHbrZ-9iTW7gt8bM1GuhKgH_I
*** Bug 796005 has been marked as a duplicate of this bug. ***
*** Bug 796004 has been marked as a duplicate of this bug. ***
I have the same issue. I did notice if I use Windows to navigate to a folder, right click an image file and select Gimp from the Open With menu Gimp does start and opens the image. After opening an image file this way it is possible to use File > Open and see a list of the files in the same directory as the one opened with right click, open with, but no other locations.
I think that it is caused by behavior change of windows 10 sysytem. For Example, on Windows's Explore.exe, we must wait for getting Drives data to open DataGrid (Information area), first time only. (see the address bar to show animation as status-bar.) Once getting filesystem' data, Not waiting. So, Please try to pre access the drives by API and to wait?
(In reply to ShiroYuki_Mot from comment #12) > I think that it is caused by behavior change of windows 10 sysytem. > For Example, on Windows's Explore.exe, we must wait for getting Drives data > to open DataGrid (Information area), first time only. > (see the address bar to show animation as status-bar.) > Once getting filesystem' data, Not waiting. > > So, Please try to pre access the drives by API and to wait? So, Please try to pre access the drives by API and/or to wait? (To wait for end of getting data)
(In reply to ShiroYuki_Mot from comment #13) > (In reply to ShiroYuki_Mot from comment #12) > > I think that it is caused by behavior change of windows 10 sysytem. > > For Example, on Windows's Explore.exe, we must wait for getting Drives data > > to open DataGrid (Information area), first time only. > > (see the address bar to show animation as status-bar.) > > Once getting filesystem' data, Not waiting. > > > > So, Please try to pre access the drives by API and to wait? > > So, Please try to pre access the drives by API and/or to wait? > (To wait for end of getting data) Are you a developer by any chance? :-) If so, we would definitely appreciate a patch since we are a little lacking on Windows developers and you seem to know your way around! ;-)
Bonjour, It may be the version of glib : https://bugzilla.gnome.org/show_bug.cgi?id=796003#c3 You may be able to check the glib version, on Windows : cd [gimp folder]\bin gimp-2.10.exe --version --verbose > gimp_environnement.txt start gimp_environnement.txt :o)
Dear jehan, thanks for your reply. :) Before reply, My GIMP 2.10.0 x64 (Installed by gimp-2.10.0-x64-setup.exe from Official) is work Correctly! No problem!. Another drive letter can be opened correctly. (ex. M:\ or N:\) But many reports up! ... ? So, I think like a pre post. Perhaps, The reporter will get a solution by opening the target drive on The Explorer, before opening GIMP, I think so. Or, Between two installer(recent and first), are there a differnce... ? Answer is No! I am not developer. Holiday programmer, using VB.net on .Netframework. (Sorry, my poor English ... X( )
(In reply to sylvie.alexandre from comment #15) > Bonjour, > > It may be the version of glib : > https://bugzilla.gnome.org/show_bug.cgi?id=796003#c3 > > You may be able to check the glib version, on Windows : > cd [gimp folder]\bin > gimp-2.10.exe --version --verbose > gimp_environnement.txt > start gimp_environnement.txt > > :o) I try... Open notepad.exe as an Administrator Save File As "gimp_environnement.txt" Open cmd.exe as an Administrator Microsoft Windows [Version 10.0.17134.48] (c) 2018 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>cd "c:\program files\gimp 2\bin" c:\Program Files\GIMP 2\bin>gimp-2.10.exe --version --verbose > gimp_environnement.txt c:\Program Files\GIMP 2\bin> c:\Program Files\GIMP 2\bin>rem GIMP Console Popup c:\Program Files\GIMP 2\bin>start gimp_environnement.txt プロセスはファイルにアクセスできません。別のプロセスが使用中です。 ( > En; The process can not access the file. Another process is in use.) c:\Program Files\GIMP 2\bin> c:\Program Files\GIMP 2\bin>rem Close GIMP Console c:\Program Files\GIMP 2\bin>start gimp_environnement.txt Results Like This ----------------- GIMP (GNU Image Manipulation Program) ver.2.10.0 git-describe: GIMP_2_10_0 C compiler: Using built-in specs. COLLECT_GCC=x86_64-w64-mingw32-gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-w64-mingw32/6.3-win32/lto-wrapper Target: x86_64-w64-mingw32 Configured with: ../../src/configure --build=x86_64-linux-gnu --prefix=/usr --includedir='/usr/include' --mandir='/usr/share/man' --infodir='/usr/share/info' --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir='/usr/lib/x86_64-linux-gnu' --libexecdir='/usr/lib/x86_64-linux-gnu' --disable-maintainer-mode --disable-dependency-tracking --prefix=/usr --enable-shared --enable-static --disable-multilib --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --libdir=/usr/lib --enable-libstdcxx-time=yes --with-tune=generic --enable-version-specific-runtime-libs --enable-fully-dynamic-string --enable-libgomp --enable-languages=c,c++,fortran,objc,obj-c++ --enable-lto --with-plugin-ld --enable-threads=win32 --program-suffix=-win32 --program-prefix=x86_64-w64-mingw32- --target=x86_64-w64-mingw32 --with-as=/usr/bin/x86_64-w64-mingw32-as --with-ld=/usr/bin/x86_64-w64-mingw32-ld --enable-libatomic Thread model: win32 gcc version 6.3.0 20170415 (GCC) GEGL ver.0.4.1 を使用 (ver.0.4.1 上でコンパイル) GLib ver.2.54.2 を使用 (ver.2.54.2 上でコンパイル) GdkPixbuf ver.2.36.11 を使用 (ver.2.36.11 上でコンパイル) GTK+ ver.2.24.31 を使用 (ver.2.24.31 上でコンパイル) Pango ver.1.40.11 を使用 (ver.1.40.11 上でコンパイル) Fontconfig ver.2.12.6 を使用 (ver.2.12.6 上でコンパイル) Cairo ver.1.15.10 を使用 (ver.1.15.10 上でコンパイル)
(In reply to sylvie.alexandre from comment #15) > Bonjour, > > It may be the version of glib : > https://bugzilla.gnome.org/show_bug.cgi?id=796003#c3 > > You may be able to check the glib version, on Windows : > cd [gimp folder]\bin > gimp-2.10.exe --version --verbose > gimp_environnement.txt > start gimp_environnement.txt > > :o) Dear sylvie.alexandre, Thanks for your reply. I forgot the greeting with my previous reply. Please forgive me. And I understood two 'version 2.10.0' (different libraries setting) exist on Windows by the installers. Oh!, It's confusing...
Sorry, Perhaps, My thought is wrong. https://bugzilla.gnome.org/show_bug.cgi?id=795855#c12 - #14 and https://bugzilla.gnome.org/show_bug.cgi?id=795855#c16 My Blog's commenter reported to me that it can not be solved by that method.
So it has been confirmed that this is a regression with Glib 2.54 - at least there are reports that this doesn't happen with Glib 2.53. Remains to be determined where exactly the problem is - whether it is in Glib, GTK+ or GIMP.
*** Bug 796034 has been marked as a duplicate of this bug. ***
And bug 795153 is the glib issue.
(In reply to Michael Schumacher from comment #20) > So it has been confirmed that this is a regression with Glib 2.54 - at least > there are reports that this doesn't happen with Glib 2.53. > > Remains to be determined where exactly the problem is - whether it is in > Glib, GTK+ or GIMP. Maybe glib? https://github.com/Alexpux/MINGW-packages/issues/3584
(In reply to Michael Schumacher from comment #20) > So it has been confirmed that this is a regression with Glib 2.54 - at least > there are reports that this doesn't happen with Glib 2.53. > > Remains to be determined where exactly the problem is - whether it is in > Glib, GTK+ or GIMP. Sorry, I should have said that 2.54 has no issues while the issue was with 2.55 series. I downgraded to 2.54 (which is fine since GIMP requires 2.54.2 or higher). As Elle pointed out, bug report with glib was filed and the issue is supposed to have been resolved with 2.56.2 which does not exist yet. Hope that's helpful.
Thanks all for all the awesome debugging! Following through links from comment 23 (which is indeed definitely the same bugs, reading at descriptions), the upstream bug report is: https://bugzilla.gnome.org/show_bug.cgi?id=795153 As they explain in the report, this is new code, which did not exist hence does not pertain to glib 2.54. And as was noted by Partha, the fix (commit 96904149e20a04066290bc1592469930c2f57ed0) will be in 2.56.2 which is not released. So we can't just bump the requirement. Since it is a pretty bad bug though, what I did instead was adding an additional test for Win32, explicitly forbidding glib 2.56.0 and 2.56.1 (on Win32 only). This way, packagers cannot not know about this issue and will package 2.54.x instead. And it gives us time, for when glib 2.56.2 is out and available in debian testing, then we can bump and remove the additional configure test. commit 8d7f13be186401c4d5c63e6e666b9105ac968dfe (HEAD -> master, origin/master, origin/HEAD) Author: Jehan <jehan@girinstud.io> Date: Sat May 12 23:00:22 2018 +0200 Bug 795855 - File chooser dialogs do not show folders or files for... ... drive roots (e.g. C:\, D:\, ...)) This is a regression of glib 2.56 (not applying to 2.54 since it is new code). It has been fixed recently in what will be 2.56.2 but is not released yet, so we can't just bump the requirement. Since it is a pretty bad bug though, let's add a test specifically for these versions in the configure script so that nobody will package these versions of glib. We can remove this test when we will bump the glib requirement. configure.ac | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
To summarize, we are sure that this doesn't happen with 2.54? The corresponding mailing list thread was referring to 2.53 as the currently available version without that issue...
Pretty sure since we also had several reports of working 2.54. Ex: comment 17, by ShiroYuki who doesn't have the issue (as said in comment 16). Or again Sylvie who says she doesn't have the problem with 2.54.3 but has it with 2.56.0 (comment 15). Also upstream bug 795153, comment 7: > Doesn't apply to glib-2-54, as new stat code didn't exist back then.
Of course, I am only compiling information from what I gathered from various reports here. Yet unless I missed an important piece of information, it looks like we only have to avoid 2.56.0 and 2.56.1.
In my case, this happened after installing the latest version of 2.10 in two computers right on top of a 2.8.something without installing any other version in between. Just for your information and in case it means something to you.
*** Bug 796057 has been marked as a duplicate of this bug. ***
*** Bug 796096 has been marked as a duplicate of this bug. ***
*** Bug 796097 has been marked as a duplicate of this bug. ***
*** Bug 796101 has been marked as a duplicate of this bug. ***
My Blog's commentator says to me. Work Correctly! by the new installer, "gimp-2.10.0-setup-2.exe". From the drive letter, expand correctly. It is FIXED!!! Thanks for all Developers. :) (Tonight, I will try it.)
Cool! Thanks for all the help ShiroYuki, and Sylvie, and Partha, and everyone else involved in this report! :-)
I confirm, fixed in gimp-2.10.0-setup-2.exe installer.
Whisper in a small... GLib is 2.56.1... Now...? (Please refer to Bug 7959254 Comment 9)
Comment 37 Rev. Wrong ; Bug 7959254 > Bug 795925
*** Bug 795989 has been marked as a duplicate of this bug. ***
(In reply to ShiroYuki_Mot from comment #37) > Whisper in a small... > GLib is 2.56.1... Now...? > (Please refer to Bug 795925 Comment 9) I see https://twitter.com/gimp_official 2018/05/16 @GIMP_Official, now. All things clear! It's so Great Jobs!
*** Bug 796175 has been marked as a duplicate of this bug. ***