Created attachment 120254 [details] Garbled menu in Libreoffice This is on latest Debian Jessie ( 8.1 at this time ). I installed TightVNC. Then opened LibreOffice. The menu is garbled. Please refer to the attachment. Note that this problem does not happen on a standard gnome session ( meaning standard X11 server ). It also doesn't happen on another VNC server ( TigerVNC ). I've attached the extensions supported by TightVNC ( where this bug is seen ) and TigerVNC ( where the menu is good ). I'm of the opinion that this is someway related to XInputExtension ( or some VNC extension ), as TightVNC supports very minimal extensions, whereas TigerVNC supports many. But the question is all other applications have their menu working fine in TightVNC. LibreOffice is the only app which has this menu issue.
Created attachment 120255 [details] Tightvnc xdpyinfo command output
Created attachment 120256 [details] TigerVNC xdpyinfo command output
What is the LibreOffice version you are using? Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
[user@host]$ libreoffice --version LibreOffice 4.3.3.2 430m0(Build:2) Version number specific to my Linux distribution ( debian ) available at: https://packages.debian.org/jessie/libreoffice
Does the problem also occur with LibreOffice 5? You can try it in parallel: https://wiki.documentfoundation.org/Installing_in_parallel/Linux
Created attachment 120473 [details] Issue is present in Libreoffice 5.
Created attachment 120949 [details] Temporary fix for this issue Xtightvnc ( http://www.tightvnc.com/ ) seems to behave differently as it has its own way of handling keysyms. So, the XkbKeycodeToKeysym() calls for the modifier keys ( Alt / Ctrl / Shift ) are 0. Hence, the following code in vcl/unx/generic/app/saldisp.cxx returns ??? when it is given a keysym of 0. OUString SalDisplay::GetKeyNameFromKeySym( KeySym nKeySym ) const if( aKeyCode != 0 && aKeyCode != NoSymbol ) { if( !nKeySym ) aRet = "???"; else { ... ... ... } } return aRet; } I have used this patch to fix this issue temporarily for my case. The patch uses meaningful defaults for the modifier keys. Though a better patch is welcome.
why don't you submit that patch for review to the gerrit LibO website? https://gerrit.libreoffice.org/
As tommy mentioned, Could you please submit the attached patch to gerrit as described here: https://wiki.documentfoundation.org/Development/gerrit/SubmitPatch? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once it's done
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180404
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20180502