Bug 470408 – cannot spawn zsh with python bindings

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 470408 - cannot spawn zsh with python bindings


Summary:	cannot spawn zsh with python bindings


Status:	RESOLVED OBSOLETE

Product:	vte
Classification:	Core
Component:	general
Version:	0.16.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	VTE Maintainers
QA Contact:	VTE Maintainers

URL:
Whiteboard:	[obsolete-next]

Depends on:
Blocks:

Reported:	2007-08-26 11:38 UTC by Chris Jones
Modified:	2014-04-06 17:42 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description Chris Jones 2007-08-26 11:38:19 UTC

I've been playing around with the python bindings for vte and have encountered a very odd situation.
If I edit the vte-demo.py file included with vte and change the fork_command() to fork_command("/usr/bin/zsh") I get an empty terminal. stracing shows that zsh segfaulted, but doesn't give a great clue as to why.

Comment 1 Christian Persch 2008-10-15 15:06:19 UTC

Works here. Can you still reproduce this with vte trunk ?

Comment 2 Chris Jones 2008-10-16 15:52:15 UTC

I just built trunk, copied gnome-pty-helper to libexec, edited vte-demo.py and ran it, LD_PRELOAD'ing the libvte I'd built (I prefer not to make install things on my main systems) and it was still broken, but it's possible that this way of testing was not suffcient.

Comment 3 Patryk Zawadzki 2009-09-26 12:20:43 UTC

vte 0.22.1 started to kill zsh here. Wasn't hard to notice I used to use zsh as my shell until yesterday both gnome-terminal and vte started to close themselves as soon as I launch them.

Comment 4 Christian Persch 2009-09-26 13:09:36 UTC

I don't think that's the same issue as comment 0; since here vte itself segfaults, not zsh.

$ gdb --args .libs/lt-vte -c /usr/bin/zsh 
(gdb) r
Program received signal SIGSEGV, Segmentation fault.

+ Trace 217863

Thread 3071912208 (LWP 19007)

#0 _vte_terminal_ring_append
at vte.c line 307
#1 vte_sequence_handler_cd
at vteseq.c line 1063
#2 vte_sequence_handler_erase_in_display
at vteseq.c line 2658
#3 _vte_terminal_handle_sequence
at vteseq.c line 3293
#4 vte_terminal_process_incoming
at vte.c line 3973
#5 time_process_incoming
at vte.c line 14182
#6 update_repeat_timeout
at vte.c line 14356
#7 g_timeout_dispatch
at gmain.c line 3396
#8 g_main_dispatch
at gmain.c line 1960
#9 g_main_context_dispatch
at gmain.c line 2513
#10 g_main_context_iterate
at gmain.c line 2591
#11 g_main_loop_run
at gmain.c line 2799
#12 gtk_main
at gtkmain.c line 1204
#13 main
at vteapp.c line 938

Comment 5 Fryderyk Dziarmagowski 2009-09-26 19:39:22 UTC

I can observe same problems on my setup: 0.22.0 works, 0.22.1 kills vte based apps (zsh as main sh)
gdb trace same as above.

Comment 6 Fryderyk Dziarmagowski 2009-09-27 07:10:49 UTC

...but it not the same issue as originally reported (see #596460)

Comment 7 Behdad Esfahbod 2009-09-27 21:33:55 UTC

The crash is fixed.  I have no idea what's the thing with zsh.

Comment 8 Christian Persch 2009-12-04 18:54:51 UTC

I still can't repro the original problem in comment 0:

$ ./vte -c zsh
$ ./vte-demo.py -c zsh

both work on vte git master.

Comment 9 Fabio Durán Verdugo 2009-12-05 13:32:01 UTC

*** Bug 603843 has been marked as a duplicate of this bug. ***