Org.kde.plasma.keyboardindicator is flooding my logs

What the title says. I did a system update a couple of days ago and since then my journalctl logs have been flooded with plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt. My system has always been plagued with issues of all kinds and right when I thought I finally had a break this thing popped up. It looks harmless to me but I just dont want my logs to be filled with unnecessary stuff.

The culprit seems to be a plasma widget that goes by the same name (Plasma Keyboard Indicator) which hasn’t been updated for over 6 years. Wonder what was changed last week for it to flare up now. I say that because its popping in the logs people are posting in the last few days like here. Its usually ignored. Also the widget seems to be preinstalled so there’s no way to remove it via the widget GUI. Kind of annoying why thats even a thing for an unimportant widget.

Here’s what journalctl -b | tail -n50 looks like:

Jun 27 14:53:15 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:53:15 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:19 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:19 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:19 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:19 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:19 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:19 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:19 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:19 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:20 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:20 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:20 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:20 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:20 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:20 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:20 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:20 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:20 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:20 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:20 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:20 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:20 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:20 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:20 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:20 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt
Jun 27 14:57:28 ThisPC plasmashell[2986]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt

Goes without saying this goes on forever.

Here’s the garuda-inxi output:

System:
Kernel: 6.9.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=0a9d7354-fca7-4660-8bdd-55e14210438b rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.1.1 tk: Qt v: N/A info: frameworks v: 6.3.0
wm: kwin_wayland with: krunner vt: 1 dm: SDDM Distro: Garuda
base: Arch Linux
Machine:
Type: Laptop System: Dell product: Vostro 15-3568 v: N/A
serial: <superuser required> Chassis: type: 9 serial: <superuser required>
Mobo: Dell model: 05HRPP v: A00 serial: <superuser required> part-nu: 0793
uuid: <superuser required> UEFI: Dell v: 3.3.0 date: 01/17/2019
Battery:
ID-1: BAT0 charge: 21.5 Wh (100.0%) condition: 21.5/41.4 Wh (51.8%)
volts: 16.7 min: 14.8 model: SMP DELL VN3N047 type: Li-ion serial: <filter>
status: full
CPU:
Info: model: Intel Core i3-6006U bits: 64 type: MT MCP arch: Skylake
gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
model-id: 0x4E (78) stepping: 3 microcode: 0xF0
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 425 high: 500 min/max: 400/2000 scaling:
driver: intel_pstate governor: powersave cores: 1: 400 2: 400 3: 500 4: 400
bogomips: 15999
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Dell driver: i915
v: kernel arch: Gen-9 process: Intel 14n built: 2015-16 ports: active: eDP-1
empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:1916
class-ID: 0300
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.0
compositor: kwin_wayland driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 0
Monitor-1: eDP-1 res: 1366x768 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast surfaceless: drv: iris wayland: drv: iris x11:
drv: iris inactive: gbm
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.1.2-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 520 (SKL GT2)
device-ID: 8086:1916 memory: 5.64 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 13 device: 0 type: integrated-gpu
name: Intel HD Graphics 520 (SKL GT2) driver: mesa intel v: 24.1.2-arch1.1
device-ID: 8086:1916 surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
v: 24.1.2-arch1.1 (LLVM 17.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel
v: kernel alternate: snd_soc_skl,snd_soc_avs bus-ID: 00:1f.3
chip-ID: 8086:9d70 class-ID: 0403
API: ALSA v: k6.9.6-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.0.7 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: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
vendor: Dell driver: ath10k_pci v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 bus-ID: 01:00.0 chip-ID: 168c:0042 class-ID: 0280
IF: wlp1s0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Dell driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0 state: down mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Qualcomm Atheros driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-8:5 chip-ID: 0cf3:e009
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: <filter> bt-v: 4.2 lmp-v: 8
status: discoverable: no pairing: no
Drives:
Local Storage: total: 931.51 GiB used: 437.74 GiB (47.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000LM035-1RK172
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5400 serial: <filter> fw-rev: SDM2 scheme: GPT
Partition:
ID-1: / raw-size: 247.62 GiB size: 247.62 GiB (100.00%)
used: 198.91 GiB (80.3%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 600 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 247.62 GiB size: 247.62 GiB (100.00%)
used: 198.91 GiB (80.3%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 247.62 GiB size: 247.62 GiB (100.00%)
used: 198.91 GiB (80.3%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 247.62 GiB size: 247.62 GiB (100.00%)
used: 198.91 GiB (80.3%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 11.55 GiB used: 718.5 MiB (6.1%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 52.0 C pch: 50.5 C mobo: 50.0 C
Fan Speeds (rpm): cpu: 0
Info:
Memory: total: 12 GiB available: 11.55 GiB used: 3.88 GiB (33.6%)
Processes: 250 Power: uptime: 16h 8m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 4.61 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2040 libs: 607 tools: pamac,paru Compilers:
clang: 17.0.6 gcc: 14.1.1 Shell: garuda-inxi default: fish v: 3.7.1
running-in: konsole inxi: 3.3.35
Garuda (2.6.26-1):
System install date:     2023-11-17
Last full system update: 2024-06-27 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:

There seems to be a reported bug on this here: 488870 – When opening a new window, journal is flooded with "org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt"
However, Nate Graham could not reproduce this bug. Does your log spam also start from opening new windows (example given on report was opening a new window in Konsole)? Maybe you could chime in on this bug with any additional information you can find out.

4 Likes

You can ignore this.

The org.kde.plasma.keyboardindicator is a KDE system widget under /usr/share/plasma/plasmoids/org.kde.plasma.keyboardindicator/ which shows you the status of the lock keys of your keyboard (for example “Caps Lock”) and has nothing to do with user-created "Plasma Keyboard Indicator Widget` from the KDE store.

3 Likes

I have seen it even on a fresh reboot so I cant tell when or how it starts but based on some testing I can say for sure opening new windows is not the only cause. For me any interaction with the kde/plasma ecosystem generates a fresh set of log spam, including but likely not limited to:

  • Opening new windows of kde apps like konsole and dolphin
  • Hovering over apps and widgets on the desktop panel long enough for the tooltip to generate
  • Switching between windows of kde apps like konsole and dolphin using icons on the desktop panel
  • Switching between windows of apps (any not just kde ones) by Alt-Tab-ing

Interactions within the apps doesnt generate anything so it’s either something related to the window manager or the main desktop panel that comes by default since I have a couple of side panels with a widget or two and they dont generate anything either when interacted with. I guess I’ll add this to the bug report and see if Nate finds anything.

1 Like

Aah I see. I looked at the about section of the preinstalled widget and the author names were quite similar so I assumed it’s the same one from the KDE store.

Also it’s under /usr/share huh. I dont know why but I was looking under .local/share and was confused when I found nothing. I know you just said I can ignore it but do you think its safe to remove the folder as a quick fix? :smiley:

Edit: nvm looking through the .qml file I dont think the widget itself is capable of the log spam. Probably something it’s using from upstream.

I don’t have /usr/share/plasma/plasmoids/org.kde.plasma.keyboardindicator/ on Arch/KDE and KaOS and none of these messages in the journal. It is installed on Garuda and is cluttering up the journal.

I don’t know which kde/plasma package this widget comes from. To be on the safe side, make a backup of the folder and delete the original (or simply rename the folder), then reboot and test.

1 Like

Garuda KDE

/usr/share/plasma/plasmoids/org.kde.plasma.keyboardindicator/
├── contents
│   ├── config
│   │   ├── config.qml
│   │   └── main.xml
│   └── ui
│       ├── configAppearance.qml
│       └── main.qml
└── metadata.json

4 directories, 5 files

I tried it. Didnt work. The widget did get removed when I deleted the folder but the log spam is still there. So it’s definitely not the the widget itself.

First of all, the correct way is to find which package this folder belongs to, and then remove that package, if it is possible (it could be a dependency for other important packages).

pacman -Qo /usr/share/plasma/plasmoids/org.kde.plasma.keyboardindicator
sudo pacman -R <owner-package>

After this is removed (in any way), create a new user acoount and login to check if the messages are also in the new user’s journal log.

The message looks like it is a Qt issue, rather than KDE, unless there are some old configuration files.
You may search for files with relevant text in $HOME files contents.

grep -slir "keyboardindicator" $HOME/*
grep -slir "Key_Alt" $HOME/*
grep -slirE "\bAlt\b" $HOME/*

Deleting ~/.cache/* and relogin, should not harm.

3 Likes

I went through it quickly: the keyboardindicator is included in kdeplasma-addons, which in turn has qt6-quick3d and qt6-quicktimeline as dependencies. These are exactly the packages that are not installed on my other systems and have no messages in the journal.

As I said, you can ignore the messages in the journal. But if it is so important to you, then go through the steps that @petsam suggested.

There is another possibility…just don’t look in the journal :smile:

2 Likes

If the journal fills with garbage, then

  1. it gets difficult to see other important messages
  2. it needs a proper configuration in sysctl IIRC for max disk space

This package is not super-important and can be removed, until the real source of the issue is discovered somehow. :person_shrugging:

sudo pacman -R kdeplasma-addons
2 Likes

That’s not the cause - you guessed right, the QT stuff is the cause :slight_smile:

1 Like

Thanks a lot for the help guys @nepti and @petsam. Really appreciate it. By now I’ve done pretty much everything in here. Tldr: nothing worked

  • Removed the parent package kdeplasma-addons and logged in as a new user
  • Deleted ~/.cache/ and relogged in
  • Searched using grep. Didnt find anything unusual
  • Downgraded all the QT dependencies to a previous version one by one including qt6-quick3d and qt6-quicktimeline. The only one I didnt was qt6-base, which I learned would be a bad idea when I downgraded qt6-declarative and found out it broke everything including the sddm so I had to reload the snapshot. And I’m too lazy to downgrade every single package depending on qt6-base. Way too many.

Though I did find something that worked while mucking around and its to break plasmashell using strace. Now I dont know what’s going on under the hood but this what I did. I thought I’ll try tracing back the process and so downloaded strace and attached it to the PID in the error log which I assume is for plasmashell because its says so in the log. When I saw the output it was evident I had no clue what I was doing so I Ctrl-Z`ed myself out. Which broke plasmashell I suppose since nothing worked including the widgets, panels and even the desktop. I could still use the system just fine using krunner, desktop peek and alt-tab. Most importantly, there were no more of those logs. The journal was squeaky clean after a whole week of garbage spam. Bit of a caveman like but functional solution.

Yup, what @petsam said. My system is quite error prone and looking at the journal is almost second nature by now. A journal with 90% junk while taking several times the storage wouldnt be very useful. And I feel like programs launch much slower now with the log spam but that could be just placebo. I also run a couple of containers and scripts in the background whose logs appear in the journal. Quite nice for debugging purposes and finding any system related causes.

Thats about it. I didnt touch plasmashell or its parent package plasma-workspace because its way beyond my scope of knowledge. But if anyone has any ideas or more elegant solutions do let me know. I dont mind trying them. Like is there a way to maybe prevent plasmashell from making any logs? That would be good enough for me

1 Like

And the whole thing was about meaningless messages in the journal that are only of interest to the developers of the software in question :laughing:

I’m sure that was the only solution :rofl:


Jokes aside, you have a different user case than I do.

Personally, I never filter logs, no matter what they are about. No color highlighting, no explicit search for errors or warnings, and no exporting to external applications for better readability.

Plain text in the editor and reading everything from start to finish - for irrelevant messages like the one in this topic, I just scroll over them. If you only display what is supposedly important, you quickly overlook the actual cause. But as I said, you have a different user case.

I like your style btw :+1:
Good luck :slightly_smiling_face:

1 Like

There seems to be more info, and has been confirmed here as a duplicate of this: 484992 – Xwayland apps get Tab keyboard events even when they should be filtered out by event filter
Has to do with xwayland applications and forwarded keystrokes it seems. (In a Wayland session to have the option to have X11 apps to always be able to read all keystrokes).

At least it would seem from the labeling in the bug tracker, but something doesn’t match up at all :thinking:
After testing that setting (in KDE Settings turning the “Legacy X11 App Support” keystroke read options to “Never” and restarting the computer), the log is still spammed… I think there is more at play here, and that bug 488870 might be erroneously labeled as a duplicate of 484992. (Naxdy’s post in 488870 – When opening a new window, journal is flooded with "org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt" also reports the same findings with that setting)

1 Like

The messages are triggered by the “Global Menu” in the “Application Menu Bar” as soon as you open an application (for example Dolphin, Kate etc.).
If you remove the “Application Menu Bar”, the messages disappear.
If you create a new empty “Application Menu Bar”, the messages appear again.
If you remove the “Global Menu” from the empty “Application Menu Bar”, the messages disappear again.

It is also clear from the journal what happens first:

kded6[1656]: org.kde.plasma.appmenu: Got an error

and after:

plasmashell[1697]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt

I can reproduce it on “Garuda dr460nized”, “Garuda kde-lite” and “EndeavourOS/KDE” with kded version 6.3.0-1.

I could not reproduce it on KaOS - KaOS uses kded version 6.3.0-2.

2 Likes

Same Issue here. First how I got here.

I miss my application menu in KeepassXC like described in this Github Issue here. The guy who opened the issue opened this KDE Bug Report and the solution was to install manually plasma5-integration. But that didn’t fix it for me. I’m not sure if this is related to my missing application menu, but now I’m here. :smiley:

PS: I’m running Garuda Linux, obviously with KDE

Edit: Nvm, I’m not missing the application menu this guy Kai missed, I miss the normal menu bar? (Idk how it is called). Normally it appears if you press Alt-Key.

Recent garuda-update updated kded to 6.4.0-1
Still getting the spam on the logs.
I’m keeping my eyes on 488870 – When opening a new window, journal is flooded with "org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt" for when hopefully Naxdy might report back something new.

Edit: changed the topic title here to hopefully be something a little more search friendly since this issue has been ongoing for some time.

1 Like