Dear Maintainer, After upgrade from old-stable to stable, Tilda no longer reliably responds to the show/hide shortcut (in my case F12). If Firefox is running and currently has the focus, then pressing F12 pulls down Tilda as expected. Note that Firefox would also like to intercept the F12 key but Tilda receives it and acts correctly. If Firefox is running but minimized (no active application), then pressing F12 does nothing. Presumably Tilda does not receive the keypress. If Firefox is running and visible but gedit has the focus, then pressing F12 does nothing. If Tilda is pulled-down but gedit has the focus, then pressing F12 does not close Tilda as expected. Changing the configuration to use F2 has no effect on this behaviour, it's not specific to F12. Other applications behave the same as gedit so that Tilda won't open (for example Calculator, Files, Meld); some applications behave the same as Firefox so that Tilda correctly opens (for example Gimp, VLC). Deleting the configuration file(s) under ~/.config/tilda/ and re-setting the key has no effect. All of this worked fine before the upgrade. Desktop is standard Gnome, using a single monitor which is identified by Tilda as "0 (XWAYLAND0)".
This is a known issue that will be resolved once the D-Bus enabled update of tilda will reach the distribution. I am planning a new upload in the next weeks that will ship a new tilda version. In the mean time, there are two workarounds: * one is to build tilda from source if you are on Wayland as the current master branch of tilda already has the D-Bus support. * another one is to use an Xorg session instead of Wayland.
This is a known issue that will be resolved once the D-Bus enabled update of tilda will reach the distribution. I am planning a new upload in the next weeks that will ship a new tilda version. In the mean time, there are two workarounds: * one is to build tilda from source if you are on Wayland as the current master branch of tilda already has the D-Bus support. * another one is to use an Xorg session instead of Wayland.
Hi, and thanks for the quick reponse. Sorry, I didn't know that this was a "known issue", despite some searching for related terms. Thanks for the fix, and the workarounds. I can confirm that using an Xorg session gives reliable show/hide responses from Tilda as before. Thank you, and feel free to close this issue or keep it open until you have uploaded, as you wish :)