Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40032 - [octave] fltk plotting bug

Attached to Project: Arch Linux
Opened by Ric (invik) - Tuesday, 22 April 2014, 16:15 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 15 May 2015, 03:00 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

In octave-3.8.1-1-x86_64, plotting with graphics_toolkit = fltk is broken (produces only corrupted images). Plotting with graphics_toolkit = gnuplot works fine.

When downgrading to octave-3.8.0-2-x86_64, plotting works fine again.


Steps to reproduce:

From the octave command shell,

1. If not set by default, set graphics engine to fltk by entering graphics_toolkit ("fltk").
2. Entering any plotting command (i.e. "plot(1)") produces a corrupted graphic.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 15 May 2015, 03:00 GMT
Reason for closing:  No response
Comment by Сковорода Никита (ChALkeR) - Saturday, 07 June 2014, 17:27 GMT
Works for me with octave 3.8.1-1-x86_64 and fltk 1.3.2-5-x86_64.
Comment by Ric (invik) - Monday, 09 June 2014, 11:40 GMT
Solved: I moved from nouveau video driver to nvidia, and now plotting octave-3.8.1-1-x86_64 works fine.

I guess it was an issue with the nouveau drivers, but I still wonder why it worked fine with octave-3.8.0-2-x86_64...
Comment by Сковорода Никита (ChALkeR) - Tuesday, 10 June 2014, 06:57 GMT
That could be a bug in either nouveau (buggy opengl implementation) or octave (relying on unspecified behaviour that works for some drivers).
Can you do an opengl trace (using community/apitrace) that reproduces the bug?
Comment by Сковорода Никита (ChALkeR) - Tuesday, 10 June 2014, 07:07 GMT
This is the test file and my trace.

Trace: $ apitrace trace octave point.m
Replay trace: $ apitrace replay -w octave-cli-3.8.1.trace
Gui: $ apitrace octave-cli-3.8.1.trace
   octave-cli-3.8.1.intel.trace (50.6 KiB)
   point.m (0 KiB)
Comment by Сковорода Никита (ChALkeR) - Tuesday, 10 June 2014, 07:30 GMT
Can you try to replay my trace on your nouveau setup and tell if it works?
If it does, please record your own trace that doesn't work.

Loading...