Summary: | Interface fonts are huge compared to system when using GNOME integration | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Andy Smith <andy-documentfoundation.org> |
Component: | UI | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | andy-documentfoundation.org, ilmari.lauhakangas |
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 90796 |
Description
Andy Smith
2016-03-19 10:17:43 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 (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 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. This appears to be resolved for me now using Debian packaged version 1:5.2.5-2 (in Debian stretch). |