Bug 479734 - Media keys [fn] work on KDE x11 session, not on KDE Wayland (but do work on Gnome Wayland)
Summary: Media keys [fn] work on KDE x11 session, not on KDE Wayland (but do work on G...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: usability, wayland
Depends on:
Blocks:
 
Reported: 2024-01-13 11:57 UTC by Damian
Modified: 2024-03-01 06:10 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Damian 2024-01-13 11:57:45 UTC
SUMMARY
Media keys (e.g.: [fn] + [f10] for volume down) do work on KDE x11 session, but do not on KDE Wayland (but do work on Gnome Wayland).

STEPS TO REPRODUCE
1. Install fedora gnome workstation
2. run `dnf groupinstall "KDE Plasma Workspaces"`
3. get on KDE Wayland
4. Try to use a media key in your keyboard like [fn]+[f10] (volume down in my case)

OBSERVED RESULT
Nothing happens

EXPECTED RESULT
Volume going down

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 39
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Kernel Version: 6.6.9-200.fc39.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15,6 GiB of RAM
Graphics Processor: AMD Radeon RX 5700 XT
Manufacturer: Micro-Star International Co., Ltd
Product Name: MS-7C02
System Version: 1.0

ADDITIONAL INFORMATION
- command `sudo showkey` registers those correctly ("keycode 114 press", "keycode 115 press" etc.)
- command `xev` doesn't detect them at all

- command `setxkbmap -print -query` returns:
WARNING: Running setxkbmap against an Xwayland server
xkb_keymap {
        xkb_keycodes  { include "evdev+aliases(qwerty)" };
        xkb_types     { include "complete"      };
        xkb_compat    { include "complete"      };
        xkb_symbols   { include "pc+us+inet(evdev)"     };
        xkb_geometry  { include "pc(pc105)"     };
};
rules:      evdev
model:      pc105
layout:     us
Comment 1 Nate Graham 2024-02-15 21:57:29 UTC
I suspect your method of installation has caused this problem. Those keys are handled by different parts of the system that don't all come pre-packaged. The volume keys for example are handled by software provided in the "plasma-pa" package. So if that's not installed, install it, reboot, and try again. If that doesn't work, can you try again in a new user account, or in a new installation of Fedora KDE on its own?
Comment 2 Damian 2024-02-29 13:50:32 UTC
(In reply to Nate Graham from comment #1)
> I suspect your method of installation has caused this problem. Those keys
> are handled by different parts of the system that don't all come
> pre-packaged. The volume keys for example are handled by software provided
> in the "plasma-pa" package. So if that's not installed, install it, reboot,
"plasma-pa" is already installed

> and try again. If that doesn't work, can you try again in a new user
> account, or in a new installation of Fedora KDE on its own?
A new user account indeed is working
Comment 3 Nate Graham 2024-03-01 06:10:45 UTC
Thanks. That means there's something wrong with the configuration of your user account. Perhaps kglobalaccel is not running? Either way, please follow up with your distro for details on resolving this.