On 02/11/20 10:49 AM, Predrag Zecevic - Unix Systems Administrator wrote:
On 02/09/20 16:32, Michal Nowak via openindiana-discuss wrote:On 02/07/20 08:55 AM, Predrag Zecevic - Unix Systems Administrator wrote:Hi Michal,What I have found this morning is that that "error" happens only in terminator (terminal), while it works as expected in mate-terminal...:; ps -ef| grep mate[-]terminalglobal predrag* 16447 1805 0 08:45:46 ? 0:00 mate-terminalThen in that terminal (no exit): :; npm -version 6.13.4 I am running :; ps -ef| grep terminato[r]global predrag* 1863 1805 1 12:11:03 ? 18:08 /usr/bin/python2.7 /usr/bin/terminatorIn terminator tab (no screen, or tmux) I have started: :; truss -o /tmp/npm.truss.$(date '+%Y%m%dT%H%M%S') npm -version and that tab has exited, Last 15 lines of that truss file: :; tail -15 /tmp/npm.truss.20200207T085312 /1: close(23) = 0 /1: mprotect(0x40DC2000, 249856, PROT_READ|PROT_WRITE) = 0 /1: mprotect(0x40DC2000, 249856, PROT_READ|PROT_EXEC) = 0 /1: mprotect(0x40DC2000, 249856, PROT_READ|PROT_WRITE) = 0 /1: mprotect(0x40DC2000, 249856, PROT_READ|PROT_EXEC) = 0 /1: mprotect(0x40DC2000, 249856, PROT_READ|PROT_WRITE) = 0 /1: mprotect(0x40DC2000, 249856, PROT_READ|PROT_EXEC) = 0 /1: write(20, " 6 . 1 3 . 4\n", 7) = 7 /1: write(20, 0xFFDF99E0, 0) = 0 /1: Received signal #24, SIGTSTP [default] /2: Received signal #1, SIGHUP, in port_getn() [default] /2: siginfo: SIGHUP pid=16511 uid=2903 /1: Received signal #25, SIGCONT [default] /2: port_getn(10, 0xEED88EC0, 1024, 1, 0x00000000) Err#4 EINTR /3: Received signal #1, SIGHUP, in lwp_park() [default] So, can you try it (too) in terminator session?Yes, I can see the problem in Terminator. I even porter Terminator from Python to Python 3, but it still get terminated. Terminator is unfortunately not very lively project these days and I don't see any prospect in filing bug upstream. I also did not found any other record of someone having this particular problem.I am afraid we don't have any other tiling terminal at this moment...The best what I can suggest is to set "When command exits" in Preferences -> Profiles -> Command to something else than "Exit the terminal". Not perfect but at least you'll get the command's output.Still a backtrace will occur on stderr: Traceback (most recent call last):File "/usr/lib/python3.5/vendor-packages/terminatorlib/terminal.py", line 1386, in spawn_childdbg('spawning debug session with: %s:%s' % (details[0], TypeError: 'NoneType' object is not subscriptable<Window object at 0xfffffd7fec0b6708 (terminatorlib+window+Window at 0xbc8290)> is not in registered window listMichalHi Michal, all,this was not only 'terminator' problem, but also 'tmux' one (running within 'terminator'): it also exits. I did small experiment in 'mate-terminal' I have started 'tmux' session, and pane is also killed when trying to find out npm version!This can be prevented in 'tmux' with following configuration directives (bind-keys 'R' and 'r' should be free, or use another letters):bind-key R set-option remain-on-exit on bind-key r respawn-pane This is annoying too, since you have to respawn or kill pane... Here example of use of 'tmux' directives: ---8<------ :; tmux set-option remain-on-exit on :; npm --version 6.13.4 Pane is dead (signal 1, Tue Feb 11 10:15:41 2020) ---8<------NOTE: 'screen' utility handles all OK, so tab is not exited on 'npm --version' call in either combination with terminal programsRegards
Hi Predrag,yes, I can see the same behavior in `tmux` when in Xterm. Strange, but at least we know it's not the Terminator terminal.
Michal _______________________________________________ openindiana-discuss mailing list [email protected] https://openindiana.org/mailman/listinfo/openindiana-discuss
