After upgrade to Plasma 6.5.1 - key F12 (global) shortcut stopped working?

Anybody can test/confirm? I can then report a bug.

I use it open Yakuake. Now it seems to be working only from Desktop, but not when other apps are focused.

No issues here.

  • Did you try a new USER?

  • Did you look at keyboard shortcuts?

  • Did you try adding an additional shortcut like: CtrlAltY to see if that worked?

Do you actually use Yakuake?

I have logged out to test it again, but the same behavior, no Yakuake shown on F12 when other apps in focus, while on Desktop it opens.

I always test and verify before making absolute statements (as opposed to random guesses).

Info
Operating System: Manjaro Linux 
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.6-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics
Memory: 17 GB of RAM (16.1 GB usable)
Graphics Processor: AMD Radeon Graphics
Product Name: B550M Steel Legend

Cool, it was quick then. I can however confirm it happening here unfortunately.

Interestingly, Yakuake window will show when KRunner is displayed or when some KDE dialog is open (or window such as Shortcuts config…). Seems to be some weird Plasma config issue then. That maybe Yakuake is displayed but below any other apps (e.g. Firefox browser).

Indeed: When Firefox is not maximized (not fullscreen mode, just maximized), Yakuake will show. Once it’s maximized, it won’t show.

Yet you only logged out and in again, with the same USER data and settings.

You did not yet confirm it happening on a new profile/USER.

The first thing I do to verify any kind of issue or bug is to switch user to my TEST user.

It’s 99% likely something in your own $HOME.

Sure that does not resolve anything, though. If I have some Plasma setting that is observed, the it does not matter that resetting profile will remove the bug. The bug will still appear on the same config set.

It absolutely does resolve the question of whether this is an issue only with your config or HOME folder data.

If creating a TEST user clears the issue, then you can drill down to your home…

Without any finesse, I resort to my ‘brainless’ method as follows:

Brute force troubleshooting…

mv ~/.config ~/.configBORKED

  • logout and log back in again to force plasma to recreate the folder with default settings
    dolphin --split ~/.config ~/.configBORKED
  • copy back half of the BORKED folder contents at a time and relog to see if issue returns
  • if it does, then delete the folder again, relog, and only copy half of that previous half
  • repeat until the culprit is found, then finally, copy back everything BUT that culprit
1 Like

Indeed this is the issue (maximized windows will cover Yakuake).

Nope, you seems to miss the point. The point is that maximized windows obscure Yakuake, i.e. Yakuake does open, but in the background and it is somehow overshadowed by other maximized windows.

My Yakuake is configured as such:

Yet you still didn’t verify this on a test user, right?

I can confirm that Yakuake opens normally if I have PlexHTPC playing windowed, maximised and fullscreen.

1 Like

Check a test account as suggested.

delete the directory “.local/share/yakuake” from your home directory
delete the file “.config/yakuake” from your home directory

Launch yakuake with f12 again, and reconfigure.

Check your settings for desktop effects (ksettings/animations).

1 Like

LLMs to the help and creating appropriate KWin Windows Rule:

Yup, with solutions like this I’m not surprised your Plasma is broken…

With comments like yours making fun of users (“pebkac”) I am not surprised this community feels less welcoming.

1 Like

I have changed Window behavior under Focus stealing from Medium to Low. This seems to fix the issue (I have deactivated the Yakuake KWin rule to verify this). It seems that having focus stealing set to Medium has somehow confused Plasma after upgrading to 6.5.1.

1 Like

Here’s the bug report you’re after: https://bugs.kde.org/show_bug.cgi?id=509990

2 Likes

Ah, thanks. So it’s a bug.

Some commenters were just too sure of themselves to jump to conclusions and blame the user. Fortunately there are others in this community who are really helpful.

1 Like

I had the same issue and the same change (focus stealing from Medium to Low) did help also in my case.

I can’t recall if I did use Medium focus stealing before update, so not sure if it was the 6.5.1 changing my focus stealing setting, or breaking the yakuake window placement/z-index

I tried also to set up yakuake as “maximized” window and that did seems to expose another bug with dual monitor setup (laptop screen under LCD), putting the yakuake window “between” them, but not raising it above other windows either.

(JFYI post, that you are not alone :slight_smile: )

1 Like