04-06-2026, 01:06 PM (This post was last modified: 04-06-2026, 01:07 PM by HHH.)
Hi
I'm testing the new GIMP 3.0 on Windows, and I’ve run into a persistent issue with the Text Tool. The Problem: Every time I select a font and start typing on the canvas, GIMP automatically overrides my selection and reverts the font to "Sans-Serif". This happens regardless of which font I choose initially. Steps to reproduce:
Select the Text Tool.
Pick any font from the Tool Options (e.g., Segoe UI, Tahoma).
Click on the canvas to create a text box.
Start typing — the font immediately jumps back to "Sans-Serif".
System Info:
GIMP Version: 3.0
OS: Windows 11
Input Method: [english]
I understand that GIMP 3.0 is a major transition to GTK3, so I wanted to report this to see if it's a known regression or if there is a specific workaround for Windows users.
Has anyone else encountered this in the 3.0 builds?
Best regards,
....although from past experience they will (1) ask you to update to Gimp 3.2.2 (2) mark as a duplicate of some other bug and forget about it.
Some of us lurk here.
Since GIMP 3.2.2 is the current version, updating to that helps us know if the problem still persists or has been fixed. I remember hearing that this issue with the text tool was a problem, but I've also heard it's fixed in 3.2. If it's already solved in the latest release, we don't spend time diving into it further instead of one of the other outstanding reports.
I think we do a good mix of new features and bug fixes. Unfortunately, one person's "some fancy stuff that's not (yet) needed." is another person's "basic necessary feature for real user's workflow".
04-07-2026, 08:16 AM (This post was last modified: 04-07-2026, 08:17 AM by rich2005.)
@CmykStudent_ ( lost password did you )
Believe me your good work is appreciated, some small changes like guides outside of canvas can mean more than say a "headline" linked layers. As you guessed I have been "singed" - raise an issue and six months later get an email saying it has been consigned to oblivion and then I wonder why I bothered.
I can say, my linux installation using Gimp 3.2.2 from the 'buntu PPA works as expected. It seems very much a Windows problem, I have seen it reported a few times recently. Is it definitely fixed for Windows in a future release ?
For anyone who can not reproduce the problem, this a 1 min 15 second example. https://youtu.be/-6JEInhlwY0 and the default save on exit is on.
rich2005: No worries! The people who maintain our issue tracker are very helpful in making sure we don't get flooded with duplicate issues. But sometimes they're a bit too quick on the draw, or come off as curt because of their writing style. It's a difficult balance to strike - we don't want to scare off or discourage people from reporting issues, but we also don't want to miss valid reports because they're lost in a sea of empty submissions.
Glad the off-canvas guide fix was helpful! It took me a bit to warm up to link layers, but it's really useful to be able to import images and non-destructively transform them without losing quality. We're hoping to bring that feature over to regular layers as well in 3.4!
I haven't been able to replicate the text issue so far, but I'll keep trying, and I'll see if our other Windows developers can still replicate too.
(04-07-2026, 09:08 PM)CmykStudent_ Wrote: It took me a bit to warm up to link layers, but it's really useful to be able to import images and non-destructively transform them without losing quality. We're hoping to bring that feature over to regular layers as well in 3.4!
Since you talk about layers, do you know if clone layers are still considered? I'm sure I saw these mentioned in the development roadmap, but I can't find these anymore.
(04-08-2026, 01:22 PM)Scallact Wrote: Since you talk about layers, do you know if clone layers are still considered? I'm sure I saw these mentioned in the development roadmap, but I can't find these anymore.
I don't think anyone's specifically working on clone layers at the moment, but there's definitely interest. Jehan's big project for GIMP 3.4 is to make a new XCF format that's based on GEGL buffer. It'll gives us fast autosave (because syncing buffers is apparently very quick), and could lay the groundwork for clone layers (since we'd just have references to the origin GEGL buffer for the clone layers).
(04-08-2026, 01:22 PM)Scallact Wrote: Since you talk about layers, do you know if clone layers are still considered? I'm sure I saw these mentioned in the development roadmap, but I can't find these anymore.
I don't think anyone's specifically working on clone layers at the moment, but there's definitely interest. Jehan's big project for GIMP 3.4 is to make a new XCF format that's based on GEGL buffer. It'll gives us fast autosave (because syncing buffers is apparently very quick), and could lay the groundwork for clone layers (since we'd just have references to the origin GEGL buffer for the clone layers).
Thanks for the heads-up!
At this point, it feels like you're collecting all the fruits of the long GEGL development and integration, and every new feature is gold!!! I'm very glad the xcf format is being worked on!
Since I've already hijacked this thread (sorry OP), I'll just further express my very personal and specific wish: Editable clone layers!! :-)
(Today, 10:08 AM)Scallact Wrote: Since I've already hijacked this thread (sorry OP), I'll just further express my very personal and specific wish: Editable clone layers!! :-)
No promises yet, but I brought this up with our project maintainer Jehan and we might be much closer to this than I thought.
Basically, we could extend the Link Layer code to use a layer (or layers) in the open image as a source - and viola, we'd have clone layers! Then we could make editing one clone layer affect all the others, since they'd share the same source layer. So this may be less involved code-wise (though UI work will remain a challenge as usual).
)