New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 66 users

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2015
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Regression

Blocking:
issue 517549

Restricted
  • Only users with EditIssue permission may comment.



Sign in to add a comment

[Linux] REGRESSION: Chrome 43 browser font magnification/scaling issue

Reported by gregwallace@google.com, Jun 9 2015

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.30 Safari/537.36

Steps to reproduce the problem:
1. Attempted reboot of system
2. Incognito mode
3. Reset settings
4. Ensure no accessibility settings have been turned on

What is the expected behavior?
Browser should not be scaled to unreasonable proportions

What went wrong?
Rebooted laptop, launched chrome and everything is magnified. Can't be fixed using settings. See attached screenshot.

Did this work before? Yes Earlier today before reboot of system.

Chrome version: 43.0.2357.124  Channel: stable
OS Version: Ubuntu 14.04.1 LTS
Flash Version: Shockwave Flash 18.0 r0

Please feel free to ping me for logs etc. gregwallace@

 
Showing comments 31 - 130 of 130 Older

Comment 31 by jrave...@gmail.com, Jun 10 2015

So I was able workaround this issue by adding the following to google-chrome start:

--high-dpi-support=1 --force-device-scale-factor=1

I'm using Chrome 43.0.2357.124 on Ubuntu 15.04 kernel 4.0.  This issue only started happening when https://crrev.com/32ac9f15d6b11556611d2c86849740f8fb921d32 was merged to google-chrome stable.

This is really a serious regression and must be reverted or fixed ASAP.
KI raised for visibility: https://gutsv3.corp.google.com/#ticket/16770588

Comment 34 by mmoss@chromium.org, Jun 10 2015

What about that commit?

Comment 35 by jrave...@gmail.com, Jun 10 2015

That is the commit that was merged into chrome-stable that is causing this regression.

Comment 36 by jrave...@gmail.com, Jun 10 2015

Sorry, I'm getting my commits confused.  My bad.  It's this commit that I meant to refer to:

https://chromium.googlesource.com/chromium/src/+/1e83acd552618ab337d286187ed23d84434bd122

Comment 37 by mmoss@chromium.org, Jun 10 2015

The fix for that is already in the commits referenced in #29 and #30.

Comment 38 by dhw@chromium.org, Jun 10 2015

 Issue 498805  has been merged into this issue.

Comment 39 by dhw@chromium.org, Jun 11 2015

 Issue 491597  has been merged into this issue.
Issue 498808 has been merged into this issue.
Issue 498693 has been merged into this issue.
Labels: TE-Verified-43.0.2357.125 TE-Verified-M43
Verified the above issue on Ubuntu 14.04, with chrome version '43.0.2357.125' and it is working as intended. No font enlargement/scaling issue observed. Below are the few scenario checked.

Scenario -1
1. Launch chrome Navigate to few websites.
2. Exit and relaunch chrome 
3. Observe the address bar/ menu bar font/size.

Scenario -2
1.Launch Incognito mode.
2.Navigate to few website
3.Observe the address bar/ menu bar font/size.

3.Scenario -3 (Continue were I left off, option should be checked)
1. Launch chrome and navigate to few website.
2. Reboot system and launch chrome.
3. Observe the address bar/ menu bar font/size.

Hence marking the above issue as TE-Verified-43.0.2357.125.

Thank you!
Release 43.0.2357.125 (64-bit) also verified as working Dell XPS Ubuntu Edition (2013 model), 13" full-hd display. Ubuntu version: 15.04.
Nice, thanx

Comment 44 by mmoss@chromium.org, Jun 11 2015

Status: Started
OK. I'm going to leave this open for a little bit, so that anybody who hasn't upgraded yet will hopefully find it, rather than filing more new bugs.

If you're coming here for the first time, the fix is to upgrade to the just-released 43.0.2357.125 version.

Comment 45 by jrave...@gmail.com, Jun 11 2015

Also confirmed 43.0.2357.125 fixes the issue on Ubuntu 15.04.  Thanks for the quick turn around!  
mmoss@, thank you for working on fix, and sorry for regression caused by my revert.

I looked into more details and it looks like this is happening to users who has physical (not configured) DPI higher than 144dpi, and many FHD laptops fall into this category. My environment happened to have 96dpi display and I didn't notice this difference. My apologies.

The new version should use the font scale configured in gtk-xft-dpi, so it should stay 1.0 as long as a user don't change the font scale configuration.

Issue 499529 has been merged into this issue.

Comment 48 by Deleted ...@, Jun 11 2015

Being a developer myself I dont often comment on bugs.
I think you should be embarrassed at releasing a stable version with this regression.. although I think calling it a regression is being generous..
Thanks for fixing it quickly.

Comment 49 by van...@gmail.com, Jun 11 2015

Yeah, it's pretty strange it wasn't catched in Beta or even Unstable

