Description: In impress and draw, selecting the gallery in the sidebar makes the sidebar too large. In fact, so large that it is impossible to work. First seen in 7.0.2.1. Think that 7.0.1.2 was OK, but cannot be sure, used for too little. 6.4.x is OK. The issue is present in the kde5 and gen VCLs, but not in the GTK3 one. Steps to Reproduce: 1. Optional. Start with a new profile to be sure that the issue is not related to a stale profile 2. Open libreoffice --draw 3. Go to the sidebar and select the gallery Actual Results: The sidebar expands in width to accommodate the gallery until it covers half of the computer screen. The actual drawing or slide you were working on remains compressed in a tiny space, insufficient for editing. To make the matter worse, trying to reduce the sidebar width when the gallery made it so huge typically is merely impossible, but in some cases leads to weird issues such as LibO taking up 100% CPU or crashing or the sidebar disappearing completely. When the latter thing happens, trying to re-expand it or to toggle its appearance does not work. At this point, restarting LibO gives you no sidebar at all until the profile is reset. Expected Results: The gallery should not make the sidebar take an unreasonable amount of space. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.0.2.1 Build ID: ede20268f3f8777cdf69e0281835d320c41213fc CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: kf5 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Created attachment 165854 [details] Screenshot with the huge gallery sidebar
Looks like this is fixed in master. After user profile reset not in 7.1 master: Version: 7.1.0.0.alpha0+ Build ID: 4a899a5f8a72ea29a6919316afe3627de9f33e95 CPU threads: 6; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: hu-HU (hu_HU.UTF-8); UI: en-US Calc: threaded Version: 7.1.0.0.alpha0+ Build ID: 4a899a5f8a72ea29a6919316afe3627de9f33e95 CPU threads: 6; OS: Linux 5.4; UI render: default; VCL: kf5 Locale: hu-HU (hu_HU.UTF-8); UI: en-US Calc: threaded But reproduced in (7.0 master (kf5 only)): Version: 7.0.2.0.0+ Build ID: b27137a7091104cce177791478e86d127680c9af CPU threads: 6; OS: Linux 5.4; UI render: default; VCL: kf5 Locale: hu-HU (hu_HU.UTF-8); UI: en-US Calc: threaded Can't reverse bisect because not in 7.1 oldest...
see also for a Windows 8.1 system with issue, but not repro on Windows 10 installs.
(In reply to Attila Baraksó (NISZ) from comment #2) > Looks like this is fixed in master. After user profile reset not in 7.1 > master: > > Version: 7.1.0.0.alpha0+ > Build ID: 4a899a5f8a72ea29a6919316afe3627de9f33e95 > CPU threads: 6; OS: Linux 5.4; UI render: default; VCL: gtk3 > Locale: hu-HU (hu_HU.UTF-8); UI: en-US > Calc: threaded > > Version: 7.1.0.0.alpha0+ > Build ID: 4a899a5f8a72ea29a6919316afe3627de9f33e95 > CPU threads: 6; OS: Linux 5.4; UI render: default; VCL: kf5 > Locale: hu-HU (hu_HU.UTF-8); UI: en-US > Calc: threaded > > But reproduced in (7.0 master (kf5 only)): > > Version: 7.0.2.0.0+ > Build ID: b27137a7091104cce177791478e86d127680c9af > CPU threads: 6; OS: Linux 5.4; UI render: default; VCL: kf5 > Locale: hu-HU (hu_HU.UTF-8); UI: en-US > Calc: threaded > > Can't reverse bisect because not in 7.1 oldest... Hi Attila, I've updated linux-64-7.0.git, could you please reverse bisect this issue again to find when it got fixed ?
I can neither reproduce with git master nor Debian-provided 7.0.3.1. Version: 7.1.0.0.alpha1+ Build ID: e1e662065c911e55aeb85a67664dea9d5ed12313 CPU threads: 12; OS: Linux 5.9; UI render: default; VCL: kf5 Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded Version: 7.0.3.1 Build ID: 00(Build:1) CPU threads: 12; OS: Linux 5.9; UI render: default; VCL: kf5 Locale: en-GB (en_GB.UTF-8); UI: en-US Debian package version: 1:7.0.3-4 Calc: threaded
> Hi Attila, > I've updated linux-64-7.0.git, could you please reverse bisect this issue > again to find when it got fixed ? Hey Xisco, Thanks for the update! This was the fix: https://cgit.freedesktop.org/libreoffice/core/commit/?id=d9ae83e596e94c4d4967c5de653c2060b0648c78 Required a little manual detective work to finding the fix (because now I can't reproduce in 7.0 master, neither oldest), but I did my homework. :)
*** This bug has been marked as a duplicate of bug 136737 ***