[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #42254] Crash on ^C
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #42254] Crash on ^C |
Date: |
Thu, 01 May 2014 12:53:42 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 |
Update of bug #42254 (project octave):
Status: None => Wont Fix
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
Hi, thanks for your bug report. This exact issue has been reported before and
is unfortunate but is currently the expected behavior.
Do not run octave-gui directly. Use octave --force-gui instead. The octave-gui
program should be hidden deep in an internal library directory and should not
be on your $PATH. If it is on your $PATH, that is a packaging/distribution
bug. The octave program needs to run first to properly disassociate from the
controlling terminal. This may change in a future version, but it's what we
have for now.
If running octave --force-gui does not resolve this issue, feel free to
request reopening this report.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?42254>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/