Activity log for bug #1730742

Date Who What changed Old value New value Message
2017-11-07 19:38:03 Jon Oster bug added bug
2017-11-07 19:38:03 Jon Oster attachment added terminator-logs.zip https://bugs.launchpad.net/bugs/1730742/+attachment/5005538/+files/terminator-logs.zip
2017-11-07 19:42:31 Jon Oster description Fair warning: this is a weird and frustrating bug. I am more than willing to actively help track down what the heck is going wrong. Version: 1.91-0~1781~ubuntu16.04.1, installed from the PPA, and trunk revision 1781. When I open terminator, split the window twice (with Ctrl-Shift-E or Ctrl-Shift-O), then close those two panes (with Ctrl-Shift-W), it crashes trying to close the second pane. The window becomes non-responsive, and I have to kill the process manually. This happens 100% of the time...unless the working directory when I launch terminator is anything apart from / or my home directory. If the working directory is anything else, it doesn't crash, but instead prints the following to stderr at the point where it would normally crash: sys:1: Warning: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). Most likely the process is ignoring SIGCHLD, or some other thread is invoking waitpid() with a nonpositive first argument; either behavior can break applications that use g_child_watch_add()/g_spawn_sync() either directly or indirectly. This is true regardless of whether I run from trunk or from the terminator installed from the PPA. I'm attaching the debug logs of two different runs of terminator, one with the bug and one without. I'm not sure if it'll be much help, though; apart from object addresses and UUIDs, they only differ in the fact that the good one extends past the point where the bad one crashes. Now for the really annoying part: I tried this on a colleague's machine, who is also running Ubuntu 16.04, and I can't reproduce it there. In both cases, I removed ~/.config/terminator before running; that had no effect. Fair warning: this is a weird and frustrating bug. I am more than willing to actively help track down what the heck is going wrong. Version: 1.91-0~1781~ubuntu16.04.1, installed from the PPA, and trunk revision 1781. Kernel is 4.8.10-040810-generic, WM is Unity. When I open terminator, split the window twice (with Ctrl-Shift-E or Ctrl-Shift-O), then close those two panes (with Ctrl-Shift-W), it crashes trying to close the second pane. The window becomes non-responsive, and I have to kill the process manually. This happens 100% of the time...unless the working directory when I launch terminator is anything apart from / or my home directory. If the working directory is anything else, it doesn't crash, but instead prints the following to stderr at the point where it would normally crash: sys:1: Warning: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). Most likely the process is ignoring SIGCHLD, or some other thread is invoking waitpid() with a nonpositive first argument; either behavior can break applications that use g_child_watch_add()/g_spawn_sync() either directly or indirectly. This is true regardless of whether I run from trunk or from the terminator installed from the PPA. I'm attaching the debug logs of two different runs of terminator, one with the bug and one without. I'm not sure if it'll be much help, though; apart from object addresses and UUIDs, they only differ in the fact that the good one extends past the point where the bad one crashes. Now for the really annoying part: I tried this on a colleague's machine, who is also running Ubuntu 16.04, and I can't reproduce it there. In both cases, I removed ~/.config/terminator before running; that had no effect.
2017-11-08 10:51:44 Jon Oster summary Terminator crashes when closing panes, but only when launched from certain directories Terminator crashes when closing panes, but only when launched from default directories
2017-11-08 13:41:47 Egmont Koblinger bug added subscriber Egmont Koblinger