Bug 511015

Summary:	Yakuake opens under active window
Product:	[Applications] yakuake	Reporter:	Miroslav Jarý <mira.jary>
Component:	general	Assignee:	Eike Hein <hein>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	mat.mueller, nate
Priority:	NOR
Version First Reported In:	25.08.2
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Miroslav Jarý 2025-10-24 12:29:05 UTC

SUMMARY
When I try to open Yakuake, it always opens under the currently active window.

STEPS TO REPRODUCE
1. Open any window (e.g. Firefox)
2. Try to open Yakuake (by keyboard shortcut or the task bar icon)

OBSERVED RESULT
Yakuake opens under the previously focused window

EXPECTED RESULT
Yakuake opens in front of the previously focused window

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.0
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.4-zen2-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 12 × 13th Gen Intel® Core™ i5-13420H
Memory: 32 GiB of RAM (31,1 GiB usable)
Graphics Processor 1: Mesa Intel® Graphics
Graphics Processor 2: NVIDIA GeForce RTX 4050 Laptop GPU/PCIe/SSE2
Manufacturer: LENOVO
Product Name: 82XV
System Version: LOQ 15IRH8

ADDITIONAL INFORMATION

Comment 1 Matthias Mueller 2025-10-25 06:31:09 UTC

I can confirm this after updating to Plasma 6.5 yesterday (Arch) - yakuake was NOT updated!

I also notice that this only occurs when invoking yakuake with F12 - if i run it from krunner, it appears on top.

Comment 2 Matthias Mueller 2025-10-25 11:00:19 UTC

Another observation: it seems to be related to (assumed?) changes in the focus stealing prevention.
If i set it to low or none, everything works fine. If it is set to medium or above, yakuake doesn't take focus. 

I noticed this after creating a window rule that would keep yakuake always on top. That workaround solved the visibility issue, but even then, the focus would not be switched to yakuake after summoning it with F12.

I think it might be caused by https://bugs.kde.org/show_bug.cgi?id=509990 ?

Comment 3 Nate Graham 2025-10-25 15:53:38 UTC


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