GNOME Bugzilla – Bug 165303
incorrect plug-in search path after 2.0 -> 2.2 upgrade
Last modified: 2008-01-15 12:46:28 UTC
Windows version of Gimp 2.2.3 refuses to open Jpeg files, displaying error message "unknown file type" (this is a rough translation, as I'm using a french language version). I checked with some Jpeg files that Gimp 2.0.5 (my previous version)opened and worked with. I made sure that .xcf files in the same directory can be opened by Gimp 2.2.3. I got no other error messsage nor crashes in any way (my version of W2k is quite stable, well protected by anti-virus and firewall). GTK is 2.1.14.
It would be very helpful if you could (1) attach a copy of one of the files that fails to open, and (2) tell us the name of the file, including the full path. Also, GTK can't be 2.1.14, because GIMP 2.2.x requires GTK 2.4.x. If you have multiple versions of GTK+ on your system, it is likely to cause problems, so you should get rid of the older one. (It isn't likely to be the cause of this problem, though.)
I recall a report of someone who fixed this by renaming his personal gimp profile directory (.gimp-2.2 in the user profile directory). Seems like there can be some settings that cause problems. If renaming the directory fixes this (GIMP will create a new profile on the next restart), it would be helpful if you could attach a zippped archive of it to this bug report - unless you got many plug-ins installed there, then you should leave them out and list them seperately.
The Problem has been solved thanks to the above mail from Michael Schumacher : installing Gimp 2.2.3 did not re-create all paths to files (such as brushes, patterns etc) as defined in menu "File/Preferences". Paths to preference files pointed only to my personal user file ("C:\Documents and Settings\Christian\.gimp-2.0" etc) or to "D:\Program Files\GIMP-2.0 ..." Adding new paths such as "D:\Program Files\GIMP-2.2 ..." solved the problem. I hope you can get my clumsy explanations, I must translate from my french menus! Thanks for your help Herzlichsten Dank zu Michael Schumacher für deine Hilfe (setzte mich auf dem Weg)
Removing NEEDINFO because the reporter has provided all necessary information; thank you.
Actually, it should still be NEEDINFO, see my reqeuest for the whole .gimp-2-2 directory in comment #2. This isn't a common problem, it is actually very rare (including this case, it makes two I know of), and the cause for it is still unknown.
Hmm, don't you have bugzilla powers?
No
Created attachment 36597 [details] zip file of my user directoru .gimp-2.2 as requested by Michael Schumacher in comment #2 Regards
Okay, removing NEEDINFO again :-)
> Adding new paths such as "D:\Program Files\GIMP-2.2 ..." solved the problem. GIMP 2.2 is supposed to pick files from the same directory as GIMP 2.0 was installed to. Otherwise migration of user preferences won't work.
Re comment #7: you should have bugzilla powers now ;-)
Was the attachment created after you fixed it or before?
The attachment was made after I fixed it. Regards
Regarding comment #10: So GIMP 2.2 picks the plug-ins from the 2.0 directories, and doesn't add paths to it's own?
The 2.0 and 2.2 plug-in directories are identical (or rather, are supposed to be identical). To clear this point, has the user directory been migrated from a previous GIMP 2.0 installation or was a fresh user installation performed when GIMP 2.2 was started for the first time?
Ok, this explains it - unless the user explicitely installs into the same directory as GIMP 2.0, the paths are not identical. This is the default, AFAIK.
What happened here is that the user changed his/her plug-in search path in the past. This causes the new search path to be written to the gimprc file. When updating to gimp-2.2, the gimprc file is copied over in an attempt to migrate user settings. This caused a problem here since the gimprc contained an explicit plug-in search path. On a typical UNIX installation this would not have been a problem but since Jernej has choosen a different prefix for gimp-2.2 than what gimp-2.0 was installed in, this breaks. The easiest way to work around this problem is probably to change the installer so that gimp-2.2 is installed into the same prefix as gimp-2.0 (after cleaning up the previous installation of course).
Actually, when upgrading Gimp, the installer defaults into the previously- installed directory, so with normal upgrades this shouldn't be a problem. If Gimp 2.0 is uninstalled first, the installer will default into a different prefix (the prefix is constructed automatically by the installer from Gimp's version number - maybe I should ignore the minor version here, and only use major?). The way installer is written, it does not require previous version to be manually uninstalled, as it will automatically remove unneded files.
By installing GIMP 2.2 into the gimp-2.0 directory (after uninstalling what was installed by the gimp-2.0 installer), you would nicely avoid this problem. The API version is still GIMP-2.0.
What's the state of this bug-report? If there are no plans to change the installer, then it should be closed WONTFIX.
Fixed in new 2.2.4 installer.