| Summary: | Active terminal doesn't always gain focus correctly after opening the window | ||
|---|---|---|---|
| Product: | [Applications] yakuake | Reporter: | Elias Probst <mail> |
| Component: | general | Assignee: | Eike Hein <hein> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | aleixpol, aspotashev, flying-sheep, good.win.alexs, huon, iamgrief, jazzvoid, kde, kde, luislezcair, m.keyran, martin.blumenstingl, mgraesslin, notuxius, rushhourresources, vlada.dudr, xargon86 |
| Priority: | NOR | ||
| Version: | Git (Frameworks 5) | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Elias Probst
2014-11-27 18:06:33 UTC
The "focus type" Yakuake receives also simply changes when moving the cursor into the Yakuake window. Every 2nd time it's the proper focus, while every other 2nd time it's the "broken" focus where shortcuts like Ctrl+Shift+V don't work. So this can simply be tested by moving the cursor above and away from the Yakuake window repeatedly in kwin's "Focus follows mouse" mode. Also notable: when the "wrong focus" is active, the cursor isn't shown as filled solid but only as an unfilled rectangle. *** Bug 343199 has been marked as a duplicate of this bug. *** Even without "Focus Follows Mouse", the terminal sometimes doesn't gain focus properly when the cursor is above the Yakuake window while it's opening. FWIW, I spent a while tracking this through a bunch of layers of Qt code and landed within a mystery of how the xcb plugin handles window activation - still don't have any definitive answers though ... (In reply to Eike Hein from comment #3) > Even without "Focus Follows Mouse", the terminal sometimes doesn't gain > focus properly when the cursor is above the Yakuake window while it's > opening. It's always the case for me, not just "sometimes": - when the mouse pointer is inside the region where Yakuake window would appear, the terminal doesn't gain focus (i.e. shortcuts don't work, cursor is drawn as an outline), - when the mouse pointer is outside the Yakuake window to be shown, the terminal always gains focus correctly. *** Bug 354646 has been marked as a duplicate of this bug. *** Unchecking "Ask the window manager to perform the animation" (in Configure -> Window) seems to have fixed this for me. FWIW I got the dodgy focus seemingly randomly, about 30% of the time. I did/do not have "Focus Follows Mouse" turned on. I can confirm this workaround. (In reply to Huon from comment #7) > Unchecking "Ask the window manager to perform the animation" (in Configure > -> Window) seems to have fixed this for me. Worked for me as well. Thanks a lot! This solution doesn't work for certain window managers, for intance, XMonad. Well, on XMonad it always does what this workaround does. That said I don't think this is a real solution. I don't have focus follows mouse on and this still happens every other time or so... I've found right clicking in the konsole window restores focus, though that is not really a workaround obviously. Same problem here; doesn't seem to depend on how the focus policy is configured; Huon's fix appears to be a good workaround. I can also confirm this bug. The workaround proposed also fixes the issue. Arch Linux Yakuake 3.0.2 KDE Frameworks 5.22.0 Qt 5.6.0 Gentoo Linux Kwin 4.11.22 Yakuake 3.0.2 Konsole 16.04.3 KDE Frameworks 5.24 I don't have "follow the mouse" focus policy, same symptoms as mentioned before, workaround helps If I have mouse outside Yakuake when it shows up, it gains focus, but if I have multiple split terminals, after I hide/show Yakuake window multiple times, focus jumps to next split terminal. Not confirming this bug in Yakuake 3.0.4+ Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.9.40-1-MANJARO x86_64 Distribution: "Netrunner Rolling" On the latest plasma 5.14 and yakuake 3.0.5 the workaround mention above ("Ask the window manager to perform the animation") doesn't work anymore, pane focus got messed independently of is this option is turned on or off
*** This bug has been confirmed by popular vote. *** |