[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #40685] octave fails with no DISPLAY, used to
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #40685] octave fails with no DISPLAY, used to fall back to cli mode |
Date: |
Sat, 23 Nov 2013 23:19:06 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36 |
URL:
<http://savannah.gnu.org/bugs/?40685>
Summary: octave fails with no DISPLAY, used to fall back to
cli mode
Project: GNU Octave
Submitted by: mtmiller
Submitted on: Sat 23 Nov 2013 06:19:05 PM EST
Category: GUI
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Incorrect Result
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: GNU/Linux
_______________________________________________________
Details:
Reporting on behalf of this thread:
http://octave.1599824.n4.nabble.com/Warning-lt-octave-gui-cannot-connect-to-X-server-td4659449.html
This did work not too long ago, if not running in X or unable to connect to X
for whatever reason, the GUI was not run and the octave executable falls back
to octave-cli.
Now that we are considering disabling the GUI unless explicitly enabled with
--gui, this may become fixed as a side effect.
Should octave fall back to command-line even if --gui is requested if the GUI
can't be started or should it error?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?40685>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #40685] octave fails with no DISPLAY, used to fall back to cli mode,
Mike Miller <=