Bug 161050 - The main menu is not present in KDE if the widget global menu is used in the KDE panel
Summary: The main menu is not present in KDE if the widget global menu is used in the ...
Status: RESOLVED DUPLICATE of bug 156387
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
24.2.0.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-12 11:16 UTC by Tulio Macedo
Modified: 2024-05-27 14:04 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Application window without menu (34.14 KB, image/png)
2024-05-12 11:16 UTC, Tulio Macedo 		Details
AppImage version with the menu in the panel (45.32 KB, image/png)
2024-05-12 11:18 UTC, Tulio Macedo 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tulio Macedo 2024-05-12 11:16:53 UTC 
Created attachment 194091 [details]
Application window without menu

There is a widget in KDE to move the main menu from the application window to the panel, if the application has the current focus.
In that way, the application window has no main menu, the KDE panel with the widget take care of that.
Using LibreOffice with this configuration, the menu in the application window is not present, as expected, but there no menu in the panel either.
As the attached image show, with the flatpak version there's no menu of any kind, but the AppImage version has the expected behavior.
Comment 1 Tulio Macedo 2024-05-12 11:18:37 UTC 
Created attachment 194092 [details]
AppImage version with the menu in the panel

Including image with other version (Flatpak does not work and AppImage does).
Comment 2 Stéphane Guillou (stragu) 2024-05-27 14:04:00 UTC 
Thanks for the report.
This flatpak + wayland issue (you are using Wayland, right?) is already tracked in bug 156387.

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