Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Libreoffice menu bar invisible #187

Open
oberon-manjaro opened this Issue Apr 22, 2016 · 6 comments

Comments

Projects
None yet
6 participants
@oberon-manjaro
Copy link

oberon-manjaro commented Apr 22, 2016

libre

Using regular Vertex, commit 6c6cfdb, with libreoffice-5.1.2 (fresh).

@oberon-manjaro

This comment has been minimized.

Copy link
Author

oberon-manjaro commented Apr 27, 2016

Working fine with "libreoffice-still" package, which is at 5.0.5. Might be their issue...?

@Photon89

This comment has been minimized.

Copy link

Photon89 commented Apr 27, 2016

No, it's an issue with the GTK theme, it works well here with the Adwaita GTK3 theme (Arch Linux, GTK 3.20.3, libreoffice-fresh 5.1.2).

@aguador

This comment has been minimized.

Copy link

aguador commented May 3, 2016

This may help narrow down the problem. The dark version works with no problem on both 32- and 64-bit machines. The problem only appears with the light (and, of course, square) versions.

@fulljackz

This comment has been minimized.

Copy link

fulljackz commented Jun 9, 2016

Hi, seems that this fix issue with Debian Stretch

apt-get remove libreoffice-gtk3 && apt-get install libreoffice-gtk

capture du 2016-06-09 16-52-42

@vith

This comment has been minimized.

Copy link

vith commented Jun 26, 2016

Still an issue with

extra/libreoffice-fresh 5.1.4-1 [installed]
extra/gtk3 3.20.6-1 [installed]
aur/vertex-themes 20160329-2 (130, 15.41) [installed]

on Arch Linux.

I'm using SAL_USE_VCLPLUGIN=gtk as a workaround for now. This can be uncommented in /etc/profile.d/libreoffice-fresh.sh

@fitojb

This comment has been minimized.

Copy link

fitojb commented Oct 10, 2016

LibreOffice 5.2.x should fix this issue. The fixes are unfortunately too invasive to backport to 5.1.6 RC2 (the last version of the 5.1 series to be released), so please upgrade to 5.2.x.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.