when running in vnc, in the Customize dialog Shortcut keys list:
Ctrl, Alt, and Shift are missing and "???" shows instead.
hi, are you still seeing this bug with latest LibO 126.96.36.199 release?
still get ??? instead of ctrl/alt/shift with the latest trusty updates:
The problem also occurs with up-to-date Voidlinux running under Linode
The short-cut mod-keys are displayed as ??? in the menus when running LibreOffice in a VNC session, even though they are displayed correctly when running LibreOffice outside VNC as an X client through an X-forwarding ssh connection, and when running Voidlinux on a local KVM instance. The problem occurs both with and without the -compatiblekbd switch for turbovnc.
Perhaps LibreOffice is assuming the existence of certain files or features that may not be present under VNC. For example, in the past there was some discussion about LibreOffice dropping support for environments that don't have XKB extensions, which, unfortunately, would include many implementations of VNC.
I can not confirm with LO 4.3.6, win7. I'm connecting to the win machine from ubuntu. Can you attach printscreen what you see? Maybe linux only issue.
Created attachment 115018 [details]
Screenshot of shortcut menu problem under VNC
This screenshot illustrates the problem with shortcut keys in LibreOffice's menus when running under VNC. This particular example is with an up-to-date installation of Voidlinux on a Linode virtual server, using turbovnc as the virtual X desktop, rendered locally using ssvnc on Debian/Crunchbang.
The problem does not arise using when using VNC to gain remote access to a Xorg session on a real display (e.g. with x11vnc), but then that is not an option when setting up virtual X11 desktops on headless servers.
The most likely explanation for this, which I have previously experienced, is that your vnc server doesn't have a working XKB.
This is an issue which exists / has existed in various vnc servers. You may have better luck with a newer version or a different vnc server, or a change to the configuration of the vnc server may fix it, but either way it's not an LO bug - we just depend on XKB being present, which it generally ought to be.
(this can be confirmed by running "xprop -root | grep XKB" - if the output is blank, XKB isn't working)
-> RESOLVED NOTOURBUG