Bug 108515 - Menu bar re-appears and freezes the application when closing a document
Summary: Menu bar re-appears and freezes the application when closing a document
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.3.3.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Performance
  Show dependency treegraph
 
Reported: 2017-06-13 21:58 UTC by Dan
Modified: 2023-04-12 16:55 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan 2017-06-13 21:58:05 UTC
Step 1:

Hide the menu bar.

Step 2:

Open another Writer window and also hide the menu bar.

Step 3:

Close the second window.

Result:

Menu bar has appeared in the first window. This also freezes the application if there are many windows open.

Screencast illustrating the bug:

https://youtu.be/bTMJECE0_sk
Comment 1 Buovjaga 2017-06-23 12:59:08 UTC
Missing first steps:
0. (If not seeing Notebookbar) Tools - Options - Advanced - Enable experimental features
1. View - Toolbar layout - Notebookbar
2. Notebookbar hamburger - uncheck Menubar

I repro, but did not get a freeze even with 5 windows open.

Arch Linux 64-bit, KDE Plasma 5
Version: 6.0.0.0.alpha0+
Build ID: ab27953d9ef2076e0acd43ed4ba6652732794777
CPU threads: 8; OS: Linux 4.11; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on June 23rd 2017
Comment 2 Dan 2017-06-23 17:44:40 UTC
Thanks for responding,

I'm not using any experimental features.

It's just a keybinding in LibreOffice.

It's in Tools>Customize>Keyboard>View>Menubar

Here's an image:

http://i.imgur.com/tT4CGp3.png

I don't have the new menu enabled.
Comment 3 QA Administrators 2018-06-24 02:41:38 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2020-06-24 03:41:14 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2022-06-25 03:38:25 UTC
Dear Dan,

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 https://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://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug