Maxima backend fails to start in cantor 17.04
Bug #1714439 reported by
Rik Mills
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KDE Educational Applications |
Fix Released
|
Medium
|
|||
cantor (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
As per KDE bug: https:/
Interface hangs indefinitely on "initiating session".
Version 16.12.3 seems so work ok.
This is resulting in package version 17.04.3 being stuck in -proposed pocket for artful, as the 'testmaxima' autopackagetest inevitability fails.
Options to fix may be:
(a) Fix of the backend in KDE Apps 17.04 to work with maxima version in artful, or;
(b) Disable the backend build and resultant test, and either remove the backend binary package or mark it as empty and broken pending a better fix, or;
(c) Delete the version 17.04.3 from artful proposed, and upload a no-change rebuild against the new analitza libs already in artful release.
Changed in kdeedu: | |
importance: | Unknown → Medium |
tags: | removed: block-proposed |
Changed in kdeedu: | |
status: | Unknown → Fix Released |
Changed in cantor (Ubuntu): | |
status: | New → Fix Released |
To post a comment you must log in.
(a) is preferable obviously, but may not be quick happening
(b) will work ok. have tested a build locally with autotests build and run in LXC against arftul
(c) need to do a test rebuild in a PPA for that, to confirm it works and no regressions when building the old 16.12.3 version against new analitza 17.04.3 libs