KDE Plasma 6 Wayland session has a significant menubar focus bug

So with KDE 6, X11 support is sub-par… so I am attempting to switch to Wayland because I see a noticeable framerate drop when shaking the wobbly windows in an X11 session. Of course this doesn’t mean Wayland performs better than X11, it just means the KDE devs don’t care enough to fix KDE 6 X11 support and make it performas good as KDE 5 did.

Anyway, there’s a pretty big bug now with the Dr460nized Mac-like menubar under Wayland (this does not happen in X11)…

Applications now lose focus when they open a child window. The menubar will lose all its menus and just say “Dr460ized KDE” as if you clicked the desktop When the window closes it does not properly return focus to theapplication. Some apps will be stuck in this state and you can’t get focus with menu options in the bar untilyou click something else (another app or the desktop) and then back to the application window. Others will go into a weird mixed up state where it will say “Dr460ized KDE” but the menu options come back.

In GIMP if you open filter dialog, the menubar changes from GIMP to this “Dr460ized KDE” state. If you cancel the filter dialog, rather than returning to say “GNU Image Manipulation Program”, it will still say “Dr460ized KDE”… however the GIMP menus are also there.

Other apps such as Quartus Prime will get stuck in a state with no menubar if you open and then close a child window. You have to click off and on to get it back. This is extremely disrupting to workflow, as well as feeling extremely broken. Unfortunately clicking the menubar or dock icon doesn’t even return focus to the menubar.

I avoided switching to Wayland under KDE 5 because it wasn’t ready. Now we’re basically forced to switch via KDE 6 and it still isn’t ready. But really I’m not sure what side of everything is responsible for this bug? Wayland? KDE 6? Both?

There’s only one solution I’ve found to get around this bug (besides switching back to X11 and dealing with bad performance and other bugs)… focus follows mouse. I’d love to use focus follow mouse except for one major issue… it’s not very well suited for the menubar because moving the mouse between a window and the menubar often causes you to lose focus by the time you get there… if not from crossing another window, it happens constantly by the useless desktop stealing focus.

Is there any way to make the desktop unable to steal focus? I don’t even use folder view, I don’t need the desktop at all. If I could just have a wallpaper that is completely non-interactive, that would be great. I’m guessing this is impossible though.