Comment 50 by mmoss@chromium.org, Jun 12 2015

Status: Fixed
FWIW, the problems were caught earlier, but the patches were inadvertently not merged to the stable build when they were merged to beta and unstable (hence why beta and unstable aren't currently broken). Stuff happens :(

Anyhow, people are obviously getting updated and things look good, so I'm going to close now.

Comment 51 by fergal@google.com, Jun 12 2015

mmoss@, stuff happens but I'm really curious how a stable candidate could
have made it out when the problem is immediately noticeable on startup. Any
kind of human testing or screenshot diffing would have caught this.

Comment 52 by fergal@google.com, Jun 12 2015

mmoss@, stuff happens but I'm really curious how a stable candidate could
have made it out when the problem is immediately noticeable on startup. Any
kind of human testing or screenshot diffing would have caught this.
How can I get the new version? I'm on 43.0.2357.124. On the main menu I don't get any link for an update. On chrome://chrome/ I also don't see any link to relaunch or get new version.
#53 You are not writing which Linux distro you are using but if it is Ubuntu just lauch software updater manually. It is usually set to check automatically once a day.
It was 14.04. OK, after following your instructions and relaunching manually, it worked
fergal, re: 51 and 52: I’m somewhat baffled by that as well. I was running the dev/beta version on my machine, but on hi-dpi machines it just works, and on machines which have their DPI set to 96, it just works as well (for unrelated reasons, I always configure the DPI explicitly).

I’m not sure why other people (don’t we have a group of testers?) didn’t spot this issue before the stable release went out, though.
The new release seems solve the problem. However there is one remaining problem I don't know whether it is kept intentionally.
Compared to chromium Version 43.0.2357.81 Ubuntu 15.04 (64-bit) and old (good) version of chrome on Ubuntu, the space of bookmark bar surrounding the folders is larger than those on chromium. So are tabs. This is also the case for bookmark entries and setting menu. The space between each bookmark entry and settings is large. 
So basically everything looks compact on chromium, but loose on chrome. 

Comment 58 Deleted

After installing the update 43.0.2357.125 the main interface size seems to be fine, still the developer tools are way too large (see screenshot attached)
Bildschirmfoto vom 2015-06-12 11:51:57.png
215 KB View Download

Comment 60 by Deleted ...@, Jun 12 2015

I have an issue with Versione 43.0.2357.125 (64-bit) on KDE (kubuntu 15.04) and Linux Mint MATE (mate 1.10)
See attached file

schermata1.jpeg
153 KB View Download
Schermata.png
235 KB View Download

Comment 61 by d...@bitbod.com, Jun 12 2015

I still have this issue on version 43.0.2357.125, on Ubuntu 12.04.
Yeah its not fixed :(

Kubuntu 14.04 here.

Comment 64 by kwpol...@gmail.com, Jun 13 2015

Not fixed in Version 45.0.2427.7 dev (64-bit) on Arch Linux.

Comment 65 by mmoss@chromium.org, Jun 13 2015

For anyone who is still seeing scaling issues with the .125 release, please do the following:

1) Open chrome://chrome and verify that you're actually running .125. If Chrome didn't shutdown completely, you might still be running a previous .124 process.

2) If you are running .125 and things still look wrong, make sure you're not running with any of the previous workarounds, like --force-device-scale-factor. You can see what flags are active on the chrome://version page under "Command Line:".

3) If no previous workarounds are in use and it still looks wrong, trying running with one or both of the following flags and let us know if that fixes the issue:
  --high-dpi-support=1
  --force-device-scale-factor=1

4) If none of that works, please upload a screenshot. If you can do a side-by-side screenshot comparing the same page rendered in .125 and in a version of Chrome (beta or unstable) which displays properly, that would be even better.

5) If you can, please also build and run https://github.com/derat/font-config-info and report the output, or at least report the output from the following commands:
  xdpyinfo | grep -B 1 resolution
  xrandr --current

If you think you are seeing this issue, but you are running ANY VERSION OTHER THAN 43.0.2357.125, try the steps above and collect the information described, but please file a separate bug. This bug is specifically about a regression in the stable channel build.

Comment 66 by mmoss@chromium.org, Jun 13 2015

suisanahta, please file a new bug (with the details you posted previously). That sounds like it might be a legitimate issue, but specific to dual-monitor environments, and it might not get noticed if you post to a closed (and more generic) bug.
Reported a-fresh for dual-monitor config as https://code.google.com/p/chromium/issues/detail?id=500201

As noted in there using --force-device-scale-factor=1 does work around the issue on .125 for me currently (I was definitely on .125, did not have any other command-line options already that might have affected it).
Adding --force-device-scale-factor=1 fixes this issue. I am using Debian Sid with KDE4.

xdpyinfo | grep -B 1 resolution
  dimensions:    1920x1200 pixels (650x406 millimeters)
  resolution:    75x75 dots per inch

