[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave

https://bugs.kde.org/show_bug.cgi?id=406684 --- Comment #14 from avlas --- (In reply to Alexander Semke from comment #13) > (In reply to avlas from comment #12) > > I moved all issues to specific bug reports, with the exception of these two: > > > > B- Octave recommendations: > >(i) use Oct

[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave

https://bugs.kde.org/show_bug.cgi?id=406684 Alexander Semke changed: What|Removed |Added Resolution|--- |LATER Status|REPORTED

[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave

https://bugs.kde.org/show_bug.cgi?id=406684 --- Comment #12 from avlas --- I moved all issues to specific bug reports, with the exception of these two: B- Octave recommendations: (i) use Octave's default 'qt' graphics_toolkit instead of 'gnuplot' (ii) recommend using latest stable Octave

[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave

https://bugs.kde.org/show_bug.cgi?id=406684 --- Comment #11 from avlas --- Usability issue of omitted backends at startup: Filled specific bug here https://bugs.kde.org/show_bug.cgi?id=406779 -- You are receiving this mail because: You are watching all bug changes.

[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave

https://bugs.kde.org/show_bug.cgi?id=406684 --- Comment #10 from avlas --- Forgot about this: "I realized that Octave's warnings impede Cantor to proceed with expected outputs" Filled specific bug here: https://bugs.kde.org/show_bug.cgi?id=406777 -- You are receiving this mail because: You are

[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave

https://bugs.kde.org/show_bug.cgi?id=406684 --- Comment #9 from avlas --- > C- workspace: variables are not displayed specific bug: https://bugs.kde.org/show_bug.cgi?id=406776 -- You are receiving this mail because: You are watching all bug changes.

[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave

https://bugs.kde.org/show_bug.cgi?id=406684 --- Comment #8 from avlas --- Unfortunately this bug has become an umbrella of issues. The remaining issues are: A- Cantor packaging in kde neon: a specific bug has been filled B- Octave recommendations: (i) use Octave's default 'qt' graphics_tool

[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave

https://bugs.kde.org/show_bug.cgi?id=406684 --- Comment #7 from avlas --- Good news regarding point (2) above. It seems there is a bug either in flatpak's Octave, or in the upstream Octave code, which gives an error in cantor_print even though cantor_print uses a try-catch instruction. I will fi

[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave

https://bugs.kde.org/show_bug.cgi?id=406684 --- Comment #6 from avlas --- link to flatpak issue: https://github.com/flatpak/flatpak/issues/2846 -- You are receiving this mail because: You are watching all bug changes.

[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave

https://bugs.kde.org/show_bug.cgi?id=406684 --- Comment #5 from avlas --- I could make flatpak octave executable visible to flatpak cantor by doing: sudo flatpak override --filesystem=/var org.kde.cantor However it seems that this trick is not enough and communication between the two flatpak pr

[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave

https://bugs.kde.org/show_bug.cgi?id=406684 --- Comment #4 from avlas --- (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

[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave

https://bugs.kde.org/show_bug.cgi?id=406684 --- Comment #3 from Alexander Semke --- (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

[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave

https://bugs.kde.org/show_bug.cgi?id=406684 --- Comment #2 from avlas --- (In reply to Alexander Semke from comment #1) > (In reply to avlas from comment #0) > > there are problems with dependencies and system folders that are not visible > > because of how flatpak containers work, so wondering i

[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave

https://bugs.kde.org/show_bug.cgi?id=406684 --- Comment #1 from Alexander Semke --- (In reply to avlas from comment #0) > there are problems with dependencies and system folders that are not visible > because of how flatpak containers work, so wondering if the easiest way may > be offering a flat

[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave

https://bugs.kde.org/show_bug.cgi?id=406684 Иван Туманов changed: What|Removed |Added CC||tu4manj...@yandex.ru -- You are receiving this

[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave

https://bugs.kde.org/show_bug.cgi?id=406684 Иван Туманов changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail becau