Gimp-Forum.net
GIMP 3.0 RC: Text Tool forces font back to Sans-Serif on Windows - Printable Version

+- Gimp-Forum.net (https://www.gimp-forum.net)
+-- Forum: GIMP (https://www.gimp-forum.net/Forum-GIMP)
+--- Forum: General questions (https://www.gimp-forum.net/Forum-General-questions)
+--- Thread: GIMP 3.0 RC: Text Tool forces font back to Sans-Serif on Windows (/Thread-GIMP-3-0-RC-Text-Tool-forces-font-back-to-Sans-Serif-on-Windows)



GIMP 3.0 RC: Text Tool forces font back to Sans-Serif on Windows - HHH - 04-06-2026

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:
  1. Select the Text Tool.
  2. Pick any font from the Tool Options (e.g., Segoe UI, Tahoma).
  3. Click on the canvas to create a text box.
  4. 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,


RE: GIMP 3.0 RC: Text Tool forces font back to Sans-Serif on Windows - rich2005 - 04-06-2026

No Gimp developers on this forum. You should report as a bug

https://gitlab.gnome.org/GNOME/gimp/-/issues

....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.

There some work-arounds using tool presets or tags and filter here: https://www.gimp-forum.net/Thread-Text-defaults


RE: GIMP 3.0 RC: Text Tool forces font back to Sans-Serif on Windows - MrsP-from-C - 04-06-2026

Quote:....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.

..... and go on working on some fancy stuff that's not (yet) needed.