xrandr --current
Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 16384 x 16384
VGA-0 disconnected (normal left inverted right x axis y axis)
DVI-D-0 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
   1920x1200     59.95*+  59.88  
   1680x1050     59.95  
   1600x1200     60.00  
   1600x1000     60.00  
   1280x1024     85.02    75.02    60.02  
   1280x960      60.00  
   1152x720      60.00  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   640x480       75.00    59.94  
HDMI-0 disconnected (normal left inverted right x axis y axis)

./font-config-info 
Running at Sat Jun 13 21:00:34 2015

GtkSettings:
gtk-font-name        "Droid Sans  9"
gtk-xft-antialias    1 (yes)
gtk-xft-hinting      1 (yes)
gtk-xft-hintstyle    "hintmedium"
gtk-xft-rgba         "rgb"
gtk-xft-dpi          98304 (96,00 DPI)

GTK 2.0 styles:
GtkLabel             "Droid Sans 9"
GtkMenuItem          "Droid Sans 9"
GtkToolbar           "Droid Sans 9"

GSettings (org.gnome.desktop.interface):
font-name            "Cantarell 11"
text-scaling-factor  1,00

X11 display info:
screen pixels        1920x1200
screen size          650x406 mm (75,03x75,07 DPI)

X resources (xrdb):
Xft.antialias        "1"
Xft.hinting          "1"
Xft.hintstyle        "hintmedium"
Xft.rgba             "rgb"
Xft.dpi              "96"

XSETTINGS:
bash: dump_xsettings: command not found
Install dump_xsettings from https://code.google.com/p/xsettingsd/
to print this information.

Fontconfig (Droid Sans 9):
requested size       9 points
family               Droid Sans
pixelsize            12,00 pixels
size                 9 points
antialias            1
hinting              1
autohint             1
embeddedbitmap       0
hintstyle            2 (medium)
rgba                 1 (rgb)

Fontconfig (default pattern):
antialias            [no match]
hinting              1
autohint             1
embeddedbitmap       1
hintstyle            3 (full)
rgba                 1 (rgb)

Fontconfig (default match):
family               DejaVu Sans
pixelsize            16,00 pixels
size                 12 points
antialias            1
hinting              1
autohint             1
embeddedbitmap       0
hintstyle            2 (medium)
rgba                 1 (rgb)

Fontconfig (non-family/size defaults):
antialias            1
hinting              1
autohint             1
embeddedbitmap       0
hintstyle            2 (medium)
rgba                 1 (rgb)

Comment 69 by hgab...@gmail.com, Jun 13 2015

If one files a new report regarding this bug on .125 please let us know here. I'm also facing this (I have dual monitors) and the --force-device-scale-factor=1 indeed works(around).

Comment 70 by mmoss@chromium.org, Jun 13 2015

hgabreu: The bug for dual-monitor configurations is Issue 500201.

Comment 71 by mmoss@chromium.org, Jun 13 2015

Addendum to instructions in #65:

6) If possible, please also test with google-chrome-beta and google-chrome-unstable and report if those have the same scaling issues, or if it appears fixed in those versions.
google-chrome-beta 44.0.2403.39 and google-chrome-unstable 45.0.2427.7 also have that issue. I need to use --force-device-scale-factor=1 to fix it.

Comment 73 by Deleted ...@, Jun 14 2015

.125, same issues.

xdpyinfo | grep -B 1 resolution
  dimensions:    1844x1037 pixels (1018x572 millimeters)
  resolution:    46x46 dots per inch

xrandr --current
Screen 0: minimum 8 x 8, current 1844 x 1037, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
DVI-I-2 disconnected (normal left inverted right x axis y axis)
DVI-I-3 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected primary 1844x1037+0+0 (normal left inverted right x axis y axis) 1600mm x 900mm
   1920x1080      60.0*+   60.0     59.9     50.0     30.0     25.0     24.0     60.1     60.0     50.0  
   1280x1024      60.0  
   1280x720       59.9     50.0  
   1024x768       60.0  
   800x600        60.3  
   720x576        50.0  
   720x480        59.9     60.1  
   640x480        60.0     59.9     59.9  


Screenshot from 2015-06-14 14:18:00.png
232 KB View Download
.124 no issues

.125, beta and unstable all have the problem. 
--high-dpi-support=1 does not fix the problem
--force-device-scale-factor=1 fixes the problem

OS: Kubuntu 14.04
snapshot20n.png
1.3 MB View Download
Still experiencing the issue -- fixed only with additional parms.

Version 43.0.2357.125 (64-bit)

Ubuntu 15.04  
3.19.0-20-generic #20-Ubuntu SMP Fri May 29 10:10:47 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

$ xdpyinfo | grep -B 1 resolution
  dimensions:    1280x1024 pixels (338x270 millimeters)
  resolution:    96x96 dots per inch

