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 793462 - gnome-terminal doesn't properly adjust back to HiDPI
gnome-terminal doesn't properly adjust back to HiDPI
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Wayland
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2018-02-14 17:51 UTC by Jason Ekstrand
Modified: 2018-05-02 19:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jason Ekstrand 2018-02-14 17:51:48 UTC 
I've got a HiDPI laptop (Dell XPS 13) and I regularly use a low-DPI external monitor (with the laptop lid closed).  When I initially start gnome-terminal on the HiDPI display, everything is fine.  When I plug in the external monitor and close the lid, everything properly goes back to 1x rendering for the lower resolution.  When I unplug the external monitor and go back to using the HiDPI laptop panel, some of my terminal windows figure out that they're back on HiDPI and start rendering at 2x and some don't and they get upscaled and look fuzzy.

If it helps, it seems like the one's that don't properly snap back to 2x are frequently windows that are either maximized or large.  That said, it's somewhat random so I don't know for sure that the size of the window actually matters.
Comment 1 Christian Persch 2018-04-09 09:04:34 UTC 
Does this happen with other gtk+ applications, like evolution or gedit?
Comment 2 Jason Ekstrand 2018-04-09 14:41:14 UTC 
I've never observed with evince or nautilus.  GTK3 based firefox is also mostly ok apart from a plugin issue or two which is most likely a FF bug.  I don't use evolution or gedit on a daily basis.
Comment 3 Jason Ekstrand 2018-04-09 20:33:43 UTC 
Never mind that.  I just observed it in both evince and nautilus. :-)  Sounds like a GTK+ bug.
Comment 4 Christian Persch 2018-04-09 20:50:00 UTC 
-> gtk+
Comment 5 GNOME Infrastructure Team 2018-05-02 19:52:16 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/1031.