Bug 379404 - Cantor can't initialize session for maxima backend
Summary: Cantor can't initialize session for maxima backend
Status: RESOLVED FIXED
Alias: None
Product: cantor
Classification: Applications
Component: maxima-backend (show other bugs)
Version: 17.04
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Filipe Saraiva
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-01 12:11 UTC by hackitforfun
Modified: 2018-05-30 22:16 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In: 18.04


Attachments
cantor.log (18.45 KB, text/plain)
2017-08-12 14:49 UTC, Coacher
Details
cantor-strace.log (1000.66 KB, text/plain)
2017-08-12 14:49 UTC, Coacher
Details
attachment-13196-0.html (1.28 KB, text/html)
2018-05-04 19:51 UTC, hackitforfun
Details

Note You need to log in before you can comment on or make changes to this bug.
Description hackitforfun 2017-05-01 12:11:00 UTC
Platform: arch linux
cantor version: 17.04
maxima version: 5.39

Initializing session takes forever, after cancelling the initialization, maxima help menu appears fine, but no cursor or text, making it impossible to use maxima as backend for cantor.
Comment 1 Filipe Saraiva 2017-05-01 14:50:00 UTC
Hi @hackitforfun, I could not reproduce your bug. Please, could you provide the output of 'maxima -v' command?

In my case:

$ maxima -v
+ '[' clisp = clisp ']'
+ '[' true = true ']'
+ '[' -x /usr/lib/maxima/5.39.0/binary-clisp/maxima ']'
+ exec /usr/lib/maxima/5.39.0/binary-clisp/lisp.run -q -M /usr/lib/maxima/5.39.0/binary-clisp/maxima.mem '' -- -v
Maxima 5.39.0 http://maxima.sourceforge.net
using Lisp CLISP 2.49 (2010-07-07)
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.
(%i1)
Comment 2 hackitforfun 2017-05-01 14:54:06 UTC
(In reply to Filipe Saraiva from comment #1)
> Hi @hackitforfun, I could not reproduce your bug. Please, could you provide
> the output of 'maxima -v' command?
> 
> In my case:
> 
> $ maxima -v
> + '[' clisp = clisp ']'
> + '[' true = true ']'
> + '[' -x /usr/lib/maxima/5.39.0/binary-clisp/maxima ']'
> + exec /usr/lib/maxima/5.39.0/binary-clisp/lisp.run -q -M
> /usr/lib/maxima/5.39.0/binary-clisp/maxima.mem '' -- -v
> Maxima 5.39.0 http://maxima.sourceforge.net
> using Lisp CLISP 2.49 (2010-07-07)
> Distributed under the GNU Public License. See the file COPYING.
> Dedicated to the memory of William Schelter.
> The function bug_report() provides bug reporting information.
> (%i1)
Thanks for the reply, here's the output

❯ maxima -v
+ '[' ecl = clisp ']'
+ '[' ecl = cmucl ']'
+ '[' ecl = scl ']'
+ '[' ecl = gcl ']'
+ '[' ecl = acl ']'
+ '[' ecl = openmcl ']'
+ '[' ecl = ccl64 ']'
+ '[' ecl = ecl ']'
+ exec /usr/lib/maxima/5.39.0/binary-ecl/maxima -- -v
;;; Loading #P"/usr/lib/ecl-16.1.2/sb-bsd-sockets.fas"
;;; Loading #P"/usr/lib/ecl-16.1.2/sockets.fas"
;;; Loading #P"/usr/lib/ecl-16.1.2/defsystem.fas"
;;; Loading #P"/usr/lib/ecl-16.1.2/cmp.fas"
Maxima 5.39.0 http://maxima.sourceforge.net
using Lisp ECL 16.1.2
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.
(%i1)
Comment 3 Alaksiej Stankievič 2017-06-06 22:39:19 UTC
I'm also on archlinux and have the same problem.
cantor 17.04.1
maxima 5.38.1

> maxima -v
+ '[' sbcl = clisp ']'
+ '[' sbcl = cmucl ']'
+ '[' sbcl = scl ']'
+ '[' sbcl = gcl ']'
+ '[' sbcl = acl ']'
+ '[' sbcl = openmcl ']'
+ '[' sbcl = ecl ']'
+ '[' sbcl = sbcl ']'
+ '[' -x /usr/lib/maxima/5.38.1/binary-sbcl/maxima ']'
+ exec sbcl --core /usr/lib/maxima/5.38.1/binary-sbcl/maxima.core --noinform --end-runtime-options --eval '(cl-user::run)' --end-toplevel-options -v
Maxima 5.38.1 http://maxima.sourceforge.net
using Lisp SBCL 1.3.17
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.

Alaksiej Stankievič
Comment 4 Alaksiej Stankievič 2017-06-06 22:53:12 UTC
I have downgraded to 16.12.3 and now maxima session works
Comment 5 Coacher 2017-08-12 14:49:00 UTC
Created attachment 107234 [details]
cantor.log

Cantor-16.12.3 with KF-5.34.0 and Maxima-5.40.0 works fine.
Here are messages from cantor when running from the terminal.
Comment 6 Coacher 2017-08-12 14:49:47 UTC
Created attachment 107235 [details]
cantor-strace.log

And here's strace log of the same session.
Comment 7 Coacher 2017-08-23 09:34:52 UTC
Cantor-17.04.3 with KF-5.34.0 and Maxima-5.40.0 hangs.
Comment 8 Rik Mills 2017-08-24 07:52:09 UTC
Maxima backend is similarly broken for ubuntu 17.10

Cantor: 17.04.3
maxima: 5.40.0
KF5: 5.37
Comment 9 Alexander Semke 2018-05-01 06:08:59 UTC
The login mechanism was refactored and made more stable. The problem should be fixed now in 18.04. Please give it a try.
Comment 10 Alaksiej Stankievič 2018-05-03 06:36:49 UTC
Platform: arch linux
cantor version: 18.04
maxima version: 5.41

I confirm that maxima session in cantor works properly.

Thanks for fixing.
Comment 11 hackitforfun 2018-05-04 19:51:47 UTC
Created attachment 112419 [details]
attachment-13196-0.html

I confirm that maxima session can be inititiated.
However, I have to manually interrupt the backend (in this case maxima) in
order to do the next calculation. This is not normal, isn't it ?
Thanks for the fix anyway.

Platform: arch linux
cantor version: 18.04
maxima version: 5.41

On Thu, May 3, 2018 at 8:36 AM, Alaksiej Stankievič <
bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=379404
>
> --- Comment #10 from Alaksiej Stankievič <harald_zealot@tut.by> ---
> Platform: arch linux
> cantor version: 18.04
> maxima version: 5.41
>
> I confirm that maxima session in cantor works properly.
>
> Thanks for fixing.
>
> --
> You are receiving this mail because:
> You reported the bug.
>
Comment 12 Alexander Semke 2018-05-05 13:13:04 UTC
(In reply to hackitforfun from comment #11)
> Created attachment 112419 [details]
> attachment-13196-0.html
> 
> I confirm that maxima session can be inititiated.
> However, I have to manually interrupt the backend (in this case maxima) in
> order to do the next calculation. This is not normal, isn't it ?
This is not normal, of course. I cannot reproduce this. Do you always have this behavior or for some certain commands only?
Comment 13 Christoph Feck 2018-05-30 22:16:04 UTC
If you can provide the information requested in comment #12, please add it.