I have a multi-monitor setup on wayland. The option to make the terminal appear on the mouse screen only works when the mouse enter certain windows (in my case Microsoft Teams chat and Guake Preferences, but I believe that any XWayland window would work).
Example: I put the Teams window so that it spans all monitors. If the mouse is inside the window on monitor X then guake appears on monitor X. If the mouse leaves the window on monitor X and then I move it to monitor Y then guake will pop up on monitor X instead on Y.
Expected behavior
Guake should pop up where the cursor is
Actual behavior
Guake pops up where the cursor has been seen last by X server
Same issue, Guake seems to "lock" to the monitor where Google Chrome was last active. Focusing another application doesn't seem to have any impact. Currently running Guake 3.10, on Wayland 23.1.2, everything pulled from OpenSUSE Tumbleweed.
The main problem is not the guake bug itself but the fact that guake does poorly work on Wayland. Lot's of hacks to get it working and the support is not there. Since Wayland is becoming a default option, guake will need see what its future will be like. People will not be switching to X11 as a solution.
Just to confirm Guake really follows last X window either mvoed or mouse hover in area. Joplin, Slack, Teams, Chrome all exhibit this behavior.
Describe the bug
I have a multi-monitor setup on wayland. The option to make the terminal appear on the mouse screen only works when the mouse enter certain windows (in my case Microsoft Teams chat and Guake Preferences, but I believe that any XWayland window would work). Example: I put the Teams window so that it spans all monitors. If the mouse is inside the window on monitor X then guake appears on monitor X. If the mouse leaves the window on monitor X and then I move it to monitor Y then guake will pop up on monitor X instead on Y.
Expected behavior
Guake should pop up where the cursor is
Actual behavior
Guake pops up where the cursor has been seen last by X server
$ guake --support
Guake Version: 3.8.5 Vte Version: 0.68.0 Vte Runtime Version: 0.68.0 -------------------------------------------------- GTK+ Version: 3.24.33 GDK Backend:I can confirm this behaviour on ubuntu 22.04.1, guake built from git
$ guake --support
Guake Version: 3.9.1.dev12 Vte Version: 0.68.0 Vte Runtime Version: 0.68.0 -------------------------------------------------- GTK+ Version: 3.24.33 GDK Backend:I've got the same issue.
I.e it captures the correct screen when I hover over Chrome. But it doesn't when it's gedit.
I'm on Ubuntu 22.4.1 LTS. mart@VivoBook:~$ guake --version Guake Terminal: 3.8.5 VTE: 0.68.0 VTE runtime: 0.68.0 Gtk: 3.24.33
PS: Haven't tried compiling latest dev versions. But comments #2115 seems to suggest that it may not be fixed yet.
i've switched to xorg as a workaround, where i still have some issues with fullscreen (disappearing tabs) but not with mouse follow
I also have this problem
ubuntu 22.4.1 Wayland
Guake Terminal: 3.9.1.dev12 VTE: 0.68.0 VTE runtime: 0.68.0 Gtk: 3.24.33
I have the same issue with ubuntu 22.4.1 Wayland and Guake 3.9.0. Anyone knows if there's an update on this issue?
Same issue, Guake seems to "lock" to the monitor where Google Chrome was last active. Focusing another application doesn't seem to have any impact. Currently running Guake 3.10, on Wayland 23.1.2, everything pulled from OpenSUSE Tumbleweed.
For what it's worth, you can use
Win+click+drag can move it to the other screen. It also seems to fix it, at least temporarily.The issue still persists on Ubuntu 22.04
This bug still exists on new install of: Ubuntu 24.04.1 LTS on Wayland (wayland is the default on ubuntu for some years) Gnome version 46.0
I first tried the apt package and then tried install from source/git (3.11.dev16)
The bug is that guake often does not show up on the display where the mouse is.
(I also had to add the F12 shortcut manually in gnome, it would be nice if that happened automatically somehow.)
$ guake --support
Guake Version: 3.11.dev16 Vte Version: 0.76.0 Vte Runtime Version: 0.76.0 -------------------------------------------------- GTK+ Version: 3.24.41 GDK Backend:Can confirm that Ubuntu 24.10 is doing this.
The main problem is not the guake bug itself but the fact that guake does poorly work on Wayland. Lot's of hacks to get it working and the support is not there. Since Wayland is becoming a default option, guake will need see what its future will be like. People will not be switching to X11 as a solution.
Just to confirm Guake really follows last X window either mvoed or mouse hover in area. Joplin, Slack, Teams, Chrome all exhibit this behavior.