|Summary:||Yakuake does not open on the screen where the mouse pointer is|
|Product:||[Applications] yakuake||Reporter:||phrxmd <philipp.reichmuth>|
|Component:||general||Assignee:||Eike Hein <hein>|
|Severity:||normal||CC:||brix, firlaevhans.fiete, hello, ilker4fun, mistry01, morashonjenkins, nate, nick.sev, nicolas.fella, paul, RBredereck, rossporter506, rulatir|
|Latest Commit:||https://invent.kde.org/utilities/yakuake/commit/ae055c29d7f4fb2ca5e8406410611ffb499f5028||Version Fixed In:||22.08|
Description phrxmd 2021-11-08 13:20:52 UTC
SUMMARY On Wayland, Yakuake always opens on a particular screen. I would prefer it to open on the screen with the mouse pointer, just like KRunner does in X11. STEPS TO REPRODUCE 1. With multiple monitors, invoke Yakuake. 2. Move the mouse pointer to another monitor and invoke Yakuake again. OBSERVED RESULT Yakuake always opens on a particular screen - in my case my notebook's screen, which happens to be the leftmost screen. EXPECTED RESULT Yakuake should open on the screen where the mouse pointer is, like KRunner does on X11. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211105 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION Some people might prefer it to open always on a particular screen, so "follow the mouse" could be a configuration option.
Comment 1 Firlaev-Hans 2021-11-13 17:34:42 UTC
Can confirm on KDE Neon unstable. Oddly enough when I tried it yesterday on my main (Arch Linux) PC on Wayland I could NOT confirm this, Yakuake actually DID open on the screen with the mouse. However, it was not resized correctly for the secondary monitor which has a lower resolution, thus it was cut off to the right. I have not found any configuration difference between the two machines that would explain the different behavior (both were also running the master build of Yakuake)
Comment 2 m1st0 2021-12-15 17:56:00 UTC
EXPECTED RESULT Yakuake should open on the screen where the mouse pointer is on Wayland, like KRunner or Yakuake does on X11.
Comment 3 m1st0 2021-12-15 18:06:48 UTC
(In reply to m1st0 from comment #2) > EXPECTED RESULT > Yakuake should open on the screen where the mouse pointer is on Wayland, > like KRunner or Yakuake does on X11. Sorry, should have confirmed rather than noted unnecessary semantics. Confirmed on Kubuntu 21.10, KDE Plasma 5.23.0.
Comment 4 ilker 2022-02-15 08:21:25 UTC
Can confirm that it doesn't working on Kde Neon with 5.24.0
Comment 5 morashon 2022-02-21 13:27:37 UTC
Confirm on Manjaro KDE Plasma 5.23.5
Comment 6 Nick 2022-03-16 08:38:59 UTC
Confirm on EndeavourOS with KDE Plasma 5.24.3
Comment 7 Nate Graham 2022-04-11 20:25:40 UTC
Git commit ae055c29d7f4fb2ca5e8406410611ffb499f5028 by Nate Graham, on behalf of Martin Seher. Committed on 11/04/2022 at 20:25. Pushed by ngraham into branch 'master'. On Wayland, show on active output QCursor::pos does not work under wayland. So use active output from KWin to determine startup screen, if not configured otherwise. M +14 -0 app/mainwindow.cpp https://invent.kde.org/utilities/yakuake/commit/ae055c29d7f4fb2ca5e8406410611ffb499f5028
Comment 8 Nate Graham 2022-05-25 16:25:04 UTC
*** Bug 454369 has been marked as a duplicate of this bug. ***
Comment 9 ttv200 2022-08-23 07:25:59 UTC
*** Bug 440825 has been marked as a duplicate of this bug. ***
Comment 10 Thomas Brix Larsen 2022-08-26 20:42:00 UTC
This no longer works on Xorg after upgrading to Yakuake 22.08.0 (on Arch Linux). Downgrading Yakuake to 22.04.3 restores the functionality. KRunner is also affected.
Comment 11 Szczepan Hołyszewski 2022-09-04 12:42:48 UTC
Experiencing this with Yakuake 2022.04.3 as well.
Comment 12 Nate Graham 2022-09-04 13:19:14 UTC
(In reply to Szczepan Hołyszewski from comment #11) > Experiencing this with Yakuake 2022.04.3 as well. As the "Version fixed in" field says, this is expected to be fixed in version 22.08.
Comment 13 Szczepan Hołyszewski 2022-09-04 13:34:38 UTC
Sorry, I got confused because Thomas Brix Larsen above said that _downgrading_ to 2022.04.3 fixed this for him. But it seems that he was in fact reporting a regression on X caused by this fix?