$ xrandr --current
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 4096 x 4096
VGA-0 connected 1280x1024+0+0   
   1280x1024      60.0 +   75.0*

Updated last night and back to normal for me

Comment 77 by Deleted ...@, Jun 17 2015

Same issue for me with Version 43.0.2357.125

Everything is really BIG.

3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux

Linux Mint 17 32 bit 

Have tried the first three points of advice in post #65 with no resolution.

sorry, that is all I can do at present, have spent an hour and a half trying to resolve this and setup Firefox in the mean-time. I need Chrome for iView (Flash). 


Comment 78 by Deleted ...@, Jun 17 2015

To add to the previous post, I should say that my resolution for this laptop via my loungeroom TV is 1366 by 768. I haven't updated my main desktop yet which is 1920 by 1080.

Until the latest Chrome update above, Chrome has always been great on my 1366 by 768 loungeroom laptop/TV. 

Comment 79 by vkr...@gmail.com, Jun 17 2015

Version 43.0.2357.124 was fine. Updated this morning to 43.0.2357.125 - bad fonts are back, and the menu (with New Tab, Settings, etc) seems to be placed randomly on the screen depending on which of the two monitors the chrome window is and what is the size of the chrome windows. 

--force-device-scale-factor=1 fixes font sizes, menu location is still random.

$ xdpyinfo | grep -B 1 resolution
  dimensions:    3840x1080 pixels (1060x301 millimeters)
  resolution:    92x91 dots per inch

$ xrandr --current
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 16384 x 16384
VGA-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 525mm x 297mm
   1920x1080     60.00*+
   1680x1050     59.95  
   1600x1200     60.00  
   1600x900      60.00  
   1440x900      59.89  
   1400x1050     59.98  
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1280x800      59.81                                                                                                                                                                                                                       
   1024x768      75.03    70.07    60.00                                                                                                                                                                                                     
   800x600       75.00    72.19    60.32    56.25                                                                                                                                                                                            
   640x480       75.00    72.81    59.94                                                                                                                                                                                                     
DVI-D-0 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 525mm x 297mm                                                                                                                                                  
   1920x1080     60.00*+                                                                                                                                                                                                                     
   1680x1050     59.95                                                                                                                                                                                                                       
   1600x1200     60.00                                                                                                                                                                                                                       
   1600x900      60.00                                                                                                                                                                                                                       
   1440x900      59.89                                                                                                                                                                                                                       
   1400x1050     59.98                                                                                                                                                                                                                       
   1280x1024     75.02    60.02                                                                                                                                                                                                              
   1280x960      60.00                                                                                                                                                                                                                       
   1280x800      59.81                                                                                                                                                                                                                       
   1024x768      75.03    70.07    60.00                                                                                                                                                                                                     
   800x600       75.00    72.19    60.32    56.25                                                                                                                                                                                            
   640x480       75.00    72.81    59.94                                                                                                                                                                                                     
HDMI-0 disconnected (normal left inverted right x axis y axis)

$ ./font-config-info 
Running at Wed Jun 17 10:44:50 2015

GtkSettings:
gtk-font-name        "Tahoma Regular 8"
gtk-xft-antialias    1 (yes)
gtk-xft-hinting      1 (yes)
gtk-xft-hintstyle    "hintfull"
gtk-xft-rgba         "rgb"
gtk-xft-dpi          98304 (96.00 DPI)

GTK 2.0 styles:
GtkLabel             "Tahoma 8"
GtkMenuItem          "Tahoma 8"
GtkToolbar           "Tahoma 8"

GSettings (org.gnome.desktop.interface):
font-name            "Cantarell 10"
text-scaling-factor  1.00

X11 display info:
screen pixels        3840x1080
screen size          1060x301 mm (92.02x91.14 DPI)

X resources (xrdb):
Xft.antialias        "1"
Xft.hinting          "1"
Xft.hintstyle        "hintfull"
Xft.rgba             "rgb"
Xft.dpi              "96"

XSETTINGS:
bash: dump_xsettings: command not found
Install dump_xsettings from https://code.google.com/p/xsettingsd/
to print this information.

Fontconfig (Tahoma 8):
requested size       8 points
Fontconfig warning: "/home/vadymk/.config/fontconfig/fonts.conf", line 37: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "~/.fonts.conf", line 37: Having multiple values in <test> isn't supported and may not work as expected
family               Tahoma
pixelsize            8.33 pixels
size                 8 points
antialias            0
hinting              1
autohint             0
embeddedbitmap       0
hintstyle            3 (full)
rgba                 1 (rgb)

Fontconfig (default pattern):
antialias            1
hinting              1
autohint             0
embeddedbitmap       1
hintstyle            3 (full)
rgba                 5 (none)

