SUMMARY Dual screen setup on kubuntu 19.10 - external display is set to the left of the laptop screen with the same resolution. "Open on screen" is set to "At mouse location". If left external monitor is set to be at "exact left", yakuake will not toggle when mouse is in left screen. Set the left screen to be just slightly off left and it works fine (I dragged the left screen in SETTINGS > DISPLAYS to be just off the "snap" value, .local/share/kscreen/blablabla showed new y: position of the left screen as 48. When y is 0, yakuake breaks) STEPS TO REPRODUCE 1. Set up dual monitors in Kde / ubuntu 19.10, set yakuake to "at mouse location" 2. Have external monitor at exact left of laptop screen (1920,0) 3. Try to toggle yakuake while mouse is in external screen 4. Have external monitor an "just off left" of laptop screen (1920,48) and it works again OBSERVED RESULT Yakuake does not toggle in left monitor EXPECTED RESULT Yakuake toggles in whatever monitor the mouse is in SOFTWARE/OS VERSIONS Linux/KDE Plasma: ubuntu 19.10 (available in About System) KDE Frameworks 5.62.0 Qt 5.12.4 (built against 5.12.4) The xcb windowing system ADDITIONAL INFORMATION Was not sure what to include - pls ask if more detail needed!
I think I can confirm this, however I have a slightly different screen setup: My main screen is top right of my second screen. On my second screen yakuake opens perfectly fine, but on the main screen nothing happens. I also have it set to "at mouse location". Even if I change it to show up on the main screen, it won't show up…
for me, it now works with 5.19. Does it work now for you @Hamish?
(In reply to daniel-other+kdebug from comment #2) > for me, it now works with 5.19. Does it work now for you @Hamish? now it doesn't work again... strange. Do you have a second panel on a screen other than the main screen? Because I had removed that panel earlier and then it worked.
I think this is the same issue as in https://bugs.kde.org/show_bug.cgi?id=39669 should be fixed in the next release
whoops linked the wrong report https://bugs.kde.org/show_bug.cgi?id=396697
Fixed *** This bug has been marked as a duplicate of bug 396697 ***