System:
Kernel: 6.8.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=e47b5a22-506c-4573-b60f-520b613f7533 rw rootflags=subvol=@
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
drm.edid_firmware=DisplayPort-0:/edid/Samsung-EDID-RGB.bin intel_iommu=on
iommu=pt vfio-pci.ids=10de:1d01,10de:0fb8 ibt=off
Desktop: KDE Plasma v: 6.0.2 tk: Qt v: N/A info: frameworks v: 6.0.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: Z690 AERO D v: -CF
serial: <superuser required>
Mobo: Gigabyte model: Z690 AERO D serial: <superuser required>
uuid: <superuser required> UEFI: American Megatrends LLC. v: F28
date: 12/14/2023
CPU:
Info: model: 13th Gen Intel Core i7-13700K bits: 64 type: MST AMCP
arch: Raptor Lake gen: core 13 level: v3 note: check built: 2022+
process: Intel 7 (10nm) family: 6 model-id: 0xB7 (183) stepping: 1
microcode: 0x122
Topology: cpus: 1x cores: 16 mt: 8 tpc: 2 st: 8 threads: 24 smt: enabled
cache: L1: 1.4 MiB desc: d-8x32 KiB, 8x48 KiB; i-8x32 KiB, 8x64 KiB
L2: 24 MiB desc: 8x2 MiB, 2x4 MiB L3: 30 MiB desc: 1x30 MiB
Speed (MHz): avg: 3029 high: 5300 min/max: 800/5300:5400:4200 scaling:
driver: intel_pstate governor: powersave cores: 1: 5170 2: 800 3: 5300
4: 800 5: 5300 6: 800 7: 5300 8: 800 9: 800 10: 5300 11: 5300 12: 5300
13: 5300 14: 800 15: 4827 16: 800 17: 800 18: 4190 19: 4244 20: 800
21: 800 22: 4186 23: 4187 24: 800 bogomips: 164044
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6950 XT] vendor: XFX driver: amdgpu
v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22
pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1 empty: DP-2,
DP-3, HDMI-A-1, Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:73a5
class-ID: 0300
Device-2: NVIDIA GP108 [GeForce GT 1030] vendor: Micro-Star MSI
driver: vfio-pci v: N/A alternate: nouveau non-free: 545.xx+ status: current
(as of 2024-02; EOL~2026-12-xx) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 4
link-max: gen: 3 speed: 8 GT/s bus-ID: 04:00.0 chip-ID: 10de:1d01
class-ID: 0300
Device-3: Razer USA Gaming Webcam [Kiyo] driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4.1:7
chip-ID: 1532:0e03 class-ID: 0102
Device-4: MacroSilicon USB Video
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4.4:9 chip-ID: 534d:2109
class-ID: 0300
Device-5: Elgato Systems GmbH Game Capture HD60 X
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 3.0
speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-2.1:4
chip-ID: 0fd9:0082 class-ID: 0300 serial: <filter>
Device-6: AVerMedia USB Device driver: snd-usb-audio,uvcvideo type: USB
rev: 3.0 speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-3.2:8
chip-ID: 07ca:0110 class-ID: 0102 serial: <filter>
Display: wayland server: X.org v: 1.21.1.11 with: Xwayland v: 23.2.4
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu,vfio-pci display-ID: 0
Monitor-1: DP-1 res: 3840x2160 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
drv: radeonsi inactive: gbm
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.3-arch1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6950 XT (radeonsi
navi21 LLVM 17.0.6 DRM 3.57 6.8.1-zen1-1-zen) device-ID: 1002:73a5
memory: 15.62 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 13 device: 0 type: discrete-gpu name: AMD
Radeon RX 6950 XT (RADV NAVI21) driver: mesa radv v: 24.0.3-arch1.2
device-ID: 1002:73a5 surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
v: 24.0.3-arch1.2 (LLVM 17.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel Alder Lake-S HD Audio vendor: Gigabyte driver: snd_hda_intel
v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3
chip-ID: 8086:7ad0 class-ID: 0403
Device-2: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel
pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-3: NVIDIA GP108 High Definition Audio vendor: Micro-Star MSI
driver: vfio-pci alternate: snd_hda_intel pcie: speed: Unknown lanes: 63
link-max: gen: 6 speed: 64 GT/s bus-ID: 04:00.1 chip-ID: 10de:0fb8
class-ID: 0403
Device-4: PreSonus Audio AudioBox USB driver: snd-usb-audio type: USB
rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-12.3:18
chip-ID: 194f:0302 class-ID: 0103
Device-5: Giga-Byte USB Audio driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-2:2
chip-ID: 0414:a00b class-ID: 0300
Device-6: Razer USA Gaming Webcam [Kiyo] driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4.1:7
chip-ID: 1532:0e03 class-ID: 0102
Device-7: MacroSilicon USB Video
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4.4:9 chip-ID: 534d:2109
class-ID: 0300
Device-8: Emagic Soft- und Hardware GmbH Unitor8 driver: snd-usb-audio
type: USB rev: 1.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-8.4.2:23
chip-ID: 086a:0001 class-ID: ff00
Device-9: Elgato Systems GmbH Game Capture HD60 X
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 3.0
speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-2.1:4
chip-ID: 0fd9:0082 class-ID: 0300 serial: <filter>
Device-10: AVerMedia USB Device driver: snd-usb-audio,uvcvideo type: USB
rev: 3.0 speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-3.2:8
chip-ID: 07ca:0110 class-ID: 0102 serial: <filter>
API: ALSA v: k6.8.1-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.0.4 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Alder Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:7af0 class-ID: 0280
IF: wlo1 state: up mac: <filter>
Device-2: Aquantia AQC113C NBase-T/IEEE 802.3an Ethernet [Marvell
Scalable mGig] vendor: Gigabyte driver: atlantic v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 2 port: N/A bus-ID: 09:00.0 chip-ID: 1d6a:14c0
class-ID: 0200 temp: 42.0 C
IF: enp9s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-3: Intel Ethernet I225-V vendor: Gigabyte driver: igc v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 0a:00.0
chip-ID: 8086:15f3 class-ID: 0200
IF: enp10s0 state: down mac: <filter>
IF-ID-1: virbr0 state: down mac: <filter>
Info: services: NetworkManager, smbd, sshd, systemd-timesyncd,
wpa_supplicant
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:21 chip-ID: 8087:0033
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 16.61 TiB used: 1.75 TiB (10.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:4 vendor: Western Digital
model: WD BLACK SN770 1TB size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 731100WD temp: 54.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital
model: WD BLACK SN850X 2000GB size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 620331WD temp: 48.9 C scheme: GPT
ID-3: /dev/nvme2n1 maj-min: 259:3 vendor: Western Digital
model: WD BLACK SN770 1TB size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 731100WD temp: 58.9 C scheme: GPT
ID-4: /dev/sda maj-min: 8:0 vendor: HGST (Hitachi) model: HUS724040ALA640
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: AA70 scheme: GPT
ID-5: /dev/sdb maj-min: 8:16 vendor: HGST (Hitachi) model: HUS724040ALA640
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: AC50 scheme: GPT
ID-6: /dev/sdc maj-min: 8:32 vendor: SanDisk model: X110 2.5 7MM 256GB
size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 412 scheme: GPT
ID-7: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST2000DM008-2FR102
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: 0001 scheme: GPT
ID-8: /dev/sde maj-min: 8:64 vendor: HGST (Hitachi) model: HMS5C4040BLE640
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5700 serial: <filter> fw-rev: A5D0 scheme: GPT
Partition:
ID-1: / raw-size: 1.82 TiB size: 1.82 TiB (100.00%) used: 1.12 TiB (61.5%)
fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 2.1 MiB (0.7%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:1
ID-3: /home raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 1.12 TiB (61.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 1.12 TiB (61.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 1.12 TiB (61.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 62.62 GiB used: 393.8 MiB (0.6%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 24
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 38.0 C mobo: N/A gpu: amdgpu temp: 40.0 C
mem: 44.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 64 GiB note: est. available: 62.62 GiB used: 7.84 GiB (12.5%)
Processes: 547 Power: uptime: 13h 36m states: freeze,mem,disk
suspend: deep avail: s2idle wakeups: 0 hibernate: platform avail: shutdown,
reboot, suspend, test_resume image: 25.01 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2384 libs: 619 tools: octopi,paru,yay
Compilers: clang: 17.0.6 gcc: 13.2.1 Shell: garuda-inxi default: Bash
v: 5.2.26 running-in: konsole inxi: 3.3.33
Garuda (2.6.23-1):
System install date:     2023-05-03
Last full system update: 2024-03-23
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:

Options I see are

I believe you were in the right place to manage this.

Unfortunately none of the options prevent the desktop from stealing focus with this bug. The problem is when applications open new windows they somehow inherit the desktop’s menubar (meaning no menubar at all)… but when the window closes it stays this way. KDE thinks the window has focus because clicking on it does nothing. It does have focus but the menubar does not, and forever remains as a blank “Dr460ized KDE” menu that does nothing.

The other options that have focus based on the mouse position get around this and will reset the menu to the correct window, but crossing over the useless desktop will take it away.

This bug is intolerable.

Wayland was a huge mistake.

What’s Quartus Prime’s package name?

And by “menu” do you mean this?
image

Yes. The menubar at the top of the screen.

Quartus Prime is AUR package quartus-free-quartus

It seems like everything under Wayland experiences this bug, it’s just most apps don’t lock you out from the menu, it just looks buggy.

If you compare the menubar behaviour between X11 and Wayland, you will see it never changes while you are in the same app under X11. Under Wayland it’s constantly switching back and forth to “Dr460nized KDE”.

Yeah, sounds like a good bug to create at bugs.kde.org.
Just switching between X and W and seeing a different behavior is, I believe, a good indication, or at least a good start for some Wayland expert to take a look.

EDIT: It may also be related directly to the Global Menu widget. Maybe that’s the one to file the bug against.

1 Like

I found the bug has already been reported, but doesn’t seem to have been marked as Wayland specific…

https://bugs.kde.org/show_bug.cgi?id=483075

I will try to give them more information.

2 Likes

The bug is marked as CONFIRMED so that’s very good!

Yes providing the info you experience it only under Wayland may help them figure it out.

2 Likes

Oh also I think I was confused about the desktop grabbing focus. I guess the desktop isn’t really a thing that can have focus, it’s just clicking on the desktop drops the focus from everything else.

Focus follows mouse doesn’t have a problem with the mouse cursor crossing across the desktop, it’s just other windows that will steal its focus. But actually, FFM isn’t a way to get around this bug anyway…

Focus UNDER mouse seems to be the best way to deal with this bug until they fix it. When it is in that mode it doesn’t seem to lose focus from child windows and the global menu never disappears. You only have to deal with the problem of other windows stealing your focus. “Focus strictly under mouse” seems to also work.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.