https://bugs.kde.org/show_bug.cgi?id=420959

--- Comment #32 from avlas <jsar...@gmail.com> ---
(In reply to Nikita Sirgienko from comment #26)
> (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.

I'm sorry to insist. It may work for you but I think there are still issues
with this because this is not how it works in my system:

- Flatpak's Cantor is able to remove the file that I set by hand in /tmp, which
means Cantor is having access to /tmp, but the test fails anyway. Flatpak's
Octave is able to write to /tmp as well just fine as I can see plots in
Non-flatpak's Cantor. And both Cantors have the same config with respect to
Flatpak's Octave.

- Furthermore, once the test fails, nothing works in Flatpak's Octave anymore.

>From Octave options in Cantor I see that I can use png/jpg/svg but not eps as
you are showing in your screenshot. I guess this is because in flatpak
ghostscript is not available. Wondering if that makes the difference between
what you see and what I see.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to