With KDE6’s floating panel set to the top of the screen, Yakuake loads “under” it and hides the first lines. Setting a KWin Rule to have the app start “lower” down the screen works, at first, but only then; that is, after hiding Yakuake after the first use, it hides behind the panel again. I have the KWin Rule set to “force,” but I guess that’s not what I should be looking for. Any help?
Thanks!
Added f40, kde, kde-plasma
Not sure if this will help you, but I’ll take a chance. On the panel, you can right click on enter edit mode. Then, you should see panel settings and within that visibility. The default I believe is always visible. Try windows go below. Hope that helps!
Ooh, great thought; sadly, no dice.
After I submitted that suggestion, I tried it and it worked for me in a VM. Maybe I’m misunderstanding what you are trying to do. What I did was set the panel to the top, set windows to always open below panel, installed Yakuake and opened it using the default control key of F12. I then closed it and reopened. It always opened below the panel. Here is a screenshot:
Did you delete any kwin or other circumvention you put in place first? That would probably interfere with the default behavior.
I deleted the Kwin rule and rebooted and set the panel appropriately, but Yakuake still opens behind it.
Even when I set windows to always open below the panel, Yakuake still loads behind the panel.
Yeah, tried that one without any luck…
Interesting. I just did some more testing, playing around with the different settings and found that Yakuake knows about the plasma panel and won’t go behind it, so you don’t have to do any special settings. Please post a screenshot so I can see what is going on. Thanks!
Just a thought, but could it be related to the panel being set to “float?”
Never mind… I just checked and changing that doesn’t alter any behavior.
Yeah, I’m running out of ideas. Are you using the rpm or the flatpak. I’m using the rpm. I’ve just installed it on my laptop and it works fine there also. I did find this:
https://bugs.kde.org/show_bug.cgi?id=408468
No one has yet reported it with Plasma 6 however.
You shouldn’t have to do any kind of window rule or panel change for Yakuake AFAIK.
You might follow that bug and add your information to it. Unfortunately, it appears to only affect a particular hardware configuration rather than all installs.
I tend to use rpms (call me old school), but the description in the bug report seems to be exactly what I’m experiencing; and here I thought I was just doing something wrong.
Thanks for the ideas and I’ll work through the bug to see…
If you have time, would probably be a good idea to create a bug report also in Redhat/Fedora bugzilla and reference upstream. That would help give it more visibility.
For anyone who comes across this thread, I wanted to let you know my particular issue is no longer relevant; after toying around with both KDE Neon and openSUSE Tumbleweed in live environments and not running into the issue, I went back into my system and dug a bit deeper.
The age-old adage that it’s likely user error was never more true.
Although I was certain I installed Yakuake from the rpm, I had not and it was actually a flatpak install. After uninstalling the flatpak and reinstalling from the Fedora repos as an rpm, everything works as expected.
May this thread serve as a cautionary tale. 
