Bug 101826 - HiDPI scaling affects virtual display's resolution
Summary: HiDPI scaling affects virtual display's resolution
Status: RESOLVED MOVED
Alias: None
Product: Spice
Classification: Unclassified
Component: spice-gtk (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Spice Bug List
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-17 22:42 UTC by Zoltán
Modified: 2018-06-03 10:21 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Zoltán 2017-07-17 22:42:20 UTC
When I use Gnome's window scaling, the virtual display's image is scaled up too.
This results in a blurry image on spice-based renderers.

Starting a client (virt-manager or virt-viewer) with the GDK_SCALE=1 environment variable fixes the size of the rendered image, but will result in smaller size for GUI elements, compared to other applications.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868687 for further details.
Comment 1 Zoltán 2017-07-18 06:10:42 UTC
I'd like to add that I can get a correct resolution and sharp picture in virt-viewer if I set the zoom to 50% to compensate a scaling factor of 2, with the downside that it makes the mouse cursor huge in guests.
Comment 2 Victor Toso 2017-07-18 11:12:53 UTC
The issue is related to the widget changing its dimensions which would then change guest's resolution to fit that widget.

See: https://bugzilla.gnome.org/show_bug.cgi?id=782997

You would test it will fullscreen in some virtual workspace and see that it should not change.. because of the above bug.
Comment 3 Zoltán 2017-07-18 13:00:16 UTC
> You would test it will fullscreen in some virtual workspace and see that it
> should not change.. because of the above bug.

That bug seems to be about changing scaling factor while the program's running is not firing events about size change due to it.

This one happens while the scaling factor has been set before startup, and is not changed while it is running.
Comment 4 GitLab Migration User 2018-06-03 10:21:40 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/spice/spice-gtk/issues/29.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.