https://bugs.kde.org/show_bug.cgi?id=420959
--- Comment #21 from avlas <jsar...@gmail.com> --- (In reply to Nikita Sirgienko from comment #20) > Git commit 87172a9416a8949cc80350b733d771d7b01d90f3 by Nikita Sirgienko. > Committed on 11/05/2020 at 22:37. > Pushed by sirgienko into branch 'master'. > > [Octave] Add check, if Octave can have write in temporary dir > FIXED-IN: 20.07.70 > > M +2 -1 src/backends/octave/CMakeLists.txt > M +1 -1 src/backends/octave/octaveexpression.cpp > M +48 -2 src/backends/octave/octavesession.cpp > M +3 -0 src/backends/octave/octavesession.h > M +1 -1 src/lib/CMakeLists.txt > M +38 -0 src/lib/backend.cpp > M +8 -1 src/lib/backend.h > > https://invent.kde.org/kde/cantor/commit/ > 87172a9416a8949cc80350b733d771d7b01d90f3 I tested this fix (using Cantor's nightly flatpak package) and although it's informative about missing plotting capabilities, it could be improved. This is the popup dialog I got: ``` Plot integration test failed. Failed to open the file /tmp/cantor_octave_plot_integration_test.txt during the plot integration test. The integration of plots will be disabled. ``` First, I don't think the user needs to know about /tmp/cantor_octave_plot_integration_test.txt, just telling that access to the /tmp was not granted would likely be enough. But more importantly Octave fails to work at all afterwards, not only plotting is limited but instructions such as `2+2` also fail: no output and no error messages telling what's wrong either. Ideally the user should be told about missing plot capability but she would be allowed to work otherwise... -- You are receiving this mail because: You are watching all bug changes.
