Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 748892 - Incorrect font-size in linux guest after resolution syncing
Incorrect font-size in linux guest after resolution syncing
Status: CLOSED WORKSFORME
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-drv-qxl (Show other bugs)
6.2
All Linux
unspecified Severity high
: rc
: ---
Assigned To: Søren Sandmann Pedersen
Desktop QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-10-25 10:24 EDT by Lubos Kocman
Modified: 2014-06-18 05:14 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-03-10 12:06:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
font size with resoluton 1440x900 set on both client and guest (446.53 KB, image/png)
2011-10-25 10:24 EDT, Lubos Kocman
no flags Details

  None (edit)
Description Lubos Kocman 2011-10-25 10:24:37 EDT
Created attachment 530105 [details]
font size with resoluton 1440x900 set on both client and guest

Description of problem:

Guest system has unusually big font (see screenshot) after automatic resolution sync. 

This issue haven't appeared before as there was bug in userportal or the feature itself was broken.

I guess that this might have been caused by some incorrect dpi settings or something similar.

Version-Release number of selected component (if applicable):

spice-client-0.8.2-7.el6.x86_64
spice-vdagent-0.8.1-2.el6.x86_64
rhev-agent-2.3.16-1.el6.x86_64
xorg-x11-drv-qxl-0.0.14-10.el6.x86_64

How reproducible:


Steps to Reproduce:
1.  client with a single monitor layout is required
2. ensure that spice and rhev agents are installed
3. remove .gnome* related folder in case that you have been using gnome-display-properties on guest
4. (logout | restart) guest && disconnect spice-client (restart is not really required)
5. connect with spice client to a started guest
6. login to gnome trough gdm
7. ensure that resolution on guest is the same as on the client  
Actual results:

font-size in gnome is 1.5 or more bigger than the font-size on the client with the same resolution

Expected results:

font-size shouldn't be changed

Additional info:

"chkconfig spice-vdagentd off && reboot" fixes this issue

After the reboot: starting vdagent in running gnome-session didn't break the font size (even when resolution was synced). While log off -> gdm -> log in after that broke the font size.
Comment 1 Lubos Kocman 2011-10-25 10:25:51 EDT
Usability blocker perhaps?
Comment 2 David Blechter 2011-10-27 16:06:44 EDT
moved to 6.3. Unfortunately, there is no time for even investigation for 6.2
Comment 3 Hans de Goede 2011-11-20 06:13:34 EST
I've been doing some debugging on this, the issue is that Xorg assumes a fixed physical screen size, and calculates this from the initial resolution assuming 96 dpi.

Gnome reads the DPI from Xorg at gnome-session startup and then keeps using the DPI it initially read.

So what happens is:

Scenario a, no initial vdagent
-xorg starts in the vm at 1024x768, calculates a screen size of
 10.66 x 8 Inch
-you log in
-gnome-session starts, reads a DPI of 96 from the X server, and uses that
 for the rest of the session
-you start vdagent, resolution sync changes the resolution to say
 2048x1536, Xorg now calculates a new DPI based on a screen size of 10.66 x 8 Inch
 which gives it a DPI of 192, new apps who read the DPI themselves will see
 this!

Scenario b, vdagent initially running
-xorg starts in the vm at 1024x768, calculates a screen size of
 10.66 x 8 Inch
-gnome-session for gdm starts
 -reads dpi of 96
 -starts spice-vdagent 
  -resolution sync changes the resolution to say
   2048x1536, Xorg now calculates a new DPI based on a screen size of 10.66 x
   8 Inch, which gives its 192 DPI
-you log in
-gnome-session starts, reads a DPI of 192 from the X server, and uses that
 for the rest of the session -> Large fonts.

So I'm afraid there is absolutely nothing the agent can do here to fix this issue.

I'm changing the component to the qxl xorg driver, because *maybe* something can be done there, but I'm not sure if that is the case at all.
Comment 5 Suzanne Yeghiayan 2012-02-14 18:18:38 EST
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 6 Lubos Kocman 2012-10-29 05:21:58 EDT
Marian is this still actual? I don't think that we still have this problem.
Comment 7 Andrew Cathrow 2013-03-10 12:06:37 EDT
This doesn't appear to be a problem in rhel6.4
Please re-open if this isn't the case.

Note You need to log in before you can comment on or make changes to this bug.