https://bugs.kde.org/show_bug.cgi?id=406684
--- Comment #4 from avlas <jsar...@gmail.com> --- (In reply to Alexander Semke from comment #3) > (In reply to avlas from comment #2) > > 2) Then, in Cantor, I configured the path to octave (from the flatpak > > container). > > > > This works, however the internal cantor scripts () fail. I could not figure > > out how to fix this. For instance, (i) first instruction fails with no > > output but "__cantor_delimiter_line__", (ii) plot instructions fail with > > "error: 'cantor_print' undefined near line 1 column 12". Also, variables do > > not appear in the workspace. > It looks like some scripts are not found. Can you please check where the > script cantor_print.m is located on your system? It must be in > /usr(/local)/share/cantor/octavebackend/. I'm not sure how this is handled > in flatpack containers. "__cantor_delimiter_line__" occurs irrespective of this. the error of cantor_print is because the filesystem is not visible to flatpak containers, but this can be workarounded by adding that folder to the Octave path, e.g. copying the folder to home and using Octave's addpath. However if I do I see first a warning: warning: your version of GraphicsMagick limits images to 8 bits per pixel and then an error: free(): double free detected in tcache 2 but no figure appears > > 3) There is no way I can make Cantor Nightly aware of Octave (so I couldn't > > test further than that). This may happen because they, being containers, do > > not see each other (use different filesystems). There should be proper ways, > > though, allowing interactions between flatpak applications. > This is rather a question to this container infrastructure. Cantor needs > e.g. octave if the user wants to work with octave. If the existence of > octave is hidden from cantor, I don't see how we can fix this. Flatpak offers exports, etc, to make executables visible, so I'm sure this can be done. I'll investigate a bit on this > > 4) Cantor recommends Octave 4.0 or 4.2, but there is Octave 5.1 and 4.4 (in > > fact all 4.x should be discouraged at this moment). > Ok. We'll test with the new version and we'll change the recommended version > to Octave 5.1 in the next release. Thank you, very appreciated! [ Regarding (1) above, I filled https://bugs.kde.org/show_bug.cgi?id=406712 ] -- You are receiving this mail because: You are watching all bug changes.