Fontconfig (default match):
family               Arial
pixelsize            12.50 pixels
size                 12 points
antialias            1
hinting              1
autohint             1
embeddedbitmap       0
hintstyle            3 (full)
rgba                 1 (rgb)

Fontconfig (non-family/size defaults):
antialias            1
hinting              1
autohint             1
embeddedbitmap       0
hintstyle            3 (full)
rgba                 1 (rgb)

See also https://code.google.com/p/chromium/issues/detail?id=490398
chrome_expected_fonts.png
1.0 MB View Download
chrome_bad_fonts.png
943 KB View Download

Comment 80 by Deleted ...@, Jun 17 2015

I entered this into terminal this morning:

google-chrome --high-dpi-support=1 --force-device-scale-factor=1

All seems good. Back to normal for me on Mint 17, 32 bit, Hisense DVD TV monitor 1366 by 768.

Maybe I forgot to close down all instances of Chrome yesterday when trying this in terminal. Will let you know how it goes.

I guess an update will be coming soon?
Labels: TE-Verified-43.0.2357.127
Verified the above issue on Ubuntu 14.04, with chrome version '43.0.2357.127' & no font enlargement/scaling issue observed. Also, verified the above issue with the steps mentioned in comment#42. Hence marking the same as TE-Verified-43.0.2357.127.

Attach is the print-screen for the same.
Font on stable.png
788 KB View Download

Comment 82 by vkr...@gmail.com, Jun 19 2015

Can I download and try '43.0.2357.127' in my environment?
@#82 Apparently not yet. The data from omahaproxy.appspot.com states that the current stable version (checked all operating systems) is lower than .127.

Comment 84 by Deleted ...@, Jun 20 2015

I have the problem with chrome version 43.0.2357.125 in ubuntu 14.04
using "google-chrome --high-dpi-support=1 --force-device-scale-factor=1" fixes the problem, but I also discovered that when using the X.org X server driver for the video card the problem does not happen but is does with the NVIDIA legacy driver version 173.14.39
Labels: TE-Verified-43.0.2357.130
Verified the issue on Ubuntu 14.04 using M 43.0.2357.130 and its working fine.
Did not see any font enlargement/scaling issue while browsing in normal mode, incognito mode and after reboot of the system too its working fine.

Comment 86 by Deleted ...@, Jun 23 2015

Latest update and no change on my system. 43.0.2357.130 still exhibits over sized menus and everything looks super sized. 

When I enter this into terminal google-chrome --force-device-scale-factor=1 it all works fine. 

This is starting to get a bit annoying. Chrome has worked perfectly on this system until recent weeks.

Attached is my hardware profile.
hardwareprofile.html
69.7 KB View Download

Comment 87 Deleted

Comment 88 by Deleted ...@, Jun 23 2015

I just updated my main desktop and all is well with the latest Chrome update so it looks like its a conflict with the NVIDIA driver in Linux on my other PC, the laptop.

I can only use the latest NVIDIA driver on my laptop as nothing else works when I want to use the lounge room digital TV screen.

I also tried the X.org X server driver for the video card instead of Nvidia and latest Chrome worked fine, like it used to but I can't use this driver when connecting my digital TV to the laptop as the TV display won't work.

Up until the last two updates of Chrome, it always worked with the NVIDIA driver in Linux Mint on my laptop.

Comment 89 by Deleted ...@, Jun 23 2015

I've downgraded to Version 43.0.2357.81 on my Mint 17 system and am using the laptop with the digital TV connected with no problems at all. So, whatever the issue is, its not apparent in this version.

Chrome is perfect in this version using the NVIDIA driver in Linux Mint.

Comment 90 by vkr...@gmail.com, Jun 23 2015

Just upgraded to 43.0.2357.130. Same experiences as #86 and no improvement over what was reported in #79.
I can confirm that Chrome 43.0.2357.130 is still broken.
I can confirm that Chrome 43.0.2357.130 is still broken.

Comment 93 by Deleted ...@, Jun 23 2015

The issue continues for me on version 43.0.2357.130 on Ubuntu 14.04 with the NVIDIA legacy driver version 173.14.39
Please also supply the output of https://github.com/derat/font-config-info, otherwise we don’t have enough information to figure out what the problem is.

Comment 95 by Deleted ...@, Jun 23 2015

The issue continues for me on version 43.0.2357.130 on Ubuntu 14.04 with the NVIDIA legacy driver version 173.14.39

Output of font-config-info:
/usr/share/themes/Crunchy-blue/gtk-2.0/gtkrc:745: No se ha podido encontrar el archivo «include»: «apps/ubuntuone.rc»
GtkSettings:
gtk-font-name        "Ubuntu 11"
gtk-xft-antialias    1 (yes)
gtk-xft-hinting      1 (yes)
gtk-xft-hintstyle    "hintslight"
gtk-xft-rgba         "rgb"
gtk-xft-dpi          98304 (96.00 DPI)

