Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#21236 - [maxima] wxmaxima cannot connect to maxima

Attached to Project: Arch Linux
Opened by David Kremer (dkremer) - Wednesday, 13 October 2010, 18:20 GMT
Last edited by Jürgen Hötzel (juergen) - Monday, 01 November 2010, 15:16 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jürgen Hötzel (juergen)
Ronald van Haren (pressh)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
#1 install wxmaxima
#2 launch wxmaxima
#3 try eg diff(x^3,x,1); shift+enter
#4 observe the pop up saying "not connected to maxima!"

Additional info:
* package version(s): last in arch repo
* config and/or log files etc: no log

Steps to reproduce:

#1 install wxmaxima
#2 launch wxmaxima
#3 try eg diff(x^3,x,1); shift+enter
#4 observe the pop up saying "not connected to maxima!"
This task depends upon

Closed by  Jürgen Hötzel (juergen)
Monday, 01 November 2010, 15:16 GMT
Reason for closing:  Works for me
Additional comments about closing:  Cannot confirm. I just updated and tested:

maxima-5.21.1-4-i686.pkg.tar.xz (i686)
sbcl-1.0.43-1-i686.pkg.tar.xz (i686)
maxima-5.21.1-4-x86_64.pkg.tar.xz (x86_64)
sbcl-1.0.43-1-x86_64.pkg.tar.xz (x86_64)
Comment by David Kremer (dkremer) - Wednesday, 13 October 2010, 20:58 GMT
It's not a wxmaxima bug but a maxima one. I compiled maxima with clisp installed it solves the problem. TCP support is not installed with maxima.
Comment by Ronald van Haren (pressh) - Thursday, 14 October 2010, 07:52 GMT
We use the sbcl lisp backend as it should be much faster.

maxima and wxmaxima work both fine for me on x86_64. What architecture are you on? What output does maxima give when you start it from the cli?
Comment by David Kremer (dkremer) - Thursday, 14 October 2010, 16:26 GMT
:~$ maxima -s 4000
Connecting Maxima to server on port 4000
Maxima encountered a Lisp error:

Protocol not found: "tcp"

Automatically continuing.
To enable the Lisp debugger set *debugger-hook* to nil.

debugger invoked on a SB-INT:SIMPLE-CONTROL-ERROR in thread #<THREAD
"initial thread" RUNNING
{C3C8B79}>:
attempt to THROW to a tag that does not exist: RETURN-FROM-DEBUGGER

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
0: [CONTINUE] Ignore runtime option --eval "(cl-user::run)".
1: [ABORT ] Skip rest of --eval and --load options.
2: Skip to toplevel READ/EVAL/PRINT loop.
3: [QUIT ] Quit SBCL (calling #'QUIT, killing the process).

("no debug information for frame")
0]

Loading...