https://bugs.kde.org/show_bug.cgi?id=406684
--- Comment #5 from avlas <jsar...@gmail.com> --- 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 processes does not work as expected, i.e. any instruction makes cantor turn crazy waiting for a never reached octave's response, with a 100% CPU issue. I think I will open an issue in flatpak to see how this is expected to be done... In the meantime I would like to mention a usability issue in the context of point (1) above: I would recommend against filtering not configured backends at cantor startup (if not default backend is set). This is a matter of usability, mostly important for new users trying cantor: A new user may want to use e.g. Octave to make it default and configure its path (if not automatically detected). With current filtering this is not an option and gives the impression that such an option is not supported. So most final users will give up. Advanced users may realize that they can open any other available backend (if any) and go to settings to configure e.g. Octave's path. This is far from ideal. Ideally, all backends would be present without filtering. Then, if one selects a backend that is not properly configured, settings should be opened, so the user can set them right. -- You are receiving this mail because: You are watching all bug changes.
