[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #56551] Ctrl-C does not work properly in Octav
From: |
anonymous |
Subject: |
[Octave-bug-tracker] [bug #56551] Ctrl-C does not work properly in Octave started via Flatpak over SSH |
Date: |
Tue, 25 Jun 2019 23:28:48 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0 |
URL:
<https://savannah.gnu.org/bugs/?56551>
Summary: Ctrl-C does not work properly in Octave started via
Flatpak over SSH
Project: GNU Octave
Submitted by: None
Submitted on: Wed 26 Jun 2019 03:28:46 AM UTC
Category: None
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: None
Status: None
Assigned to: None
Originator Name: Christian
Originator Email: address@hidden
Open/Closed: Open
Discussion Lock: Any
Release: 5.1.0
Operating System: GNU/Linux
_______________________________________________________
Details:
Running Octave 5.1, started via Flatpak, on a remote host over SSH does not
work properly. Pressing Ctrl-C results in a weird behaviour, partially
disconnecting the terminal from the Octave instance.
Note: The OS is Ubuntu 18.04.
The terminal output below intends to demonstrate this.
To reproduce, it's a matter of:
- Connect to remote host via SSH
- Start Octave using Flatpak
- Press Ctrl-C
Pressing Ctrl-C seem to partially disconnect the terminal from the Octave
instance, although the latter seem to still be running.
The regular Bash prompt is seen, but also (sometimes) an Octave prompt.
The Octave process also still seems to be running until I kill it.
I'm so used to pressing Ctrl-C in Octave (to abort a command line) that this
problem makes Octave/Flatpak unusable for me over SSH.
local-host$ # First connect to a remote host, with X11 forwarding
local-host$ ssh remote-host
$ # On remote host, start Octave
$ flatpak run org.octave.Octave
GNU Octave, version 5.1.0
<snip>
octave:1> 1
ans = 1
octave:2> # Now test pressing Ctrl-C. This will cause weird behaviour
$
octave:2>
$
�$ ���flatpak run --share=network --command=bash org.octave.Octave -c
"DISPLAY=$DISPLAY octave"^C
$ ps
� PID TTY TIME CMD
24540 pts/15 00:00:00 bash
27327 pts/15 00:00:00 bwrap
27328 pts/15 00:00:00 octave-gui
27344 pts/15 00:00:00 ps
$ ki�
lparse error:
invalid character '�' (ASCII 254)
>>> ������
^
octave:2> �l�
parse error:
invalid character '�' (ASCII 254)
>>> ��
^
octave:2> -�9 2�
7parse error:
invalid character '�' (ASCII 254)
>>> ��
^
octave:2> �32�8
$ ps
PID TTY TIME CMD
24540 pts/15 00:00:00 bash
27347 pts/15 00:00:00 ps
$
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?56551>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #56551] Ctrl-C does not work properly in Octave started via Flatpak over SSH,
anonymous <=