GTK 2.0 styles:
GtkLabel             "Ubuntu 11"
GtkMenuItem          "Ubuntu 11"
GtkToolbar           "Ubuntu 11"

GSettings (org.gnome.desktop.interface):
font-name            "Ubuntu 11"
text-scaling-factor  1.00

X11 display info:
screen pixels        1024x768
screen size          302x232 mm (86.12x84.08 DPI)

X resources (xrdb):
Xft.antialias        "1"
Xft.hinting          "1"
Xft.hintstyle        "hintslight"
Xft.rgba             "rgb"
Xft.dpi              "96"

XSETTINGS:
bash: dump_xsettings: orden no encontrada
Install dump_xsettings from https://code.google.com/p/xsettingsd/
to print this information.

Fontconfig (Ubuntu 11):
requested size       11 points
family               Ubuntu
pixelsize            11.46 pixels
size                 11 points
antialias            1
hinting              1
autohint             0
embeddedbitmap       1
hintstyle            1 (slight)
rgba                 [no match]

Fontconfig (default pattern):
antialias            [no match]
hinting              1
autohint             0
embeddedbitmap       1
hintstyle            3 (full)
rgba                 [no match]

Fontconfig (default match):
family               DejaVu Sans
pixelsize            12.50 pixels
size                 12 points
antialias            1
hinting              1
autohint             0
embeddedbitmap       1
hintstyle            1 (slight)
rgba                 [no match]

Fontconfig (non-family/size defaults):
antialias            1
hinting              1
autohint             0
embeddedbitmap       1
hintstyle            1 (slight)
rgba                 [no match]

Comment 96 by Deleted ...@, Jun 24 2015

I am not sure how to install that font config program on my Linux Mint 17 32 bit OS. If someone can help with this, I am willing to look at it.

Comment 97 by vkr...@gmail.com, Jun 24 2015

The output from font-config-info on my desktop is in comment #79.

Comment 98 by Deleted ...@, Jun 25 2015

The issue continues for me on version 43.0.2357.130 (64-bit) on Kubuntu 15.04 with the NVIDIA 304 driver (nvidia 304.125)

marco@kubuntu:~/font-config-info$ /home/marco/font-config-info/font-config-info
Running at Thu Jun 25 11:22:12 2015

GtkSettings:
gtk-font-name        "Oxygen-Sans Sans-Book 10"
gtk-xft-antialias    1 (yes)
gtk-xft-hinting      1 (yes)
gtk-xft-hintstyle    "hintslight"
gtk-xft-rgba         "rgb"
gtk-xft-dpi          98304 (96,00 DPI)

GTK 2.0 styles:
GtkLabel             "Oxygen-Sans Sans-Book 10"
GtkMenuItem          "Oxygen-Sans Sans-Book 10"
GtkToolbar           "Oxygen-Sans Sans-Book 10"

GSettings (org.gnome.desktop.interface):
font-name            "Cantarell 11"
text-scaling-factor  1,00

X11 display info:
screen pixels        1920x1080
screen size          938x528 mm (51,99x51,95 DPI)

X resources (xrdb):
Xft.antialias        "1"
Xft.hinting          "1"
Xft.hintstyle        "hintslight"
Xft.rgba             "rgb"
Xft.dpi              "96"

XSETTINGS:
bash: dump_xsettings: comando non trovato
Install dump_xsettings from https://code.google.com/p/xsettingsd/
to print this information.

Fontconfig (Oxygen-Sans Sans-Book 10):
requested size       10 points
family               DejaVu Sans
pixelsize            10,42 pixels
size                 10 points
antialias            1
hinting              1
autohint             0
embeddedbitmap       1
hintstyle            1 (slight)
rgba                 1 (rgb)

Fontconfig (default pattern):
antialias            [no match]
hinting              1
autohint             0
embeddedbitmap       1
hintstyle            3 (full)
rgba                 [no match]

Fontconfig (default match):
family               DejaVu Sans
pixelsize            12,50 pixels
size                 12 points
antialias            1
hinting              1
autohint             0
embeddedbitmap       1
hintstyle            1 (slight)
rgba                 1 (rgb)

Fontconfig (non-family/size defaults):
antialias            1
hinting              1
autohint             0
embeddedbitmap       1
hintstyle            1 (slight)
rgba                 1 (rgb)


I can reproduce this issue in Chrome 43.0.2357.130. My comment #68 is still valid. I am also using NVIDIA Driver, version 346.72.

Maybe this option from my xorg.conf is relevant:
Option          "UseEdidDpi"            "false"

