Created attachment 9466 [details] 108 DPI screenshot on i586 mga6rc host gx27b with TDE Screenshot windows top to bottom: Mozilla.org's GTK2 Firefox 17 ESR, Mozilla.org's GTK2 Firefox 45 ESR, Mozilla.org's GTK3 Firefox 54, Konsole, tdecmshell X-server. Upstream patch that created the regression: https://git.gnome.org/browse/gtk+/commit/?id=bdf0820c501437a2150d8ff0d5340246e713f73f Wontfixed upstream Gnome bug that would solve problem: [REGRESSION][BISECTED] Recent change breaks HiDPI setup based on calculated or forced DPI https://bugzilla.gnome.org/show_bug.cgi?id=757142 Wontfixed upstream Mozilla bug that might solve problem: [GTK+ 3.18] UI text sizes no longer inherited from Linux system https://bugzilla.mozilla.org/show_bug.cgi?id=1269274 https://bugzilla.opensuse.org/show_bug.cgi?id=1022830 has solution in progress for openSUSE Leap 42.3. To reproduce: 1-open some non-Gnome DE 2-ensure Xorg screen density is materially above 96 DPI 3-ensure Xft.dpi is unset ('xrdb -query | grep dpi' result must be null) 4-open a GTK3 app Actual behavior: 1-GTK3 app UI fonts are undersize Expected behavior: 1-GTK3 app UI fonts match other apps
This should be handled upstream, not asked to revert upstream decisions in all users of gtk+. Upstream wontfix'ed it. In https://bugzilla.gnome.org/show_bug.cgi?id=757142#c5 upstream mentions two files have to be modified instead of 1 before. I fail to see what you're after opening this bugreport with Mageia. Closing with a random resolution.
Resolution: (none) => MOVEDStatus: NEW => RESOLVEDCC: (none) => olav
Improving Olav's /dev/random. ;)
Resolution: MOVED => WONTFIX
To be clear: I find upstream's decision strange at best. I don't get it.
How about reevaluating this? It's working out just fine in openSUSE having reverted upstream's usability regression.
Status: RESOLVED => REOPENEDResolution: WONTFIX => (none)
Created attachment 13303 [details] SeaMonkey 2.53.12 on mga9 Trinity Desktop @120 DPI = mousetype UI No change in 5 years. :(
Created attachment 13304 [details] SeaMonkey 2.53.12 on Fedora 36 on Plasma @120 DPI = same mousetype UI as mga9 No material difference from Mageia 9, except running in current Plasma instead of current Trinity.
Created attachment 13305 [details] SeaMonkey 2.53.12 on openSUSE Tumbleweed Trinity Desktop @120 DPI = UI fonts match the rest of the DE Much better on openSUSE, UI fonts in the GTK app exactly matching the rest of the All three of today's screenshots are from the same PC, the same SeaMonkey profile, and the same SeaMonkey binary from https://ftp.mozilla.org/pub/seamonkey/releases/2.53.12/linux-x86_64/en-US/seamonkey-2.53.12.en-US.linux-x86_64.tar.bz2 The only significant difference between foundations is openSUSE has been patching out the perverse Xft.dpi problem created by GTK in v3.17 five years ago.
(In reply to Felix Miata from comment #4) > How about reevaluating this? It's working out just fine in openSUSE having > reverted upstream's usability regression. There's no registered maintainer for this package now, but since ovitters is about the only one to package it in cauldron, I'll assign this report to him for the reevaluation.
Assignee: bugsquad => olavCC: (none) => marja11Source RPM: libgtk+3_0 => gtk+3.0-3.24.34-1.mga9Version: 6 => Cauldron