Guake / guake

Drop-down terminal for GNOME
https://guake.github.io
GNU General Public License v2.0
4.46k stars 579 forks source link

Kde unresponsive when clicking taskbar icon to change settings #1967

Open neppramod opened 3 years ago

neppramod commented 3 years ago

Kde becomes unresponsive for most task when I try to change setting using taskbar icon

First of all the setting window never appeared. After I clicked it multiple times, it seems to flicker. On previous boot, I restarted. I am able to open another terminal with Ctrl + Alt + T, but all icons on task bar becomes unresponsive.

Setting window should appear and let me change the values I was able to change on my first instance after install.

Actual behavior

It seems to flicker mouse for a while making whole desktop unresponsive. I am guessing since I clicked the icon bunch of times, it queued the events and fired after things started to come back up.

To Reproduce

I used touchpad to click the icon on taskbar.

I ran guake using a terminal while the icon was still showing in taskbar, this is what I saw in terminal

guake
Guake not running, starting it
Loading Gnome schema from: /usr/share/glib-2.0/schemas
Language previously loaded from: /usr/share/locale
Guake Terminal 3.8.1
VTE 0.66.0
Gtk 3.24.30
created fresh notebook for workspace 0
Spawning new terminal at /home/<username>

(guake:6401): VTE-WARNING **: 22:26:22.616: (../vte/src/vtepty.cc:667):bool _vte_pty_spawn_sync(VtePty*, const char*, const char* const*, const char* const*, GSpawnFlags, GSpawnChildSetupFunc, gpointer, GDestroyNotify, GPid*, int, GCancellable*, GError**): runtime check failed: ((spawn_flags & ignored_spawn_flags()) == 0)
current workspace is 0
can't bind show-focus key
Spawning new terminal at /home/<username>/Documents/

(guake:6401): VTE-WARNING **: 22:26:22.856: (../vte/src/vtepty.cc:667):bool _vte_pty_spawn_sync(VtePty*, const char*, const char* const*, const char* const*, GSpawnFlags, GSpawnChildSetupFunc, gpointer, GDestroyNotify, GPid*, int, GCancellable*, GError**): runtime check failed: ((spawn_flags & ignored_spawn_flags()) == 0)
Spawning new terminal at /home/<username>/Documents/

(guake:6401): VTE-WARNING **: 22:26:22.907: (../vte/src/vtepty.cc:667):bool _vte_pty_spawn_sync(VtePty*, const char*, const char* const*, const char* const*, GSpawnFlags, GSpawnChildSetupFunc, gpointer, GDestroyNotify, GPid*, int, GCancellable*, GError**): runtime check failed: ((spawn_flags & ignored_spawn_flags()) == 0)
Guake tabs restored from /home/<username>/.config/guake/session.json
Guake initialized

$ guake --support

$ guake --support Guake Version: 3.8.1 Vte Version: 0.66.0 Vte Runtime Version: 0.66.0 -------------------------------------------------- GTK+ Version: 3.24.30 GDK Backend:
ghost commented 3 years ago

I am experiencing this on Debian Sid. Guake 3.8.1 was pushed last week and there has been numerous issues so far. After boot it usually takes Guake about 5-10 minutes to start and work properly. Its icon is black until time passes and it just starts.

Plasma Version 5.23.0 KdeFramworks Version : 5.86.0 Qt Version : 5.15.2

I have notice a process xembedsniproxy is consuming a large amount of cpu and dumping "Container window visible, stack below" to .xsession-errors. Force closing xembedsniproxy makes me lose a few icons in the systray including guake but system stability is restored. Guake still runs fine in the background it just doesnt have a systray icon. Check htop if you're having the same problem.

Davidy22 commented 3 years ago

Looks like xembedsniproxy is a tool for converting system try icons from X applications into wayland compatible icons. This issue would have started 3.8 onwards because we fixed the code that would force guake to use x11, with all the consequences of forcing guake to use X that may bring on wayland. The slowdown probably needs to get fixed on the xembedsniproxy side since this happens with that, and an environment flag is coming that will allow the user to run Guake in wayland mode (#1975)