SUMMARY same issue as in KDE Bugtracker #405341 , except for the KDE neon packages STEPS TO REPRODUCE 1. try to add an CAS (maxima) worksheet, it is nowhere to be found 2. please add a default option to compile this option 3. I tried native as well as flatpak, both have the same behavior OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon (18.04) KDE Plasma Version: now 4+p18.04+git20190322.1030 amd64 Qt Version: 5.12.0+dfsg-0+xneon+18.04+bionic+build54 amd64 ADDITIONAL INFORMATION tried stable and nightly builds from the flatpak version, both are identically regarding the CAS sheet
LabPlot has to be compiled with the support for Cantor. In addition to this, the required CAS has to be installed. Do you have Maxima installed on your computer? Having read about the flatpack... If you have everything installed via flatpack you can run into the same problem as reported here https://bugs.kde.org/show_bug.cgi?id=406684 https://github.com/flatpak/flatpak/issues/2846 If I understand the problem correctly, this is because the files from different containers are not visible outside of the containers. With this, maxima's executable cannot be found on start and we don't allow to create maxima worksheets.
Dear Alexander, thank you for your fast reply. (In reply to Alexander Semke from comment #1) > LabPlot has to be compiled with the support for Cantor. In addition to this, > the required CAS has to be installed. Do you have Maxima installed on your > computer? I run KDE Neon (18.04) with the latest maxima 5.42.0 under SBCL 1-4-12 (wxmaxima GUI) as well as the cantor 19.04.0 (kde neon version) and all dev packages that seem appropriate. I tried to compile the GIT version git clone git://anongit.kde.org/labplot All packages worked for me, except the two following ones: -- MQTT Library NOT FOUND -- Cantor Library NOT FOUND MQTT isn#t important for me (even so the libs are installed ?) Cantor looks like a problem from the KDE Neon package, because --8<------------------------------------- cantor/bionic,now 4:19.04.0-0xneon+18.04+bionic+build26 amd64 [installiert] cantor-backend-kalgebra/bionic,now 4:19.04.0-0xneon+18.04+bionic+build26 amd64 [installiert] cantor-backend-lua/bionic,now 4:19.04.0-0xneon+18.04+bionic+build26 amd64 [installiert] cantor-backend-maxima/bionic 4:17.12.3-0ubuntu1 i386 cantor-backend-octave/bionic,now 4:19.04.0-0xneon+18.04+bionic+build26 amd64 [installiert] cantor-backend-python3/bionic,now 4:19.04.0-0xneon+18.04+bionic+build26 amd64 [installiert] cantor-backend-qalculate/bionic,now 4:19.04.0-0xneon+18.04+bionic+build26 amd64 [Installiert,automatisch] cantor-backend-r/bionic,now 4:19.04.0-0xneon+18.04+bionic+build26 amd64 [installiert] cantor-backend-scilab/bionic,now 4:19.04.0-0xneon+18.04+bionic+build26 amd64 [installiert] cantor-dev/bionic 4:18.12.3-0xneon+18.04+bionic+build23 amd64 <<<<<<<<<<!! libcantor-pythonbackend/bionic,now 4:19.04.0-0xneon+18.04+bionic+build26 amd64 [Installiert,automatisch] -----8<--------------------------------------------------- The package source has the 19.04 version installed, but offers only 18.12.3 as the dev symbols :-( I don't know if some knows the right person / list for mentioning the issue ? > Having read about the flatpack... If you have everything installed via > flatpack you can run into the same problem as reported here > https://bugs.kde.org/show_bug.cgi?id=406684 > https://github.com/flatpak/flatpak/issues/2846 > > If I understand the problem correctly, this is because the files from > different containers are not visible outside of the containers. With this, > maxima's executable cannot be found on start and we don't allow to create > maxima worksheets. Too bad I didn't know that, here the new package world makes life hard again. otherwise flatpak work good, but I prefer appimages ;-) (don't know if there is the same problem hidden ...) best regards, Marcus Menzel
Hi Marcus, (In reply to Marcus Menzel from comment #2) > The package source has the 19.04 version installed, but offers only 18.12.3 > as the dev symbols :-( > I don't know if some knows the right person / list for mentioning the issue ? neon has its own bugzilla component on bugs.kde.org. Just create a bugzilla for neon and describe the problem. > > Too bad I didn't know that, here the new package world makes life hard again. > otherwise flatpak work good, but I prefer appimages ;-) (don't know if there > is the same problem hidden ...) Looks like there is a solution/workaround available for this problem as mentioned in the comments in https://github.com/flatpak/flatpak/issues/2846. I'm not sure yet who has to adress this now, the developers or the image builders. I'll need some time to become familiar with flatpack a bit first... Regards, Alexander