Describe the bug
Hooks -> onStart makes Guake opening laggy
Content of my script:
#!/bin/sh
guake --execute-command 'htop'
guake --new-tab ' '
If I try to run the start command by myself through terminal after closing Guake:
$ sh -c ~/Dropbox/install/dotfiles/guake-start.sh
Guake not running, starting it
Loading Gnome schema from: /usr/lib/python3/dist-packages/guake/data
Language previously loaded from: /usr/lib/python3/dist-packages/locale
Guake Terminal 3.8.1
VTE 0.64.2
Gtk 3.24.30
created fresh notebook for workspace 0
Spawning new terminal at /home/cedric
(guake:279208): VTE-WARNING **: 22:23:08.956: (../src/vtepty.cc:690):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
Guake initialized
Calling startup script: ~/Dropbox/install/dotfiles/guake-start.sh
Startup script started with pid: <Popen: returncode: None args: ['~/Dropbox/install/dotfiles/guake-start.sh']>
ERROR:dbus.proxies:Introspect error on :1.637:/org/guake3/RemoteControl: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
File "/usr/bin/guake", line 10, in <module>
sys.exit(exec_main())
File "/usr/lib/python3/dist-packages/guake/main.py", line 616, in exec_main
if not main():
File "/usr/lib/python3/dist-packages/guake/main.py", line 535, in main
remote_object.execute_command(options.command)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
return self._connection.call_blocking(self._named_service,
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking
reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
ERROR:dbus.proxies:Introspect error on :1.637:/org/guake3/RemoteControl: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
File "/usr/bin/guake", line 10, in <module>
sys.exit(exec_main())
File "/usr/lib/python3/dist-packages/guake/main.py", line 616, in exec_main
if not main():
File "/usr/lib/python3/dist-packages/guake/main.py", line 490, in main
remote_object.add_tab(options.new_tab)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
return self._connection.call_blocking(self._named_service,
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking
reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Spawning new terminal at
(guake:279208): VTE-WARNING **: 22:24:49.652: (../src/vtepty.cc:690):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/cedric
(guake:279208): VTE-WARNING **: 22:24:50.228: (../src/vtepty.cc:690):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)

After ~100s, Guake opens with htop & a second time as asked.
Expected behavior
Hooks -> onStart works instantly.
Actual behavior
Look like there is some issue and some timeout happens.
To Reproduce
Add a on start hook, re-start Guake.
$ guake --support
Guake Version: 3.8.1
Vte Version: 0.64.2
Vte Runtime Version: 0.64.2
GTK+ Version: 3.24.30
GDK Backend: <GdkX11.X11Display
Desktop Session: ubuntu-xorg
Display: :0
RGBA visual: True
Composited: True
- Monitor: 0 - SDC eDP-1
- Geometry: 1920 x 1080 at 0, 1080
- Size: 344 x 194 mm²
- Primary: True
- Refresh rate: 59.962 Hz
- Subpixel layout: unknown
- Monitor: 1 - IVM HDMI-1
- Geometry: 1920 x 1080 at 0, 0
- Size: 544 x 303 mm²
- Primary: False
- Refresh rate: 60.0 Hz
- Subpixel layout: unknown
Describe the bug
Hooks -> onStart makes Guake opening laggy
Content of my script:
If I try to run the start command by myself through terminal after closing Guake:
After ~100s, Guake opens with htop & a second time as asked.
Expected behavior
Hooks -> onStart works instantly.
Actual behavior
Look like there is some issue and some timeout happens.
To Reproduce
Add a on start hook, re-start Guake.
$ guake --support
Guake Version: 3.8.1
Vte Version: 0.64.2
Vte Runtime Version: 0.64.2
GTK+ Version: 3.24.30
GDK Backend: <GdkX11.X11Display
Desktop Session: ubuntu-xorg
Display: :0
RGBA visual: True
Composited: True