Guake: Can't bind since Ubuntu 18.04 update

Created on 4 Jun 2018  路  18Comments  路  Source: Guake/guake

Console show this :
* (guake:14095): WARNING *: 18:52:19.209: Binding 'asterisk' failed!
My caracteristics:
Guake Terminal 3.2.2
VTE 0.52.1
Gtk 3.22.30
GNOME 3.28.1

Most helpful comment

I just ran into this issue on Arch in 2019; GNOME 3.32, fully updated, Wayland. My solution was to add a manual keybinding for the "guake" command to F12 in GNOME Settings. Works like a dream!

All 18 comments

do you use wayland?

Yes but before on Ubuntu 17.10 I was already on and binding worked perfectly

dont know how it worked i never had the binding working under wayland (see this page on the doc)

Can you see if this recommendation works: https://github.com/kupferlauncher/keybinder/issues/11

The solution with guake -t works well, i'll try the recommandation

The recommandation didn't work, I suppose the update of ubuntu updated wayland and so now makes this error

i though ubuntu reversed back to x11 ?

I think Ubuntu 18.04 gives X11 when it is the first installation but not when you're updating it.

For me, the upgrade updated all softwares and after I've got this bug. I'll take a look on previous version of Gnome, Guake, etc. when they were working to see differences.

"Because Gtk2 applications are ran in XWayland. env GDK_BACKEND=x11 would make a Gtk3 application run under XWayland too"
so guake 0.8 (on gtk2) should work natively on wayland, while gtk3 app (guake 3) should have this env var set prior to launch, apparently.

Ok I got it I was on guake 0.8 and the Ubuntu upgrade updated it to guake 3. Finally, the recommmandation with the environment variable worked, it was because I was doing it wrong.
Thank you :smile:

cool :) can you manage to make this environment variable in /usr/local/share/applications/guake.desktop ?
Something by replacing:

Exec=guake

by

Exec= env GDK_BACKEND=x11 guake

will it fix for everyone ?

Tested and it works on Wayland and X11 :)

great, I'll prepare a patch on master and if you agree to test, it will please all wayland users !

No problem :)

I just ran into this issue on Arch in 2019; GNOME 3.32, fully updated, Wayland. My solution was to add a manual keybinding for the "guake" command to F12 in GNOME Settings. Works like a dream!

@deekosta Works for me too (Fedora 30). For others, see Gnome docs on custom shortcuts.

Tried all solutions, still failing to bind indicator to guake:
image

Enabled/Disabled Wayland
started with env GDK_BACKEND=x11 guake

No luck, Please Help

env GDK_BACKEND=x11 guake-toggle

Solution for me. Faster to toggle. Maybe needs be be opened with env GDK_BACKEND=x11 guake at first.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

igorog picture igorog  路  3Comments

ka4eli picture ka4eli  路  4Comments

ludovicaelbrecht picture ludovicaelbrecht  路  5Comments

k23363 picture k23363  路  3Comments

wada3n picture wada3n  路  3Comments