Bug 150634 - menu bar (tab/ribbon view) only full visible after expand button
Summary: menu bar (tab/ribbon view) only full visible after expand button
Status: RESOLVED DUPLICATE of bug 140557
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.3.5.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-27 14:06 UTC by RG
Modified: 2022-08-27 19:41 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
4 examples in writer and impress, before and after clicking "expanse" button (558.18 KB, image/jpeg)
2022-08-27 14:06 UTC, RG
Details

Note You need to log in before you can comment on or make changes to this bug.
Description RG 2022-08-27 14:06:22 UTC
Created attachment 182046 [details]
4 examples in writer and impress, before and after clicking "expanse" button

If view is set to "ribbon/tabbed/band" in writer sometimes not enough symbols are display to fill free space of window/bar/tab, leaving free space. 

Only after clicking twice on the expand button on the right side of the bar/tab all the available space is filled with symbols. I changed also symbols from Yaru to Elementary but same behaviour. 

It hapeens most reproducible in maximized screen and in the "file" tab, where it happens in writer and calc (but not in draw or impress), or in tab "extras" where it happens in calc (but not in writer, impress and draw). And then sometimes in other tabs.

I also noticed this behaviour at least during the last year with different LO versions and under Linux Mint 20.3/Cinnamon. 

See screenshots for better understanding.

Now using Linux Mint 21 (Cinnamon 5.11, based on ubuntu 22.04) and official LibreOffice 7.3.5.2 from official Linux-Mint-repo, more system infos you can find here: https://termbin.com/ov3f

Any help which I should try on my side? Is this known behaviour?
Comment 1 V Stuart Foote 2022-08-27 19:41:10 UTC
Thanks for filing, but a known issue...

*** This bug has been marked as a duplicate of bug 140557 ***