With a fresh profile, modules start maximized. That's not a good window size for large screens, so users have to resize. Doing this with Calc ends up in a tiny and hard to spot square (title bar only). We should a) use a default windows size according the OS and b) at least define a minimum size for Calc. AFAIR, it's not an issue for other modules.
Hello Heiko, Thank you for reporting this. I confirm it with: Version: 6.3.0.0.alpha1+ Build ID: 77ae0abe21f672cf4b7d2e069f1d40d20edc49a7 CPU threads: 4; OS: Linux 4.9; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-05-31_15:33:33 Locale: en-GB (en_GB.utf8); UI-Language: en-US Calc: threaded When minimizing it the window size changes to really tiny square around 12px. Regarding starting as maximized I don't see it as an issue because the window size will be preserved for the next start. User will only have to change it once and most people don't have large screens.
Since Xisco requests input from UX, let's talk about. I work on a large super-wide screen where the modules are set to the maximum screen size - makes not much sense and I always resize first to ~1600x1200px, which is a 4/3 ratio. At least Windows has a application size policy with PreferredLaunchViewSize and we should follow this. Last but not least we define as minimum required resolution 1280x768px in [1], that could also be taken into account. Of course, the actual value has to be responsive to the resolution, and the default scaling should work with HiRes too (8k screens might come in some years). And we should maximize in case of very small screens. [1] https://wiki.documentfoundation.org/Design/MenuBar
We discussed the topic in the design meeting and agreed on the proposal, considering a 16:9 ration, which is better suited for movies, and less space such as 50%, which would be too small. Any minimum value is an advantage over the zero size that might appear to users as broken (therefore I raise the importance).
SetMinOutputSizePixel() is implemented for include/vcl/syswindow and include/sfx2/dockwin but not include/vcl/window.hxx. And this function should receive the actual value from the OS/DE. Probably an easy hack for more experienced developers. Thanks jmux for the code pointers.
@Caolán, I thought you might be interested in this issue...
SetMinOutputSizePixel sets the minimum size below which a window cannot be shrunk, which is probably not whats wanted.
In my case I had the window with 2 mm wight and 1 cm height. It is very hard to notice that this is a window. You can not edit in Calc in 0,02*1 cm... So, a default minim of 4 cm * 4 cm, or maybe 3*3 cm could be done. From my POV a 3*3 cm would be a minimum, else you can not see any cell in any file.
*** Bug 136655 has been marked as a duplicate of this bug. ***
*** Bug 136662 has been marked as a duplicate of this bug. ***
I had this bug in a bit different scenario. I was running Calc maximized, and when I tried to import a CSV file by double-clicking on it, after going through the import dialog, my window minimized to a very small square. This is reproduced everytime I run Calc maximized and import a CSV file via double-click. If Calc was not maximized before import, there was no issue.
This bites me almost daily because whenever I open Calc by opening a document, and it opens maximized, and I un-maximize the window (Super+downarrow key in GNOME), it ends up becoming a 1x1 pixels (or something like that) micro window that is barely noticeable. Non-technical users (like many people in my extended family, who don't know the keyboard shortcuts to un/maximimize) would be pretty flustered by that and will end up with a "broken" app practically speaking. > SetMinOutputSizePixel sets the minimum size below which a window cannot be shrunk, which is probably not whats wanted. Actually that's exactly what I would want, at least as the fallback for undefined states where the app can't figure out what the appropriate default size would be. Make it enforce a hard minimum of 600x400 at the very least. Why would anyone ever want to have a LibreOffice Calc/Writer/etc. main window sized anywhere smaller than 640x480 pixels? It seems to me that it could safely be assumed to be the absolute minimum to which a main app window can no longer be shrunk, because it's no longer usable below that size (even the toolbars would eat half of the height). Even phones these days have at least 720px in one dimension or the other, and no VGA output that I know shrinks below 640x480 even in disaster scenarios.
(In reply to Jean-François Fortin Tam from comment #11) > This bites me almost daily because whenever I open Calc by opening a > document, and it opens maximized, and I un-maximize the window > (Super+downarrow key in GNOME), it ends up becoming a 1x1 pixels (or > something like that) micro window that is barely noticeable. > > Non-technical users (like many people in my extended family, who don't know > the keyboard shortcuts to un/maximimize) would be pretty flustered by that > and will end up with a "broken" app practically speaking. > > > SetMinOutputSizePixel sets the minimum size below which a window cannot be shrunk, which is probably not whats wanted. > > Actually that's exactly what I would want, at least as the fallback for > undefined states where the app can't figure out what the appropriate default > size would be. Make it enforce a hard minimum of 600x400 at the very least. > > Why would anyone ever want to have a LibreOffice Calc/Writer/etc. main > window sized anywhere smaller than 640x480 pixels? It seems to me that it > could safely be assumed to be the absolute minimum to which a main app > window can no longer be shrunk, because it's no longer usable below that > size (even the toolbars would eat half of the height). Even phones these > days have at least 720px in one dimension or the other, and no VGA output > that I know shrinks below 640x480 even in disaster scenarios. I'm also experiencing exactly the same issue, running KDE Neon. In fact, I cannot even find the 'pixel' on my display and need to force-close the app. It really is an absurd situation - clearly a bug and not a feature!
*** Bug 145545 has been marked as a duplicate of this bug. ***
Hi there As far as I can see, this issue is still live and in fact, I experience it on a regular basis. I also have a group of users at my company that complain about it. That being the case, I'm interested in hearing from someone on the project team to understand how I can assist with getting it resolved. Many thanks, Jon
Created attachment 176440 [details] screenshot of minimised Calc window on Ubuntu 18.04 I can reproduce the issue by opening Calc (either opening the application or opening a document with Calc) with a recent master build: 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 Not only Calc is useless at this size (I am only able to click the "close document" button), but it might look to others like it has crashed if they don't directly spot where the tiny window is. Attached screenshot shows panel indicators for size reference.
Same problem using Ubuntu 20.04 and libreoffice 7.2.2.2.
Same issue for quite some time now. Not only with Calc, but with Writer. Ubuntu 21.04 LibreOffice Version 7.1.7.2 The window ends up being about 1 pixel wide. I can drag it larger, but very disruptive and happens frequently. I'll (try to) post an image.
Created attachment 177624 [details] Pix of the intensely small LibreOffice window
I am coming back with the idea to calculate a minimum width/height when LibreOffice is usable, and if the windows is going back to 1 mm, that limit will force to be bigger. Maybe a minimum of 5 cm width and 4 cm heigh (it's the title and 2 rows of icons) nothing usable still, but enough that we can see LibreOffice window IS on the screen).
*** Bug 134315 has been marked as a duplicate of this bug. ***
*** Bug 148637 has been marked as a duplicate of this bug. ***
Hello, This bug is very anoying and still present in latest version as shown by latest duplicates reports. Unfortunately, as screens becomes wider and uses higher dpi resolution, it is more and more difficult to find the restored window. This leads users to think it is freezed or anything unrecoverable and kill process, loosing their work. IMHO, I would expect to view at least the 'File' menu in order to save my work or quit properly, and the title bar button to maximize/close the window. I agree with the minimum size of 640x480 in last resort. I didn't see any screen smaller even considering oldest hardware capable of running current version of LO. May I ask what is expected by the UI team to take a decision ? Best regards
(In reply to draco31.fr from comment #22) > May I ask what is expected by the UI team to take a decision ? No need for further input from the design team. Seeking for volunteers to implement it.
No repro on Windows 11. Is this a Linux-only bug?
(In reply to Matt K from comment #24) > No repro on Windows 11. Is this a Linux-only bug? Yes indeed, the OS field was incorrect.
Repro today on a new Ubuntu 22.04 install with Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 5c68399e6bea3aa18477487400f8bb143d6ed84e CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
confirmed for Impress, too. Version: 7.4.1.1 / LibreOffice Community Build ID: 40(Build:1) CPU threads: 16; OS: Linux 5.18; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Debian package version: 1:7.4.1~rc1-3 Calc: threaded
Removing "Calc" from summary and component as issue has been reported for Writer and Impress as well (as well as Dray in another report that I will probably mark as duplicate). Earliest known version from Description is 6.3 alpha1+, using "6.3 all versions" as it is not available.
*** Bug 150079 has been marked as a duplicate of this bug. ***
This may affect Windows. Bug 99112 describes related behaviour; this may be a duplicate.
There's a lot of messages, but no fix. Is there anyone to work on this? It's easy enough to even check for (0,0) and change that to 600x600 so at least it will be visible if the real issue can't be solved today. I'll pay a $50 bug bounty for this fix to be committed and integrated.
The comments from this month might be about bug 150856, which was a recent regression and is fixed for 7.4.2. Heiko: how is the behaviour for you now? In Safe mode on Linux with any of the UIs, they do *not* start maximised. Same for Windows. Bug 99112 is about remembering the size across sessions, while this report is about what happens with a fresh profile in a single session. Arch Linux 64-bit Version: 7.4.1.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 8; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US 7.4.1-2 Calc: threaded Arch Linux 64-bit Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: f5c6ef40dd494f6984c6ed784fccc02806999836 CPU threads: 8; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 7 September 2022 Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 00c5b0ca9264c5440bc70a68c425127ba5a47003 CPU threads: 2; OS: Windows 10.0 Build 19044; UI render: default; VCL: win Locale: fi-FI (fi_FI); UI: en-US Calc: threaded Jumbo
On Debian, I confirm that upgrading to LO 7.4.2.1 from experimental branch today fixes this issue. Thank you. LO windows will open one last time with minimal size, though. After manually resizing them one last time they will reopen maximized upon restart, as expected. At least on Debian I never experienced this bug with GNOME or Cinnamon Desktop; only with KDE Plasma. fixed in: Version: 7.4.2.1 / LibreOffice Community Build ID: 40(Build:1) CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Debian package version: 1:7.4.2~rc1-2
(In reply to Buovjaga from comment #32) > Heiko: how is the behaviour for you now? In Safe mode on Linux with any of > the UIs, they do *not* start maximised. Same for Windows. Cannot test on Linux this week. All good on macOS, but prolly never was an issue.
The only way I consistently reproduce this bug is by following steps similar to comment 10, when opening a LibreOffice component involves getting through a dialog first. For example: 1. open Calc 2. maximise the window 3. close Calc 4. Open a CSV file with Calc 5. Once passed the import dialog, unmaximise (aka "restore down") the Calc window But also: 1. open Base 2. maximise the window 3. close Base 4. Open Base again 5. Once passed the database creation dialog, unmaximise (aka "restore down") the Base window Result: the windows is tiny. However, it is possible to resize the window to an extremely small size in any LO component.
*** Bug 151313 has been marked as a duplicate of this bug. ***
Seems to be solved with bug 150779.
(In reply to Heiko Tietze from comment #37) > Seems to be solved with bug 150779. Sorry Heiko, I can still reproduce with: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a41c82407bbb73a4d87070326485ec4b4e954a65 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded and: Version: 7.4.2.3 / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded following the steps in comment 35.
Reproduced on Libreoffice 7.4.2 on Linux Mint 21 Cinnamon 5.4.12 Following the steps of comment 35 as stated above Please, prioritize this issue, it's been there for ages and it's 100% possible to reproduce
Very reproducible for LibreOffice 7.4.3 on Ubuntu 20.04 LTS (patched to date) Is very annoying, very noticeable when using CSV. Gnome shortcuts to resize the window in https://askubuntu.com/questions/1275213/libreofficecalc-window-is-shrunk-to-a-line-and-is-unclickable I haven't investigated the output of SetMinOutputSizePixel but it looks like the end window it produces is the smallest possible desktop window, not the smallest window usable in Calc. Which even sounds like the wrong choice. It's pretty much impossible to use without keyboard shortcuts on "normal" 1920x1080 monitors. Surely after 3.5yrs the answer is not "best possible for all resolutions" but "anything that will work with many common resolutions" since I think the current approach is probably not workable for any resolution.
Hello, Reproduced on Ubuntu 22.04 Press Ctrl-Super-ArrowUp to put window back in maximized mode. However, totally unable to resize the window in unmaximized mode, thus critical bug. Thanks
EDIT: Reproduced on Ubuntu **Unity** 22.04 (not GNOME or other).
Already reproduced following comment 35 steps in: Version: 6.0.0.3 Build ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk2; Locale: en-AU (en_AU.UTF-8); Calc: group However, my steps don't give completely consistent results, so I'm not calling it a regression based on inability to reproduce in earlier versions. More consistent STR welcome. Marking as depending on bug 97894 as a fix that covers all bases (startup, maximising/unmaximising, and manual resizing) should also fix this.
Just an idea, can't it at least have a min 640x480 min size fallback? At least it's easier to spot it and resize by hand.
*** Bug 155955 has been marked as a duplicate of this bug. ***
Amin Irgaliev committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/431dc963a0d18341c9b4869a2a64009b7ff7f699 tdf#125543 Fix window size in GTK3 plugin It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(In reply to Commit Notification from comment #46) > Affected users are encouraged to test the fix and report feedback. First, Amin, thanks for the patch. Unfortunately this is not something I experience frequently, so not so easy to reproduce the situation where I saw this. Encouraging other dupe authors to try though...
I am no longer seeing the problem. When I open a new window, it is not maximized. If I maximize the window and then un-maximize it by dragging the title bar, it changes to a sensible size. Running Libre office under 7.3.7.2, Pop_OS 22.04 Gnome 42.5 Note, I'm currently running under Wayland, but was running under X windows when the problem occurred. So, works-for-me.
Thank you for the patch, Amin. If you don't have follow-up commits, please feel free to mark as "resolved". Everyone affected, especially if you come from a duplicate report: please test a recent master build and see if you can still see the issue -> https://dev-builds.libreoffice.org/daily/master/current.html Given the number of duplicates, it would be good to get lots of testers. Noting that Heiko was talking about a fresh profile in Comment 0, which matches bug 155955 (recently fixed). Using Comment 35 steps, I can't reproduce. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d74344f6cae0cf1c12f08249c8f49be1374fb98f CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
These fixes affect only the GTK3 plugin. Please test bug reproduction on other plugins: kf5, x11, gen, etc.
If the bug is still reproducible, please let us know the steps that made the bug for you.
Worked for me, thanks all. For anyone like me who was born with congenital dumbitis: you need to set the default program to LO dev otherwise it'll keep using default LO.
Amin Irgaliev committed a patch related to this issue. It has been pushed to "libreoffice-7-6": https://git.libreoffice.org/core/commit/ca93bbe8703bd6cf2aef8a649b0db2524a61afe9 tdf#125543 Fix window size in GTK3 plugin It will be available in 7.6.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
*** Bug 104371 has been marked as a duplicate of this bug. ***
Reopening this bug. An update to a newer version via the PPA. The Calc seems to be steady but I've appeared to still be having the issue on LibreOffice Draw even after an update
(In reply to ben.grote from comment #55) > Reopening this bug. > > An update to a newer version via the PPA. The Calc seems to be steady but > I've appeared to still be having the issue on LibreOffice Draw even after an > update Please copy and paste here the contents of your Help - About by clicking the copy button. This allows us to know more about your system. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
*** Bug 158964 has been marked as a duplicate of this bug. ***
It partially works for me in version 24.2 from Flathub, on Wayland GNOME 45 / Fedora 39. What works: it doesn't become minuscule. What doesn't work optimally: it seems the maximization state is maybe not saved independently from width/height, because sometimes when you unmaximize it, either... * It unmaximizes to the previous window width/height (correct behavior), or; * It unmaximizes to the "maximized window's width/height" (incorrect behavior) See this demonstration video showing both situations with LibreOffice Calc 24.2: https://youtu.be/dv8gb1GljzU Further reference that might help as inspiration for implementation, i.e. how it works in GNOME apps at least: https://developer.gnome.org/documentation/tutorials/save-state.html (you can see there that the maximization state is saved independently from width/height, but also you need to infer that width/height shouldn't get saved while in maximized state, only in windowed state) --- Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 8; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Flatpak Calc: threaded
I forgot to mention: the behavior observed in my comment #58 above is consistent across the apps, i.e. on my end it behaves the same in Draw like it does in Calc or Writer; I don't get minuscule windows on demaximizing, but the window size restoration is still a coin toss between "what it was" and "what is the width and height of the maximized window".
Ben didn't provide version details in comment 55. Jeff, thank you for the follow-up, but because this report is about the barely visible, minuscule window issue, and because there's 60+ comments, let's see if your issue is already better described elsewhere, or if it needs a fresh start in a new report, with clear steps. Thank you!