Bug 1149396 - octave fails to exec octave-gui
octave fails to exec octave-gui
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Development
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: Dmitry Roshchin
E-mail List
Depends on:
  Show dependency treegraph
Reported: 2019-09-04 13:12 UTC by Tom de Vries
Modified: 2019-11-08 10:08 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Tom de Vries 2019-09-04 13:12:35 UTC
Starting from the situation that I don't have octave installed, I get:
$ octave
If 'octave' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    cnf octave

Following the cnf suggestion, I get a package install suggestion:
$ cnf octave
The program 'octave' can be found in the following package:
  * octave-cli [ path: /usr/bin/octave, repository: zypp (repo-oss) ]

Try installing with:
    sudo zypper install octave-cli

Following the package install suggestion, I get the octave command:
$ sudo zypper install octave-cli
(1/1) Installeren van: octave-cli-5.1.0-lp151.1.15.x86_64 ................................................[gereed]

However, I get:
$ octave -q
/usr/lib64/octave/5.1.0/exec/x86_64-suse-linux-gnu/octave-gui: failed to exec '/usr/lib64/octave/5.1.0/exec/x86_64-suse-linux-gnu/octave-gui'
octave: No such file or directory

I can work around this by doing
$ DISPLAY= octave -q

This worked without a problem in leap 42.3 and 15.0, but fails in 15.1 and tumbleweed.
Comment 1 Dmitry Roshchin 2019-09-07 08:40:53 UTC
Looks like we need to go back to update-alternatives mechanism...
Comment 2 Atri Bhattacharya 2019-11-08 09:59:01 UTC
This has already been fixed as of octave 4.4.x by upstream. That is, invoking octave from the command line -- on Tumbleweed, for example -- does not launch the GUI any more. So, perhaps we only need to submit this as a patch to the affected Leap versions (where we have octave < 4.4)? I don't think we need the whole update-alternatives mechanism here.

See https://www.gnu.org/software/octave/NEWS-4.4.html
Comment 3 Atri Bhattacharya 2019-11-08 10:08:55 UTC
Sorry, ignore my previous comment. There is an issue on TW also, which is puzzling to me. Anyway, the update-alternatives mechanism will indeed fix this issue then.