https://bugs.kde.org/show_bug.cgi?id=482790
--- Comment #17 from Raphael Rosch <kdeb...@insaner.com> --- @michael, thanks! As I was typing up some more info to include yesterday my browser crashed, and then I found some more useful info today. So it seems that running kdiff3 with the QT_FONT_DPI env var set to 96 (since the dpi on my machine is 96) fixes it for me as well: > QT_FONT_DPI=96 kdiff3 The variable is somewhere being set to "90", but despite running a grep on what might be my entire filesystem, I cannot find where this variable is being set. The lights went out for a moment today and I had a chance to do a couple of experiments, running a barebones X server with xterm shows that these variables are not set by any of the bash sourced files. Even after launching my panel (mate-panel) from xterm the variables are not set. Konsole is not setting them either and when I run kdiff3 in that environment, the bug does not appear. So something in between sddm (my display manager) and mate-session is loading up these variables --and something else-- and triggering this bug. I say "something else" because unsetting both QT_SCALE_FACTOR and QT_FONT_DPI does not fix it. One or the other has to be set to the values I mentioned for the fix to happen. I really don't know how else to diagnose where the problem is being introduced, but it certainly only affects these two apps on my machine. No amount of searching has let me to find where mate (or sddm?) could be setting these environment variables. -- You are receiving this mail because: You are watching all bug changes.
