Description: CTRL+super+up makes the window disappear. All other apps will maximise the window when using this shortcut combination. The other shortcuts work OK. For example, CTRL+Super+left makes the window take up the left half of the screen. Similarly for CTRL+Super+right. It's useful for when you want to switch from maximise to half screen (to show two documents on the screen) and back again. Also for if the program starts not maximised. The solution so far is to double click the title bar or click the Maximise icon in the corner but that is slow and cumbersome. Steps to Reproduce: 1. Have window not maximised 2. Press key combination CTRL + Super + up 3. Actual Results: Window disappears. Expected Results: Window should be maximised. Reproducible: Always User Profile Reset: No Additional Info: Operating system is Ubuntu 16.10 but this bug has always been present. User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.21 (KHTML, like Gecko) konqueror/4.14.3 Safari/537.21
I can't reproduce it in Version: 5.4.0.0.alpha0+ Build ID: 634589b340316ba64b731b4d923c1056be415494 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); Calc: group or Version: 5.2.2.2 Build ID: 1:5.2.2-0ubuntu2 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; Locale: ca-ES (ca_ES.UTF-8); Calc: group in Ubuntu 16.10 Which desktop environment are you using? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once you answer the question above
The desktop environment is Unity. I haven't changed it from stock, at lease I don't think I have. uname -a gives: Linux ******** 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a gives: LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety
Not reproducible with LO 5.4.1 from Ubuntu PPA and Ubuntu 16.04 x86-64 with Unity. Version: 5.4.1.2 Build ID: 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; Locale: fr-FR (fr_FR.UTF-8); Calc: single Please, could you give the complete version information of your LibreOffice installation from menu Help > About LibreOffice (you can select and copy& paste the text in this dialog). Set status to NEEDINFO, please set it back to UNCONFIRMED once requested informations are provided. Best regards. JBF
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