On Windows you cannot resize LO windows below a certain size - on Linux there is no such restriction. You can resize the window until is is only a 1px thin bar. There should be a minimum size on Linux as well.
Yeah. NEW.
Caolan, is this a GTK issue?
Its probably a failure to set a min size via SetMinOutputSizePixel. Some backends might set the min size to the initial size if no other is set. Its not immediately obvious to me what the min size of the application windows should be or where exactly to calculate and set it.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Dear Samuel Mehrbrodt (CIB), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
*** Bug 142649 has been marked as a duplicate of this bug. ***
I have the same problem with ubuntu 20.04 and LO 7.2
Also reproducible on: Version: 7.3.0.0.alpha1+ / LibreOffice Community Build ID: eec32be26d5d5805c1cb8cb53ce9702c04829819 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded And with gen VCL too: Version: 7.3.0.0.alpha1+ / LibreOffice Community Build ID: eec32be26d5d5805c1cb8cb53ce9702c04829819 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: x11 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded On Ubuntu 18.04. This is not only an issue with resizing them manually to a size too small. Sometimes (not sure how to reproduce yet), the window opens in a minimal size, making it very had to find.
Created attachment 176439 [details] video demonstrating minimal window size on Ubuntu 18.04 Desktop environment is Budgie.
Same problem in ubuntu 20.04 on libreoffice 7.2.2.2.
Also reproducible on 22.04, libreoffice-writer 1:7.3.6-0ubuntu0.22.04.1
Also just ran into this issue, and at first i though "why is libreoffice not starting", turns out if libreoffice is started with any arguments like "--calc" or "--calc /somefile", then sometimes libreoffice decides to start with 1px windows (maybe even 0?) making me think it somehow is not progressing since the splash screen, but this does not happen if not started with a argument (like just "libreoffice") Operating System: Manjaro Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX Vega Manufacturer: ASUS
*** Bug 147075 has been marked as a duplicate of this bug. ***
*** Bug 145820 has been marked as a duplicate of this bug. ***
Hi, Is there any progress on this? The bug has been reported in 2016 and it still hasn't been resolved.
Created attachment 186233 [details] Opened Calc window appearing a line
*** Bug 151870 has been marked as a duplicate of this bug. ***
*** Bug 144237 has been marked as a duplicate of this bug. ***
*** Bug 149510 has been marked as a duplicate of this bug. ***
(In reply to Stéphane Guillou (stragu) from comment #18) > *** Bug 144237 has been marked as a duplicate of this bug. *** I came across this bug report searching how one would have to call SetMinOutputSizePixel to implement a minimum width of 5 cm as I proposed in #144237, Comment 8. Unfortunately I found no description for SetMinOutputSizePixel mentioned above. But searching for it I came across gtk_widget_set_size_request which has two parameters in pixels for width and height. Probably the screen's dpi-value can be read somehow, so ceil(50.0*dpi/2.54) would be a proper minimum width, ceil(8.0*dpi/2.54) would be a proper minimum height. Unfortunately I am not experienced enough to know where this call has to be placed.
*** Bug 155616 has been marked as a duplicate of this bug. ***
Created attachment 187905 [details] Calc Window
Any progress on this? It has been 7 years...
*** Bug 142671 has been marked as a duplicate of this bug. ***
*** Bug 156935 has been marked as a duplicate of this bug. ***