Octave print() incompatible with gnuplot5

Bug #1568647 reported by Vertago1
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Octave
Unknown
Unknown
octave (Debian)
Fix Released
Unknown
octave (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

After updating to 16.04 some of my octave scripts broke because they use gnuplot to print and the default has become gnuplot5 which has compatibility problems with octave. This is a known problem upstream, see:
http://savannah.gnu.org/bugs/?42838

I found a workaround (if gnuplot4 is installed):
sudo update-alternatives --set gnuplot /usr/bin/gnuplot4-x11

This sets the gnuplot symbolic link to point to gnuplot4 instead of gnuplot5 system wide which isn't ideal in the scenario someone needs to use gnuplot5 elsewhere. I checked for a way to configure the gnuplot path for octave but didn't see anything immediately obvious. Maybe I missed something.

I suppose changing the PATH variable for octave might be a workable patch. I figure this but probably won't get fixed before the release, but I wanted to post it so anyone who runs into the problem will see the work around.

Revision history for this message
Vertago1 (vertago1) wrote :
Revision history for this message
Vertago1 (vertago1) wrote :
Revision history for this message
Vertago1 (vertago1) wrote :
Revision history for this message
Mike Miller (mtmiller) wrote :

Thanks for the detailed bug report. As you noticed, this is upstream bug #42838, and is fixed in the upstream release 4.0.1. Merging the 4.0.1 release (which is already in Debian testing) into the Ubuntu archive will fix this bug.

Changed in octave (Ubuntu):
status: New → Confirmed
Changed in octave (Debian):
status: Unknown → New
Changed in octave (Debian):
status: New → Fix Released
Changed in octave (Ubuntu):
importance: Undecided → Low
importance: Low → Medium
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

Uploaded a few seconds ago in yakkety

Changed in octave (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.