Bug 125929 - Changing konsole font size produces inconsistent sizes after xrandr resolution switch
Summary: Changing konsole font size produces inconsistent sizes after xrandr resolutio...
Status: RESOLVED FIXED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-20 02:39 UTC by Jukka Laurila
Modified: 2010-01-18 16:29 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jukka Laurila 2006-04-20 02:39:23 UTC
Version:            (using KDE KDE 3.5.2)
Installed from:    Ubuntu Packages
OS:                Linux

To reproduce:

- start konsole
- set X to a low resolution mode using xrandr
- press ctrl-+ to enlarge the font
- press ctrl-- to reduce the font
- set X to a high resolution mode using xrandr
- press ctrl-+ to enlarge the font again

Expected result from last step: font gets bigger.
Actual result: font gets smaller.

Speculation: It seems like when a given font size is needed for the first time, konsole renders it into some cache based on the then-current DPI value of the screen. This cache is then not properly invalidated after the display resolution and DPI is changed with xrandr, and thus the font konsole gets from the cache is of the wrong size after the resolution change. Restarting konsole seems to clear this cache, and font resizing works as it should as long as the resolution stays the same.
Comment 1 Jukka Laurila 2006-04-21 23:25:00 UTC
This turned out to be a bug in Qt. See: http://www.trolltech.com/developer/tasktracker.html?method=entry&id=111388
Comment 2 Robert Knight 2006-08-07 18:07:02 UTC
Confirmed for now, it won't be possible to test the fix until Qt 3.3.7 is released.
Comment 3 Sami Liedes 2010-01-18 16:16:24 UTC
Tested in KDE 4.3.4 and works correctly for me (as also expected per comment #2). Suggest closing this bug.
Comment 4 Kurt Hindenburg 2010-01-18 16:29:18 UTC
Reopen if you can duplicate the issue again.