search

lanoxx / tilda

A Gtk based drop down terminal for Linux and Unix
GNU General Public License v2.0
1.26k stars 162 forks source link

Tilda error _vte_pty_check_envv(envv)' failed #442

Closed Strykar closed 3 years ago

Strykar commented 3 years ago

I start Tilda via .config/autostart and the program appears to be running and I can right click and explore Tilda's options but the executed program does not display. Tilda starts with this error:

(tilda:4917): VTE-CRITICAL **: 18:32:41.811: void vte_pty_spawn_with_fds_async(VtePty*, const char*, const char* const*, const char* const*, const int*, int, const int*, int, GSpawnFlags, GSpawnChildSetupFunc, gpointer, GDestroyNotify, int, GCancellable*, GAsyncReadyCallback, gpointer): assertion 'envv == nullptr || _vte_pty_check_envv(envv)' failed
Tilda has started. Press F2 to pull down the window.

I'm unsure what this error means, the program called via Tilda's config runs fine in a gnome-terminal window.

rkrzr commented 3 years ago

I am also getting this issue running tilda-1.5.2 on NixOS. Tilda hangs showing only a blinking cursor in the top left corner. It used to work flawlessly with older versions, so this must be a new problem.

Edit: I can confirm that Tilda still works flawlessly on version 1.5.0. So this regression must have been introduced either in 1.5.1 or 1.5.2.

Strykar commented 3 years ago

So I tried downgrading but the issue persists with:

Dec 09 06:30:06 i5 systemd[909]: Started Application launched by gnome-shell.
Dec 09 06:30:06 i5 tilda[6582]: void vte_pty_spawn_with_fds_async(VtePty*, const char*, const char* const*, const char* const*, const int*, int, const int*, int, GSpawnFlags, GSpawnChildSetupFunc, gpointer, GDestroyNotify, int, GCancellable*, GAsyncReadyCallback, gpointer): assertion 'envv == nullptr || _vte_pty_check_envv(envv)' failed
Dec 09 06:30:06 i5 gnome-shell[6582]: Tilda has started. Press F2 to pull down the window.

Oddly, if tilda starts fine if no custom command is set and after dropping to a shell, actually runs the same custom command just fine. So this appears to be some sort of environment error preventing it from running the custom command?

Seems related to https://github.com/lanoxx/tilda/pull/438 @lanoxx Any chance of a new release with the fix for those of use not on Ubuntu?

Currently fixed by moving to master, the patch works.

lanoxx commented 3 years ago

I will backport commit 05463f9 to the 1.5 series and release 1.5.4.

lanoxx commented 3 years ago

1.5.4 is tagged. Please reopen if this still occurs.