Description of problem: 'ssh -Y' to remote host A 'ssh' from remote host A to remote host B initiate 'cacaxine' on video file on remote host B all terminal sessions on local host abort and disappear! problem is repeatable. Version-Release number of selected component: gnome-terminal-3.8.4-1.fc19 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/libexec/gnome-terminal-server crash_function: _vte_ring_thaw_one_row executable: /usr/libexec/gnome-terminal-server kernel: 3.13.9-100.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 _vte_ring_thaw_one_row at ring.c:378 #5 _vte_ring_ensure_writable at ring.c:458 #7 _vte_ring_insert at ring.c:530 #8 _vte_terminal_ring_insert at vte.c:343 #9 _vte_terminal_scroll_text at vteseq.c:379 #10 vte_terminal_process_incoming at vte.c:4199 #11 time_process_incoming at vte.c:14976 #12 update_repeat_timeout at vte.c:15152 #17 g_main_context_iteration at gmain.c:3762 #18 g_application_run at gapplication.c:1623 Potential duplicate: bug 821141
Created attachment 888670 [details] File: backtrace
Created attachment 888671 [details] File: cgroup
Created attachment 888672 [details] File: core_backtrace
Created attachment 888673 [details] File: dso_list
Created attachment 888674 [details] File: environ
Created attachment 888675 [details] File: limits
Created attachment 888676 [details] File: maps
Created attachment 888677 [details] File: open_fds
Created attachment 888678 [details] File: proc_pid_status
Created attachment 888679 [details] File: var_log_messages
I should mention that the cacaxine process starts and displays the video file but aborts the gnome-terminal-server after about 10 seconds. My guess is that the 'ascii' generation from cacaxine is generating an escape sequence that confuses and aborts the terminal server ...
Seems the same as upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=647466. Luckily I can reproduce. Probably I'll have a fix in a day or two (keep checking the upstream link).
Hi, Could you please tell me if we are seeing the same thing? (I'm not using redhat/fedora.) cacaxine starts playing the video, at some moments it looks okay, but at other times it's quite broken, the screen is full of control characters (small boxed "001B", codes like "38;5;8m" and such. In other terminals (e.g. xterm) cacaxine's output is similarly broken. The terminal window sometimes resizes itself (with xterm it can even move around on the screen) while cacaxine is running, and it often exits with segmentation fault in just a few seconds. Seems that we're facing a broken cacaxine which happens to produce escape sequences that also cause a gnome-terminal/vte crash. I'll fix gnome-terminal. Could you please take care of filing cacaxine bug report (if its output is indeed broken in xterm etc.)? You probably don't need to ssh to a remote host, probably "unset DISPLAY" and then a local cacaxine can also trigger this. (Unless, of course, your local cacaxine is not broken, only the remote one.) Please tell me if you're also experiencing this behavior.
I believe this is fixed now in mainstream VTE git. Check the upstream link for details.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.