FS#62676 - [GIMP] always crashes when typing in font size or angle of rotation
Attached to Project:
Arch Linux
Opened by Paul (Ignotum) - Saturday, 18 May 2019, 23:11 GMT
Last edited by David Thurstenson (thurstylark) - Sunday, 10 April 2022, 05:48 GMT
Opened by Paul (Ignotum) - Saturday, 18 May 2019, 23:11 GMT
Last edited by David Thurstenson (thurstylark) - Sunday, 10 April 2022, 05:48 GMT
|
Details
Description:
GIMP crashes --- consistently --- whenever I try to type in a font size or a rotation angle. This is a bug I've noticed with previous versions of GIMP, over a number of years, and on a number of different computers. Additional info: * package version gimp 2.10.10-1 * config and/or log files etc. see attachments * link to upstream bug report, if any Steps to reproduce: 1. Open GIMP. 2. In the menu, choose "File" → "New...". 3. When the "Create a New Image" window appears, click "OK". 4. Click on the Text Tool icon. 5. Click on the canvas. 6. A window appears above the canvas. 6. Click in the window's font size box ("Change size of selected text"). 7. Press backspace or try to type --- GIMP crashes. The same happens when using the rotation tool to rotate a layer: again, all is fine until one attempts to type in an arbitrary rotation angle. (It appears to occur when entering text into a window above the canvas, regardless of what tool one is using, be it text, rotation, scale, etc.) |
This task depends upon
Closed by David Thurstenson (thurstylark)
Sunday, 10 April 2022, 05:48 GMT
Reason for closing: None
Additional comments about closing: Not reproducible by the opener. Assuming fixed upstream.
Sunday, 10 April 2022, 05:48 GMT
Reason for closing: None
Additional comments about closing: Not reproducible by the opener. Assuming fixed upstream.
https://gitlab.gnome.org/GNOME/gimp/issues/1273
I opened an new bug report upstream.
https://gitlab.gnome.org/GNOME/gimp/issues/3743
I've pasted it upstream to the GIMP site.

It was an issue with SCIM which was causing GIMP to crash. I don't know whether it is now resolved.
(I switched to an alternative input method in order to avoid the issue.)