After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 639900 - Some forked child commands exit immediately
Some forked child commands exit immediately
Status: RESOLVED NOTGNOME
Product: vte
Classification: Core
Component: general
0.24.x
Other Linux
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-01-18 21:58 UTC by Tony Houghton
Modified: 2011-01-20 14:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tony Houghton 2011-01-18 21:58:02 UTC
Are there any known issues with vte_terminal_fork_command apart from (or leading to) its being deprecated? When running certain commands in roxterm on Debian (which has vte 0.24.3) they exit immediately. These programs include nano and zsh. Ubuntu has a newer vte and there roxterm uses vte_terminal_fork_command_full and it doesn't seem to have this bug.


I tried running zsh from a wrapper script and with -v -x options and in both cases it ran correctly. I guess there's some sort of race condition (not depending on hardware performance because my 32-bit Atom netbook and 64-bit 2.6GHz Athlon 2 x4 with SSD are both affected). Could it be something to do with the std* pseudo file descriptors? I tried changing the point at which roxterm forks the child, ie usually it's after a g_idle_add and I tried running it immediately and when the vte widget got a realized signal, but neither helped.
Comment 1 Christian Persch 2011-01-18 22:31:07 UTC
How do the 'exit' --- crash? -> (nonreproducible) bug 470408 ?
Comment 2 Tony Houghton 2011-01-20 14:57:14 UTC
This turned out to be a bug in roxterm after all. Sorry for the distraction.