Now that GIMP has done a major revision, it seems the 32-bit Windows builds are broken again. This happened the last major revision as well and took weeks to resolve. I should have tested it thoroughly before pushing it out. So, GIMP Portable 2.10.0-2, like the 32-bit local install, is basically useless as you can't import, export, or save files. Our choices are:
1. Wait for the GIMP 2.10.2 Windows builds to be posted. This new version was released yesterday. A 64-bit Windows build should follow soon and then the 32-bit build after that. It should be noted that the 32-bit Windows build could still be broken.
2. Update GIMP Portable to the 64-bit build
3. Revert GIMP Portable to the last fully working previous version until the broken 2.10 builds are fully sorted
I'm leaning towards reverting myself.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
Why not do something which will also make packages smaller?
Split GIMP like Chrome into 32 and 64 bit.
Make the 32 Bit the default.
Users who wants 64 Bit will use that.
Once you do that and you gather statistics, in few month you'll know the actual answer to this question as well :-).
As discussed previously, the only reason Google Chrome is split is for legacy reasons. As soon as I have time to rework the launcher and convert password handling to PAL, it'll be joined like Firefox. This topic is specifically about the GIMP issue outlined above with the options outlined above due to the fact that the 32-bit build of GIMP 2.10.0-2 is unusable.
Sometimes, the impossible can become possible, if you're awesome!
64 Bit is a must.
I'd suggest that instead of the torture of downloading 100 MB from SourceForge you will reconsider the split thing.
Regarding Chrome, Well, I don't understand the motivation going against users' wishes, but what can I say...
It is like the official policy here.
Please don't attempt to derail this thread. We've already discussed this at length previously: https://portableapps.com/node/57599 Attempting to bring this up in an unrelated thread will not change the answer or the rationale and time limitations behind the policy.
Sometimes, the impossible can become possible, if you're awesome!
The new GIMP was posted today with both 32-bit and 64-bit builds. I'm going to test before proceeding with anything else.
UPDATE: The 32-bit builds of the new release are still broken. Can't export, save, or open files.
Sometimes, the impossible can become possible, if you're awesome!
My 2 cents...
Since the whole idea of Portable Apps and drives is to be able to use them
on other computers 32bit support is a must since in my experience Enterprise
is still using 32bit extensively (Unlike home users)...Limiting to just 64bit would
limit where you could use your portable apps...I have no problem with a 64bit branch as well...
Just definitely should maintain 32bit alternatives otherwise you're locking yourself
out of some viable portable applications computer locations.
As much as I'd like the features that have been added, I prefer functional builds across systems.
I'm in favour of reverting at this point.
I've reverted the app homepages and the app store/updater listing. It's been announced and detailed here: https://portableapps.com/news/2018-05-21--reverting-gimp-portable-to-2.8.22
Existing users can uninstall the broken newer version and then install GIMP Portable 2.8.22. If you have archived plugins in the newer copy, please manually copy them to a safe location first.
Sometimes, the impossible can become possible, if you're awesome!
I'm not certain if there's a GIMP bug filed for this issue.
If so, the following may be of interest - on my Win 10 Enterprise v.1703 64-bit system, I am able to import a JPG file with GIMP Portable 2.10.0-2, although it locks up trying to export as PNG.