https://bugs.kde.org/show_bug.cgi?id=420959
--- Comment #26 from Nikita Sirgienko <warqu...@gmail.com> --- (In reply to avlas from comment #24) > > I think I didn't explain myself quite well. Let me try again: > > I was not trying to get into the ultimate problem of why the test fails > (which is that cantor uses a different /tmp inside its sandbox). > > I was just mentioning that when the test fails, Cantor should be smart > enough to only limit these functions that require accessing to system's > /tmp, i.e. plotting, and work fine otherwise, so that users can execute > Octave's commands that are not associated with plotting. Yes, this is correct, and this is actually how new code works. For example, when use my normally builed Cantor (master branch) and Octave from flatpak (without enabled access to /tmp), I have gotten error message about disabling plot integration, but after closing it, Octave backend works correctly and even plots works (but appears in separate window, because of disabled plot integration I have also tried reproduce your problem, but I failed to run Cantor from flatpak with Octave from flatpak. -- You are receiving this mail because: You are watching all bug changes.
