Sometimes it happens, that non of the displayed terminals in yakuake have a weired fokus. weired means here: - yakuake is shown in the front - i am able to type something in the terminal - the cursor symbol is not highlighted (filled), but only the non-filled square - when using two terminals it is possible to move the terminal i write to by clicking it with the mouse, but -> it is not possible using a shortcut to switch to the next terminal -> it does not show the visual effect "Highlight terminals when moving focus between them Steps to Reproduce: This bug only happens when having the mouse in an are that will be overlapped when calling yakuake (by F12). I.e. if i moving my cursor to the lower end of my screen before pressing f12 the bug does not occur, but if i move the cursor in the above 60% of my screen (i have configure yakuake to 60% height) the bug is triggered. Maybe this bug is related to Bug 336228, it has a similar mouse position dependent trigger. Reproducible: Always Software: - KF 5.17 - Plasma 5.5.3 - Qt 5.5.1
Should be fixed by http://commits.kde.org/yakuake/ee7152471dc8a733d5acbd0e026d7898a24be1f2
Thanks ! Seems fixed here :)
Thank you for testing and confirming!
reopening. This is definitely not fixed in 3.0.2 and current git. See the attached screencast.
Created attachment 97765 [details] bug video
I unfortunately can't reproduce it anymore, which makes it hard to do anything about it.
maybe there is some other component involved, too? I am using: - KF 5.19 - Plasma 5.5.5 - Qt 5.5.1 => do you have any newer/beta versions here? In this case i can try to bring my system to the same versions and test if the bug is fixed by this.... If you like, you can also send me some patches, for verbose logging or something like that. I will do the testing on my side then.
I run everything from git including the Qt 5.6 branch. It might help if you debugged SessionStack::showEvent and see if it's trying to focus the correct terminal id and actually getting through to that widget ...
I can reproduce this with version 3.0.2, other issue I have is, if my terminal is split in two, every time I press F12 to show the terminals the focus (when it works) changes from one terminal to the other.
(In reply to Hugo Parente Lima from comment #9) > other issue I have is, if my > terminal is split in two, every time I press F12 to show the terminals the > focus (when it works) changes from one terminal to the other. see Bug 356853
I'm affected by this bug as well and can't reproduce it reliably either. I noticed however that if the bug is triggered (cursor not filled), I can still type normally, but shortcuts such as Ctrl-Shift-C and Ctrl-Shift-V get recognized as Ctrl-C and Ctrl-V instead. Clicking into the yakuake window does not work, I have to hide and show yakuake again.
Another interesting thing is that when the bug is triggered, i.e. the cursor is not filled, and you retract yakuake, you can see the terminal getting the focus, i.e. having the cursor filled way before the terminal get retracted.
Another info, on my machine the bug is only triggered if my settings has 0ms animation time, with 100ms animation time it works.
(In reply to Hugo Parente Lima from comment #13) > Another info, on my machine the bug is only triggered if my settings has 0ms > animation time, with 100ms animation time it works. i can confirm that this workaround fixes the problem. This really seems to be a race conditions, since the probability that the bug appears rises with smaller animation times. Furthermore, i have noticed that the bug only appears if the mouse cursor is in the area of the yakuake terminal. Otherwise, (e.g. if i move the cursor to the bottom of the screen) the bug does not appear.
upgrading to qt 5.6.0 solves the problem for me
(In reply to Till Schäfer from comment #15) > upgrading to qt 5.6.0 solves the problem for me i was a little bit too fast with my reply. I am still able to reproduce the bug, but is has become much less likely with qt-5.6.0 to appear.
Bug #360234 is related, and I can confirm issue on 3.0.2. (In reply to Hugo Parente Lima from comment #13) > Another info, on my machine the bug is only triggered if my settings has 0ms > animation time, with 100ms animation time it works. Works even with 1ms, but not with 0
Confirming this bug in Yakuake 3.0.4+ Probably related to https://bugs.kde.org/show_bug.cgi?id=375085 Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.9.40-1-MANJARO x86_64 Distribution: "Netrunner Rolling"
Works for me with version 20.08.3 Operating System: Gentoo Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 Kernel Version: 5.9.9-gentoo OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 23.4 GiB of RAM Graphics Processor: GeForce GTX 970/PCIe/SSE2