#857228 Fwd: guake: toggle shorcut (F12 by default) not working in Wayland

Package:
guake
Source:
guake
Submitter:
Goran LAZAREVIC
Date:
2025-07-16 16:01:01 UTC
Severity:
normal
Tags:
#857228#5
Date:
2017-03-08 22:48:38 UTC
From:
To:
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: GOGI <goksibg@gmail.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: guake: toggle shorcut (F12 by default) not working in Wayland
Message-ID: <148893243438.4634.15959325062239021025.reportbug@localhost>
X-Mailer: reportbug 7.1.5
Date: Wed, 08 Mar 2017 01:20:34 +0100

Package: guake
Version: 0.8.8-1
Severity: normal
Tags: upstream

As said in the subject, when opening a session under Wayland, shorcut
F12 for
toggling visibility of Guake window doesn't have any effect... A
workaround is
to create a shorcut under System-Settings/Keyboard to make it work.
And I have no idea what's the matter as I have no other information to
forward
from journal...

#857228#10
Date:
2017-06-26 23:31:48 UTC
From:
To:
tags 857228 + moreinfo unreproducible
thanks

Hi!

Thanks for the report, unfortunately, I can't reproduce this bug in
wayland, I tried, installing  wayland and guake in VM, start sesion
under wayland  and shorcut works fine,

BTW, I will upload  to unstable the new version, Could you try this
new version and check if the bug persist?

Regards

#857228#17
Date:
2017-09-09 16:39:01 UTC
From:
To:
Hello,

I have the same issue with Guake package's version 0.8.10.1 in Debian
Buster when opening a Gnome Wayland session. The shortcut F12 doesn't
toggle Guake's window.

I noticed one interesting thing : when Firefox or Thunderbird are open,
the shortcut F12 works well and the guake's window appears.
As F12 is also a shortcut to open the Firefox's inspecting tool, I
tried to change F12 with another shortcut in the guake's settings. This
bring no change.

I make same observations in à Virtual Machine with Debian Stretch and
Guake package version 0.8.8.1.

Regards,
Isabelle Lepage

#857228#22
Date:
2017-11-12 15:35:42 UTC
From:
To:
This happens for me too. I'm running Gnome, under Wayland. When an X11
window is selected, F12 toggles guake visibility. When a Wayland
window is selected, F12 does nothing. You can see something similar if
you run xeyes and notice that they follow the mouse when it is in an
X11 window, but not when it is in a Wayland window. (An easy Wayland
window to pop up is the setting window from the top-right Gnome
dropdown menu.)

Excellent idea. I tried it too, and it works well. Thank you Goran for
eliminating this pain point from my life!

Details:

At the bottom of the keyboard shortcuts settings panel, click the '+'
button to add a new shortcut, name it whatever you want (Toggle
Guake), give it the command /usr/bin/guake, and set it to the F12 key.

I wonder if this could be done automatically by the guake installation scripts?

#857228#27
Date:
2017-11-12 19:18:02 UTC
From:
To:
mouse is on, guake doesn't notice that the mouse has switched to a
different screen should such motion have occurred entirely within a
Wayland window. Presumably for the same reason xeyes stops tracking
the mouse while the mouse is inside a Wayland window.

#857228#32
Date:
2019-03-08 20:40:25 UTC
From:
To:
Hi!

Just to inform you that this bug is still present when installing Buster (with Gnome and Guake) from the Debian Buster DI alpha 5 DVD set.

Regards

#857228#37
Date:
2023-07-22 09:34:26 UTC
From:
To:
Actually it works  when shortcut pressed on firefox but not on desktop,
clementine and many other apps.

#857228#42
Date:
2024-06-11 01:08:24 UTC
From:
To:
I just installed guake (3.9.0-2) on Bookworm and hit this issue too.
FWIW I haven't had it installed for ages and last time I used it worked
fine.

To make it more frustrating if I had firefox open, it opens the dev
tools instead!

I followed the workaround noted here (in gnome settings) and that worked
for me too.

For good measure I also disabled <f12> for web dev tools in firefox
about.config:

devtools.f12_enabled false

Cheers,
Jeremy

#857228#47
Date:
2025-07-16 15:40:29 UTC
From:
To:
A fresh install from Trixie and issue still existing. Above workaround
is working.