Bug#996082: vte2.91: vte.terminal.spawn_async emits useless warning by default

Simon McVittie smcv at debian.org
Sun Oct 10 23:10:49 BST 2021


Control: tags -1 + moreinfo

On Sun, 10 Oct 2021 at 22:51:10 +0200, Nis Martensen wrote:
> (reportbug:22755): VTE-WARNING **: 21:37:42.462:
> (../src/vtepty.cc: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): runtime check
> failed: ((spawn_flags & ignored_spawn_flags()) == 0)

What exact function are you calling and what flags are you passing to it?

This warning should not appear unless spawn_flags contains one of the
flags that either are not available here, or have their behaviour
enabled by default anyway and therefore are unnecessary (namely
G_SPAWN_CLOEXEC_PIPES and/or G_SPAWN_DO_NOT_REAP_CHILD).

    smcv



More information about the pkg-gnome-maintainers mailing list