Bug 98764 - Interface fonts are huge compared to system when using GNOME integration
Summary: Interface fonts are huge compared to system when using GNOME integration
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: HiDPI
  Show dependency treegraph
 
Reported: 2016-03-19 10:17 UTC by Andy Smith
Modified: 2017-02-27 07:00 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Smith 2016-03-19 10:17:43 UTC
On Debian testing with GNOME desktop, trying both Debian-packaged version 1:5.1.1-1 and upstream:

Version: 5.1.1.3
Build ID: 89f508ef3ecebd2cfb8e1def0f0ba9a803b88a6d

The interface UI fonts and icons in all libreoffice apps are really huge in comparison with the GNOME system fonts.

The problem can be mitigated somewhat by setting the scaling to the lowest it will go, 80%, but I really feel like things are about double size so would be looking to set it to 50% if that were possible.

This is a HiDPI display (2560x1440px) so I suspect something regarding DPI is being detected wrongly.

Various places DPI is coming from (no specific configuration used to change these):

$ xrdb -q | grep dpi
Xft.dpi:	192
$ xrandr -q | grep primary
eDP1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 310mm x 170mm
$ xdpyinfo | grep dots
  resolution:    210x215 dots per inch

Scaling in GNOME is set to 1 for Windows and Fonts.

Interestingly if I remove the libobasis5.1-gnome-integration_5.1.1.3-3_amd64.deb package then I get an interface that uses correct proportions, i.e. the fonts used are the same size as my system fonts, and the icons are smaller too.

It doesn't look quite as pretty of course, but this would be an acceptable workaround but for the fact that without the GNOME integration, icons for separate documents are not grouped together in the dash, so I get an icon called LibreOffice for each document window, which is rather confusing.

I can do some screenshots if any of this is not clear, but basic summary is that when the GNOME integration is in use, the entire UI erroneously scales up by about 2x.

Any workaround to force DPI or similar?
Comment 1 Buovjaga 2016-03-27 15:44:54 UTC
GTK3 support is still experimental.
You can launch with GTK2 by:
SAL_USE_VCLPLUGIN=gtk

Do you see the same problem in 5.2: http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@70-TDF/current/
https://wiki.documentfoundation.org/Installing_in_parallel/Linux
Comment 2 Andy Smith 2016-03-27 17:06:51 UTC
(In reply to Buovjaga from comment #1)
> GTK3 support is still experimental.
> You can launch with GTK2 by:
> SAL_USE_VCLPLUGIN=gtk

Launching 5.1 like this:

$ SAL_USE_VCLPLUGIN=gtk libreoffice5.1 --calc

did not seem to make any difference, that is, fonts still roughly twice as big as system.

> Do you see the same problem in 5.2:
> http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@70-TDF/current/

After installing debs from:

http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@70-TDF/current/master~2016-03-27_09.53.05_LibreOfficeDev_5.2.0.0.alpha0_Linux_x86-64_deb.tar.gz

behaviour was the same both when launching as:

$ libreofficedev5.2 --calc

and

$ SAL_USE_VCLPLUGIN=gtk libreofficedev5.2 --calc

Cheers,
Andy
Comment 3 Doug Selby 2016-11-28 13:18:34 UTC
Hello,

I see the same issue with libreoffice-* 1:5.2.3.3-9.fc25 from Fedora updates on my XWAYLAND0 connected 3200x1800+0+0 290mm x 170mm screen at 192 dpi (according to xrandr and xrdb). The interface is quite unusable in default env; most options windows extend past the visible area, and others appear to be only one quarter drawn.

In my case though running with SAL_USE_VCLPLUGIN=gtk does resolve the issue completely, and so is a feasible workaround in the short term.

Cheers,
Doug.
Comment 4 Andy Smith 2017-02-27 02:50:22 UTC
This appears to be resolved for me now using Debian packaged version 1:5.2.5-2 (in Debian stretch).