Bug 435613 - [Wayland] I can not use the application menu correctly after opening Audacious
Summary: [Wayland] I can not use the application menu correctly after opening Audacious
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: appmenu (show other bugs)
Version: 5.23.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: wayland-only
Depends on:
Blocks:
 
Reported: 2021-04-11 13:05 UTC by Ahmed
Modified: 2024-06-19 11:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ahmed 2021-04-11 13:05:55 UTC
SUMMARY
When I click the application menu with Audacity opened, it clicks the Audacious icon instead (the taskbar icon can be turned on from the application settings)

STEPS TO REPRODUCE
1. Open Audacious.
2. Click on the application menu.

OBSERVED RESULT
It clicks Audacious taskbar icon.

EXPECTED RESULT
Opens the application menu.

SOFTWARE/OS VERSIONS 
Linux/KDE Plasma: KDE neon User Edition 5.21.4
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
some parts of the application menu can still be clicked when this issue happens.
Comment 1 Ahmed 2021-10-27 16:08:10 UTC
The issue still happens on the latest KDE Plasma version 5.23.2
Comment 2 Nate Graham 2024-06-18 17:01:11 UTC
Can you attach a screen recording that shows the issue?
Comment 3 Ahmed 2024-06-19 11:39:43 UTC
(In reply to Nate Graham from comment #2)
> Can you attach a screen recording that shows the issue?

I am sorry, I found out that this issue was happening because of the "Status Icon" I added from "Plugins", but the application does not show "Status Icon" when choosing "GTK Theme", but it is shown after switching to "QT Interface" from "Settings". I guess the developers of "Audacious" did that to avoid this issue, and they added the "QT Interface" to give better support for KDE Plasma, which is a nice addition.

To sum things up: The issue can not be reproduced with KDE Plasma version 5.27.11, and the latest version of "Audacious".