Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Appears to be incompatible with GNOME 47 #2255

Open
iconoclasthero opened this issue Aug 18, 2024 · 5 comments
Open

Appears to be incompatible with GNOME 47 #2255

iconoclasthero opened this issue Aug 18, 2024 · 5 comments

Comments

@iconoclasthero
Copy link

Describe the bug
Appears to be incompatible with GNOME 47. Pressing toggle visibility does various things. Sometimes it causes the window to blink on, sometimes, if you hit it enough, it causes it to STAY ON!!! When it's on, sometimes it causes guake to blink off, sometimes it causes guake to stay off.

Also it appears on the wrong window from time to time, refuses to show up on one of my monitors at all.... not really showing up when and where it's supposed to and if it does, it doesn't stay there when told to do so. It's like a poorly trained dog.

Expected behavior
Normal toggle visibility function.

Actual behavior
Pressing toggle visibility does various things. Sometimes it causes the window to blink on, sometimes, if you hit it enough, it causes it to STAY ON!!! When it's on, sometimes it causes guake to blink off, sometimes it causes guake to stay off.

Also it appears on the wrong window from time to time, refuses to show up on one of my monitors at all.... not really showing up when and where it's supposed to and if it does, it doesn't stay there when told to do so. It's like a poorly trained dog.

To Reproduce
toggle visibility in GNOME 47

NB
It appears that using $ guake-toggle from the cli works properly.


$ guake --support

Guake Version: 3.10

Vte Version: 0.77.91

Vte Runtime Version: 0.77.91


GTK+ Version: 3.24.43

GDK Backend: None


Desktop Session: ubuntu


Traceback (most recent call last):
File "/usr/bin/guake", line 33, in
sys.exit(load_entry_point('guake==3.10', 'console_scripts', 'guake')())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/guake/main.py", line 664, in exec_main
if not main():
^^^^^^
File "/usr/lib/python3/dist-packages/guake/main.py", line 462, in main
print_support()
File "/usr/lib/python3/dist-packages/guake/support.py", line 94, in print_support
get_display()
File "/usr/lib/python3/dist-packages/guake/support.py", line 86, in get_display
populate_display(display)
File "/usr/lib/python3/dist-packages/guake/support.py", line 22, in populate_display
screen = display.get_default_screen()
^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'get_default_screen'



OS: Rhino Linux 2024.2~RC (server) x86_64
Kernel: Linux 6.10.4-061004-generic
Shell: bash 5.2.21
Resolution: 1920x1080, 2560x1440, 1920x1080, 2560x1440
DE: GNOME 47.beta (Wayland)
DE: GNOME Shell 47.beta
WM: Mutter
Terminal: guake

@iconoclasthero
Copy link
Author

I managed to get back to gnome 46 on X and the problems went away, literally everything else being equal...

OS: Rhino Linux 2024.2~RC (server) x86_64 
Kernel: Linux 6.10.4-061004-generic 
Shell: bash 5.2.21 
Resolution: 2560x1440 @ 59.95Hz, 1920x1080 @ 60.00Hz, 1920x1080 @ 60.00Hz, 2560x1440 @ 59.95Hz 
DE: GNOME 46.0 
DE: GNOME Shell 46.0 
WM: Mutter 
Terminal: guake 

$ echo $XDG_SESSION_TYPE 
x11

@johnheenan
Copy link

Here is a workaround:

Remove F12 as key to 'Toggle Guake visibilty' in Guake Properties.
Add F12 as 'Custom Shortcut' to command 'guake-toggle' in Gnome, Settings, Keyboard, View and Customize Shortcuts.

@iconoclasthero
Copy link
Author

iconoclasthero commented Aug 25, 2024 via email

@effectfully
Copy link

Here is a workaround:

Remove F12 as key to 'Toggle Guake visibilty' in Guake Properties.
Add F12 as 'Custom Shortcut' to command 'guake-toggle' in Gnome, Settings, Keyboard, View and Customize Shortcuts.

Worked for me, thanks!

@Davidy22
Copy link
Collaborator

I'll get 47 when it comes to fedora 41, but for the time being does @johnheenan's workaround work for you?

Labelled as a workaround but given that it's necessary on wayland because of policy I do have a mind to just make it the default with instructions on how to do it in the settings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants