Created attachment 144538 [details] Happens in every file but attaching it in case something is wrong with it. STEPS TO REPRODUCE 1. Clean install of Krita 5 beta 5 2. Create a new document 3. Select text tool and drag a rectangular area 4. Application hangs EXPECTED RESULT The popup window where text is entered to open, but it does not open. SOFTWARE/OS VERSIONS Windows: 10 Qt Version: 5.12.12
After uninstalling beta 5 and going back to 4.4.8 the issue persists... So this is deeper than just Krita.
I have not done any changes to system installed fonts since I used the tool and it was working. So I believe it is not font related.
Could you please * attach the contents of help->report bug to this bug report * check whether it happens with a clean config (https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration)
Created attachment 144539 [details] SystemLog
Resetting configuration fixed it. Should I upload the backup that it created? Note that this was done on 4.4.8 now.
I suspect that the dialog was shown off screen -- it stores its position in the config files. I don't think we can do much with the config file.
Tried it and Alt+C does make it work so the offscreen position is likely the culprit. With that I restored the config and even Win+LArrow makes it show... Oops. I should have tried that. Sorry
The question now is... Can we detect this and make sure the dialog is always mapped to a valid screen, or not...
I just tried to connect an external display, move the text tool to it, then closed Krita, disconnected the display, opened Krita again and the text tool was correctly displayed on the single monitor... so this is already implemented in some way?
I moved it from left to right (Alt+RArrow), assuming windows handles positions TopRight = [0,0] (which I am just guessing) then the config somehow contained negative values? I cannot reproduce it now...
Yes, it is properly the job of windows to place the dialog correctly.
Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information.