Regression confirmed on Linux Mint 17.1 KDE using the NVidia driver on dual monitor configuration (switching on single monitor didn't solve the issue).

Note that there is no problem with older version 43.0.2357.65-1_amd64.

I'm also attaching font-config-info dump, hope it helps.

fonts.txt
2 bytes View Download
On an XPS 13 running Debian, the UI was properly scaled ever since Chromium 43.x. However since upgrading from 43.0.2357.124 to 43.0.2357.130, the UI has regressed back to extremely small text and an unusable UI. 
The problem seems to occur when switching back and forth from a standard monitor to a Hi-Res monitor. 

Problem reproduced on Ubuntu 14.04 / Chrome Version 43.0.2357.130 (64-bit) on a Dell XPS 13
When I set DPI of my monitor to 96x96, then Chrome looks good. With smaller DPI Chrome is scaled up. NVIDIA Driver sets my DPI to 86x85 with default settings - so that's the reason.

As a workaround put this line into your xorg.conf (Section "Screen"):
Option "DPI" "96 x 96"

Comment 104 by Deleted ...@, Jul 5 2015

I can confirm that the solution suggested in comment #103 of adding the line: Option "DPI" "96 x 96" to the xorg.conf file solved the problem for me on Ubuntu 14.04 
I also confirm that the solution in #103 works in Linux Mint 17.1 KDE (Ubuntu-based), so THANKS! However, forcing me to change my native DPI in order to fix Chrome is a WORKAROUND and not a real FIX!
--force-device-scale-factor helped me. Chrome 43.0.2357.130 (64-bit), Ubuntu 12.014.

Comment 107 by Deleted ...@, Jul 8 2015

The issue continues for me on version 43.0.2357.132 on Ubuntu 14.04 with the NVIDIA legacy driver version 173.14.39, the solution in comment #103 also works for this version. 
Output of font-config-info after editing the xorg.conf file:
Running at Wed Jul  8 08:54:59 2015

/usr/share/themes/Crunchy-blue/gtk-2.0/gtkrc:745: No se ha podido encontrar el archivo «include»: «apps/ubuntuone.rc»
GtkSettings:
gtk-font-name        "Ubuntu 11"
gtk-xft-antialias    1 (yes)
gtk-xft-hinting      1 (yes)
gtk-xft-hintstyle    "hintslight"
gtk-xft-rgba         "rgb"
gtk-xft-dpi          98304 (96.00 DPI)

GTK 2.0 styles:
GtkLabel             "Ubuntu 11"
GtkMenuItem          "Ubuntu 11"
GtkToolbar           "Ubuntu 11"

GSettings (org.gnome.desktop.interface):
font-name            "Ubuntu 11"
text-scaling-factor  1.00

X11 display info:
screen pixels        1024x768
screen size          271x203 mm (95.98x96.09 DPI)

X resources (xrdb):
Xft.antialias        "1"
Xft.hinting          "1"
Xft.hintstyle        "hintslight"
Xft.rgba             "rgb"
Xft.dpi              "96"

XSETTINGS:
Xft/Antialias        1
Gtk/FontName         "Ubuntu 11"
Xft/Hinting          1
Xft/RGBA             "rgb"
Xft/HintStyle        "hintslight"
Xft/DPI              98304

Fontconfig (Ubuntu 11):
requested size       11 points
family               Ubuntu
pixelsize            11.46 pixels
size                 11 points
antialias            1
hinting              1
autohint             0
embeddedbitmap       1
hintstyle            1 (slight)
rgba                 [no match]

Fontconfig (default pattern):
antialias            [no match]
hinting              1
autohint             0
embeddedbitmap       1
hintstyle            3 (full)
rgba                 [no match]

Fontconfig (default match):
family               DejaVu Sans
pixelsize            12.50 pixels
size                 12 points
antialias            1
hinting              1
autohint             0
embeddedbitmap       1
hintstyle            1 (slight)
rgba                 [no match]

Fontconfig (non-family/size defaults):
antialias            1
hinting              1
autohint             0
embeddedbitmap       1
hintstyle            1 (slight)
rgba                 [no match]

Comment 108 by Deleted ...@, Jul 16 2015

Has this issue been resolved with Nvidia GPUs? I am not game to install the updates unless it is still super sized in all of the fonts etc.

Comment 109 by Deleted ...@, Jul 21 2015

I haven't heard from anyone nor can I find any links to indicate that this issue has been resolved for Nvidia GPUs. Will just have to keep an old version of Chrome on my lounge PC...
@ #109: I do have it with Nvidia, latest stable Chrome, but I have two monitors, so I think it might be Issue 500201. I don't know if the other Nvidia users above have two monitors as well.

Comment 111 Deleted

Comment 112 by Deleted ...@, Jul 22 2015

The issue continues for me on version 44.0.2403.89 on Ubuntu 14.04 with the NVIDIA legacy driver version 173.14.39, the solution in comment #103 also works for this version. I use a single monitor.
Output of font-config-info are in comment #95 and #107

Comment 113 by Deleted ...@, Jul 25 2015

The issue continues for me on version 44.0.2403.107 on Ubuntu 14.04 with the NVIDIA legacy driver version 173.14.39, the solution in comment #103 also works for this version. I use a single monitor.
Output of font-config-info are in comment #95 and #107

Comment 114 by Deleted ...@, Jul 26 2015

I'm still using Version 43.0.2357.81 as it works great with my laptop and the dining room DTV 34 inch monitor, using the laptop monitor and the DTV monitor at the same time with the latest Nvidia driver for Mint 17 mate.


If I decide to use the latest version of Chrome, do I insert the info from post #103 into xorg.conf:

Option "DPI" "96 x 96"

into here:


Section "Screen"
    Identifier "intel"
    Device "intel"
EndSection

or here:

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection


If I'm using the Nvidia driver (only way I can use the dining room TV monitor) I presume its under the nvidia settings.

Comment 115 by Deleted ...@, Jul 29 2015

The issue continues for me on version 44.0.2403.125 on Ubuntu 14.04 with the NVIDIA legacy driver version 173.14.39, the solution in comment #103 also works for this version. I use a single monitor.
Output of font-config-info are in comment #95 and #107
I think the problem comes from the NVidia driver and the fact that since version 43.0.2357.125 Chrome is using system's default DPI settings instead of calculating them.
Long time ago I've tweaked system fonts' DPI to 96 from Linux Mint's font settings (because I noticed that the fonts are a bit "squashed" and this fixed the problem). Suddenly I noticed the "zooming" problem with Chrome after upgraded to version 43.0.2357.125. Then I checked in the NVidia driver application and realized that my monitor's DPI is set to 91x90, so I edited /etc/X11/xorg.conf file and manually set it to 96x96 which fixed the problem with Chrome. Checked back the NVidia diver application and it showed 96x96 DPI.
So this doesn't seem to be a bug with Chrome and is more likely a bug with your NVidia driver DPI calculations and the fact that Chrome is now using these calculated DPI values.
I had no problems with 43 but after installing 44.0.2403.125 I've got bitten by this bug. Using '--force-device-scale-factor=1' works for me. Currently using the NVidia 352.21 driver under CentOS with MATE desktop 1.8.2.
It's a bug in Chrome insofar as everything else in the system displays
properly, so Chrome is relying on a possibly broken API that other apps and
subsystems apparently don't touch.
I think https://codereview.chromium.org/1242753005/ might help (see https://code.google.com/p/chromium/issues/detail?id=511580 for details).

The commit is not yet in any released version, so please have some patience until it hits the dev channel.

Comment 120 Deleted

Comment 121 Deleted

Comment 122 by Deleted ...@, Jul 30 2015

I've added this to the xorg.conf file as per post #103:

Option "DPI" "96 x 96"

and all is well. 

I have a Gigabyte 15.5 inch laptop, Intel Core i5 2410M with Nvidia GT 540M GPU and a Kingston SSD with Mint 17 Mate 32 bit.

Comment 123 by Deleted ...@, Aug 4 2015

The issue continues for me on version 44.0.2403.130 on Ubuntu 14.04 with the NVIDIA legacy driver version 173.14.39, the solution in comment #103 also works for this version. I use a single monitor.
Output of font-config-info are in comment #95 and #107

Comment 124 by kbr@chromium.org, Aug 6 2015

Blocking: chromium:517549

Comment 125 by Deleted ...@, Aug 11 2015

The issue continues for me on version 44.0.2403.155 on Ubuntu 14.04 with the NVIDIA legacy driver version 173.14.39, the solution in comment #103 also works for this version. I use a single monitor.
Output of font-config-info are in comment #95 and #107
I'm on OpenSuSE Tumbleweed, running 355.02 NVIDIA driver (Latest). I have since switching my config from just using the Nvidia adaptor to using a Prime (Optimus) config run into this issue also. 

I've run all the tests to check what DPI things are reporting and 96 is the magic value returned by everything. Heck even calculating it (15 inch screen with 1600x900 resolution) doesn't give a reason for it to be selecting 2 as the scaling value. 

Happy to run any tests or get any helpful output. 
Please continue any discussion in Issue 515984 and  Issue 485183  (where a fix has been attempted).

Comment 128 by Deleted ...@, Aug 21 2015

The issue got fixed for me on version 44.0.2403.157 on Ubuntu 14.04 with the NVIDIA legacy driver version 173.14.39

Comment 129 by vkr...@gmail.com, Aug 21 2015

After today's update to 44.0.2403.157, fonts are huge/fuzzy on my home laptop again. Same issue as I had reported on my office desktop in comment 79. 

--force-device-scale-factor=1 restores sane behavior.

This is getting simply ridiculous.

Labels: -Via-Wizard Restrict-AddIssueComment-EditIssue
Adding comments to a closed bug, for a different version, is not helpful. Please continue any discussion in Issue 515984.
Showing comments 31 - 130 of 130 Older

Sign in to add a comment