Curiosity: is it my specific case, or does Gimp 3 defaults to the dark theme? The icon set of the system theme honestly looks superior, if compared to the dark one.
Edit: just tried the non destructive editing. This is a game changer!
It's literally the very first thing I do every time I happen to install Gimp. I could be in the minority, but honestly the dark theme does not give the best first impression.
For icons, Color and Symbolic were combined into the Default icon theme. On the Personalize section of the Welcome dialogue (or in Preferences), if you select Default icon theme and then uncheck "Use symbolic icons if available", it will show the Color icons.
Yeah.. try doing graphics work for 10 hours a day. Your eyeballs will let you know you need dark mode. Blue-light filter glasses help as well, but of course then you have to remember that you're looking at your screen through a color filter (albeit a terribly pale one). :P
I haven't actually looked at 3.0 yet, I'm still trying to figure out how to get 2.8 back, because it auto-updated me out of my old filters and stuff that I needed. :P
There isn't a Debian package available for 3.0.0 for stable, so you must be referring to a package built for Debian sid/unstable. The dependencies for that are likely different from Debian stable so I am unsure how relevant this comment actually is.
The relevance is that if this undoubtedly a bug in GIMP code itself, it would likely also manifest itself in the Debian Sid package or any self-built GIMP on this flavor, or the Microsoft Windows installer as well.
The flatpaks are not based on Debian Sid, so there is a difference here, and the task remaining is to figure out what exactly is the cause.
The installers for Microsoft Windows does for %ProgramFiles%\GIMP 3 by default and won't bother your existing GIMP 2.10.x. You can also grab any older installer from https://download.gimp.org/gimp
On macOS, you got the DMG packages, and you can also get any older ones.
The trickiest platform to get older versions might be Linux distributions - there, the package maintainers may be eager to switch from GIMP 2.10.x to 3.0.0 as soon as possible, as GIMP 2.10 is one of the last packages to e.g. require the old GTK 2.x.
I don't know if they always looked like that because I didn't use them, but I really don't like the default (non-system) themes and it doesn't even seem to play well with adwaita if you choose the system light variant (text doesn't become white when there's a blue bar behind it it stays black no matter what which makes it super hard to see).
Call me crazy and old but but I've always used gtk2's default raleigh theme and it was way easier on the eyes in every way imo lol. Everything sort of blends in together with the (new?) themes.
Thanks for v3.0, good work! But please remove this font shift effect in the menu navigation! It's totally fine to only change the background color of the touched menu item. At the moment everything flips back and forth when you move the mouse over the menu items. It gives you eye cancer...
You can import and export CMYK images (TIFF, JPEG, JPEG-XL, PSD, etc), use soft-proofing with a color profile to simulate how it would look when printed, and see what your colors would be in CMYK. A full CMYK mode is planned for an upcoming release, now that we have all the color space improvements in 3.0.
Wayland and color management is problematic; not only that profiling is not a thing yet (a probably won't be for a long time), but you may easy come to situation when you have double correction.
Fair enough, I'm gonna give 3.0 a few updates to cook and then I will see if it's still super laggy on my end still, it's weird cause the 2.x version runs completely fine but 3.0 lags to the point where even selecting layers makes takes a literal second.
When you compare the performance you are experiencing to the screen recording in the bug I linked to, is it comparable, or worse? If the latter, then it may be useful if you could file a report and attach the performance log as well.
It's not comparable actually, my cpu usage never goes above 8% and out of the 8 gigabytes of memory I gave the program only 2 at most are ever used. My cache is at 0% as well but idk if that's relevant, do you want my pc specs?
looking to revert back, unfortunately. this version crashes when i try to change the brush, and the color invert tool doesn't work the way i need it to for my use case. that said, i'm excited to see the kinks get worked out and will hopefully be able to get back on the v3 wagon with everyone soon
For the brush crash, the workaround is to change the view from icon grid to list in the pop-up before selecting (or to use the brush dockable instead). Unfortunately, the bug only affects certain platforms (flatpak and macOS), so it wasn't observed before release. We're trying to figure out how to replicate and fix it.
As for the color invert, what's the issue you're having?
sorry, this will be a bit hard to explain but i'll do my best. if i had an image with a transparent background and black text, i would rectangle select and invert to get white text. this left the background untouched and only changed the text. what was happening last night is that the text and the background would flip, so i'd end up with a black rectangle and transparent text. i figured this was probably intentional, but it just isn't what i need for my use case. is there maybe a different command that would achieve what i was doing before?
it's happening a bit differently now, i don't get the big black rectangle anymore but the invert is still a bit wonky for lack of better words. the exact image was class material so i can't share that one, but here's a video of it on a different file: https://imgur.com/a/mKLQR5T
this image was just a screenshot from a google doc. my exact steps were: fuzzy select, delete, rectangle select, color to alpha, invert. in the previous version, these steps would result in very clean white text
This seems to be some undesired interaction between the still active Color to Alpha NDE filter and the following invert.
If you merge that filter before the final invert - click on the layer's fx icon in the Layer dialog, and choose merge from the dialog which pops up - then you get the old behavior.
I am curious why you are doing it in this order - shouldn't inverting first and then using color to alpha on black get you the same result with just two steps?
thank you, i'll try that when i get home! i do it in that order because ive got keybinds for both invert and C2A, and it's just a little quicker than selecting black on C2A, or at least it feels that way. unless there's a way to change that to default to black? plus, old habits die hard lol. regardless, i'll try both and see if it comes out
Well the first crash happened when I tried to add my first layer to a newly created doc with fixed dimensions.. just CTD'd
a reload of gimp didn't CTD.
The second crash happened when I went to apply a blur, I attempted to change my brush and it CTD'd.
Also note, I tried to do a print preview and it doesn't crash but says "An error occurred while trying to print" and "Creating an app info from a command line not scurrently supported"
Hmm. The issue with brushes is a known problem with macOS and Linux flatpaks. We actually just made a fix in source which will be available in the next bugfix release - for now, you can either use the brush dockable to change brushes or switch the view from icon grid to list.
The other two we haven't had reports on. Could you post them to https://gitlab.gnome.org/GNOME/gimp/-/issues ? If there was a stacktrace produced, it'd be great if you could attach that as well.
I opened an image file by right-clicking on it and open with Gimp 3. Gimp loaded, but it got stuck on loading the image and I've had to close the entire thing.
Looks like all my Script-fu scripts are hosed by the new multi-select layer API (and one even crashes GIMP completely). Are there any guides for how to port 2.10 scripts to work with multiple drawables?
So I tried it hoping maybe we can have a Blender 2.8 moment. But no, Gimp is still software made by people who would like to create visuals using command line but want other people to use their software as well so they add some random GUI elements. Wake me up when 4.0 comes
What is going on with the Align tool in 3.0 its funky. Its just not function properly out of the box live V2, putting shit off screen etc. anyone else experience this?
Also how do I reduce the size of my hand/grab mouse icon when grabbing sliders? thx
my alignments go off screen, ticking the various options (which pre v3 never had) dont seem to do anything. I notice it seems to be aligning from the center point of the image see examples.
Just a little bit pissed off about this, actually. I had 2.8.x installed with all of my awesome filters and add-ons. Some of them never got updated for 2,10.x, so I just installed 2.10.36 alongside of it. I use 2.10 for day to day stuff, then revert to 2.8 when I need some of those old-school filters and etc.
A couple of days ago, the notice for 3.0 popped up, and I politely said NO!
Today, I went to open up GIMP 2.8, and I got GIMP 3.0. I cussed under my breath a bit, closed it, and went back to try to open GIMP 2.8, and now I have 2.10.36, 2.10.38 and 3.0 installed.
WHAT IN THE UNHOLY DID YOU GUYS DO TO AUTOUPDATE?!
Win11 64x, Ludicrous specs, more cores and ram than any program can use, backed up by a 4080.
EDIT:
Again, I DID intentionally already have GIMP set up to run two different versions.. Which I doubt you guys support, but I have no idea WHY it did what it did with the auto-update nonsense.
Furthermore, I'm probably going to need some instruction to try to salvage my 2.8.x add-ons and filters, to get them working back under 2.8, without making a nightmare out of trying to reinstall all of them. :P Some of them already took some manual tweaking to get them working in 2.8, so I don't really want to have to try to scratch my head at it and have to sort it all back out again.
EDIT2:
Yeah, I think I'm hosed. Recuva Professional can't find a 2.8 folder under AppData/Roaming/GIMP, so I assume the auto-updater deleted it (or renamed it..?) before installing the new version(s) of GIMP. :'(
I mean.. I'm assuming that 2.10 would have done SOMETHING to the contents of those folders, to prepare them to work in 2.10, yes? I dunno, it's been a while since I set all of that stuff up in 2.8.
The installers in one stable branch remove the previous versions in their branch, simply to prevent the casual user from having e.g. both 2.10.36 and 2.10.38, and not knowing which one is run.
But it just takes copy&paste in Windows Explorer to preserve any installed version - e.g. copy the GIMP 2 directory, paste and rename GIMP 2.10.36, then run the 2.10.38 installer which will replace the GIMP 2 by itself, done.
I would have to check if the 2.10 installers are trying to remove GIMP 2.8, but even if they do so, any files which aren't part of the original 2.8 installers should remain. All the installers back to the 2.4 versions are available from https://download.gimp.org/gimp/, too.
The 3.0.x version from the Microsoft Store is so far the only version to have an auto-updater, but that should leave any other version alone.
Well.. I normally use Classic Start Menu, because I can't stand the Win10-11 menu. I just discovered that Windows is doing it's level best to try to hide the 2.10.36 install, and the 2.10.38 install. If I type "GIMP", it autofills 3.0.0 and tries to not let me see the 2.10.38 version. If I "FIX" the auto-search, it still won't show me the 2.10.36 version. Since it doesn't consider the 2.10.36 version an "App", and won't even show it to me, I'm relatively certain that the Microsoft Store installer is the one that hosed everything.
There's the question whether you installed GIMP for all users or just for your user. This is one case where you can end up with multiple 2.10 versions on one system, for example.
I'm not at all sure how to figure out how I handled it back when I made it dual install 2.8 and 2.10, since the 2.8 install is utterly gone, now. I suppose I could sniff around the registry for leftovers. If the Microsoft Store did bork the auto-update, there ought to be a pile of junk left scattered around the registry.
Currently, the version I installed as a program is 2.10.36. it does not show up in the Win11 Start Menu at all. The 2.10.38 version was installed as an app. It does show up in the Win11 Start Menu, if I make it show me it.
I'm pretty sure somebody could replicate that, and install one version as a program, and one as an app, without depending on the Microsoft Store to bork it up.
Personally, I avoid installing ANYTHING with the Microsoft Store, if I can avoid it. I've ran in to various issues with it, from practically non-uninstallable items to serious privacy concerns related to apps escaping their little MS app sandbox. I actually keep two different commercial uninstallers on my system, to make sure that I can rip anything Microsoft tries to force on me back off of my system, like a rotten tooth.
Any plug-ins and other add-ons would usually go into your personal GIMP profile directory, so these may still be there, and as I wrote, getting all the 2.8 installers is still possible.
Paint Select checkbox not active on the Playground area (GIMP Appimage from GIMP 3 release page).
I have an old appimage (RC2) which has this tool activated.
Anybody has the same problem where right click does not work anymore? Like I make a selection and I want to right click and invert, but right click is not working
Please consider to file an issue report about this at https://gitlab.gnome.org/GNOME/gimp/-/issues/ and provide enough information about your system and what exactly is happening, then someone can have a look at it.
Trying it now. I'm trying to manually enter the dimensions for a rectangle select box on an image, but when I try to enter a 3, for example into the dimensions box, it just zooms on the image. Is there any way to fix this so I don't have to use the +/- to adjust?
I don't see any mention on the release page of what systems its compatible with, I assume Windows 11, but I'm still running Windows 7, is it compatible with Windows 7 still?
Debian Sid has it already, Testing should get it within the usual 10 days, I think (at least that was the usual waiting period last time I checked, but this might not be accurate anymore).
Both can be installed in parallel, GIMP 2.10 uses %ProgramFiles%\GIMP 2 by default, whereas GIMP 3.0 uses %ProgramFiles%\GIMP 3 by default.
Installers within a given stable release branch - e.g. 2.10.34, 2.10.36, 2.10.38 - are designed to remove the previously installed version of the same branch, mostly to prevent casual users from accidentally getting two such versions installed and leading to confusion. Though anyone who know how to copy and paste a directory can easily get around that as well and keep several 2.10 versions around, but that is usually people who are interested in testing e.g. whether a specific problem existed in a specific older version already.
Making pro-quality text got easier, too. Style your text, apply outlines, shadows, bevels, and more, and you can still edit your text, change font and size, and even tweak the style settings.
How is it possible to install 2 copies of GIMP simultaneously? I understand that both are different versions but shouldn't the new version replace the old one? (Windows 10)
No, it shouldn't. This was made especially so that people could have both 2.10 and 3.0.0 alongside each other, as third-party plug-in developers and/or maintainers might take some time to update.
Now that I have installed 3.0 things are working great. The previous one would immediately hung then crush the program whenever I tried to use a gegel Pugin. What kind of details would you like?
The debug output of the crash dialog, if you got one. Then we could check if this was a known crash, based on function names in the stack trace in there, hopefully.
This version seems completely unstable. I always crash to desktop when attempting to save or overwrite any file. And some image files cause ctd just by opening them.
I've tried clean reinstall and rebooting. Nothing helps.
Had to find the gimp 2.10 on a third party site. That version still works without issues for me.
I'm on win11. I'm not computer savvy, so I don't know where that debug output would be kept. All I know is exporting would cause ctd with no error message every time.
I could reinstall and look for it.
This means that the Virustotal service is doing its job: just one of the 68 AV applications is showing a positive, and if you look that one up on Wikipedia, you see that they do not have the best record in any case.
Ya, it's it runs like crap. It's not as responsive as 2.10 and the font scaling is trash. Sorry, but there's no reason to have the text in the rulers and tool options to be disproportionately larger than the rest of the text in the UI.
He’s saying this guy can literally change that by contributing to the project, but instead decided to complain in a forum. The original comment is not being helpful at all.
Someone noticed that GIMP 3.0.0 RC3 feels slower than 2.10, and when asked for more information, provided the suggested performance logs and screen recordings.
64
u/WrtWllms 19d ago