After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 760567 - GDK screen size does not count for HiDPI on Wayland
GDK screen size does not count for HiDPI on Wayland
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Wayland
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-01-13 07:12 UTC by Ben
Modified: 2018-05-02 16:53 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
test program (195 bytes, text/x-vala)
2016-01-13 07:12 UTC, Ben 		  Details
divide width and height by scale factor (1.10 KB, patch)
2016-10-12 20:48 UTC, Ben 		needs-work Details | Review

Description Ben 2016-01-13 07:12:14 UTC 
Created attachment 318940 [details]
test program

GDK gives me 3200x1800 on wayland but 1600x900 on X

In X we divide by the window scale (https://github.com/GNOME/gtk/blob/master/gdk/x11/gdkscreen-x11.c#L96)

In wayland we don't (https://github.com/GNOME/gtk/blob/master/gdk/wayland/gdkscreen-wayland.c#L173)
Comment 1 Ben 2016-10-12 20:48:03 UTC 
Created attachment 337536 [details] [review]
divide width and height by scale factor
Comment 2 Jonas Ådahl 2016-10-13 02:01:44 UTC 
Review of attachment 337536 [details] [review]:

Is suspect we should rather change the "geometry" of the GdkMonitor instead (as set by gdk_monitor_set_size()). Note that under mutter, whatever monitor geometry set on the screen, it'd still be bogus when there is a scale != 1 since mutter still doesn't handle that properly meaning there is no way to send sane values.
Comment 3 GNOME Infrastructure Team 2018-05-02 16:53:20 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME'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.gnome.org/GNOME/gtk/issues/590.