Bug 514155

Summary:	unity3d editor menus have incorrect state
Product:	[Plasma] kwin	Reporter:	Emilio Cobos Álvarez (:emilio) <emilio>
Component:	appmenu	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	normal	CC:	kdedev, nate
Priority:	NOR
Version First Reported In:	6.5.4
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Emilio Cobos Álvarez (:emilio) 2026-01-04 18:28:42 UTC

SUMMARY

The menus in unity3d's editor show incorrectly disabled when moved to the global menu or dealing with them natively. Note this application is terrible in other ways (broken scaling, X11 only, etc), but filing because I do think something is fishy and the background services KCM was persistent :)

STEPS TO REPRODUCE
1. Download unity hub from https://unity.com/download
2. Create an empty project and open the editor. I'm using [this version](https://unity.com/releases/editor/whats-new/6000.3.2f1)

OBSERVED RESULT

1. Notice how most menus are disabled (like "File > New scene"), but Ctrl+N works.

EXPECTED RESULT

2. Menus work as expected.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.11.0
Kernel Version: 6.18.3-arch1-1 (64-bit)
Graphics Platform: X11 or wayland both reproduce this

ADDITIONAL INFORMATION

Running `kcmshell6 kcm_kded` and disabling the Application menus daemon fixes this.

Without it the menus are rather slow and non-responsive.

Comment 1 Nate Graham 2026-01-06 22:53:43 UTC

> or dealing with them natively
As in, when the menus are in the window, accessed from an in-window menubar?

> Running `kcmshell6 kcm_kded` and disabling the Application menus daemon fixes this.
Even when the menus are accessed from an in-window menubar?

Comment 2 Emilio Cobos Álvarez (:emilio) 2026-01-07 00:13:32 UTC

(In reply to Nate Graham from comment #1)
> > or dealing with them natively
> As in, when the menus are in the window, accessed from an in-window menubar?

Yes

> > Running `kcmshell6 kcm_kded` and disabling the Application menus daemon fixes this.
> Even when the menus are accessed from an in-window menubar?

When reporting this, I couldn't get the in-window menubar to work reliably with the applications menus daemon. Now it seems to work, but very slowly... It seems this application does something extremely stupid when showing a menu. Like it's creating thousands of threads / processes on my machine. Perf reports most of the time being spent on glycin...

I'm willing to bet that kind of slowness is also what's causing the global menu to misbehave...

Comment 3 Nate Graham 2026-01-08 18:29:51 UTC

If it affects the in-window menus, it's not clear that there's a bug in KDE code here. As you say, it seems highly likely that that app itself is doing something weird and non-standard that's causing the issue.