FS#14924 - [wxmaxima] fails to connect to maxima backend

Attached to Project: Arch Linux
Opened by Davorin Učakar (phantom) - Tuesday, 02 June 2009, 18:21 GMT
Last edited by Ronald van Haren (pressh) - Monday, 15 June 2009, 05:13 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:
After starting wxMaxima it says in statusbar: "Maxima started. Waiting for connection ..." In console, it prints some error message (look attachment) and asks what to do.

Additional info:
* package version(s)
maxima 5.18.1-3
wxmaxima 0.8.2-2
sbcl 1.0.28-1

* config and/or log files etc.
The error remains if I delete ~/.wxMaxima. I'm not sure whether it's the only configuration file that affects wxMaxima/maxima/sbcl.

Steps to reproduce:
Start wxMaxima
   wxmaxima-output (6.4 KiB)
This task depends upon

Closed by  Ronald van Haren (pressh)
Monday, 15 June 2009, 05:13 GMT
Reason for closing:  Works for me
Comment by Gerardo Exequiel Pozzi (djgera) - Tuesday, 02 June 2009, 18:43 GMT
Works fine here, same programs versions. Do you try to delete/backup the file ~/.xmaximarc ?
Comment by Gerardo Exequiel Pozzi (djgera) - Tuesday, 02 June 2009, 18:47 GMT
Trying with xmaxima, in console can view these errors, but aparently works fine.
Comment by Ronald van Haren (pressh) - Tuesday, 02 June 2009, 18:55 GMT
works fine here too on x86_64. Are you using i686?
[edit] maxima itself does work I presume?
Comment by Gerardo Exequiel Pozzi (djgera) - Tuesday, 02 June 2009, 19:10 GMT
Note, xmaxima in console, only show these weird messages on exit.

I am currently on i686. I just tried on x86_64, in resume:

(i686)
maxima: OK
xmaxima: OK, but shows SBCL errors attached by phanthom on exit. (plus these errors at end [#1])
wxmaxima: OK

(SB-IMPL::SIMPLE-STREAM-PERROR "Couldn't write to ~s" #<SB-SYS:FD-STREAM for "a socket" {C78B7B1}> 32)
0] fatal error encountered in SBCL pid 30251(tid 3085101840):
%PRIMITIVE HALT called; the party is over.


Welcome to LDB, a low-level debugger for the Lisp runtime environment.
ldb> [djgera@arch32 ~]$


--------------------------------------------------------------------------------------------
(x86_64)
maxima: FAIL
xmaxima: FAIL
wxmaxima: FAIL

[djgera@arch64 ~]$ maxima
fatal error encountered in SBCL pid 2777(tid 140350229448432):
can't load .core for different runtime, sorry


Welcome to LDB, a low-level debugger for the Lisp runtime environment.
ldb>
--------------------------------------------------------------------------------------------

Comment by Gerardo Exequiel Pozzi (djgera) - Tuesday, 02 June 2009, 19:14 GMT
oops, missed the versions on x86_64 is the old 5.18.1-2, ignore the x86_64 report. Will try the latest.
Comment by Ronald van Haren (pressh) - Tuesday, 02 June 2009, 19:19 GMT
yeah the error you got usually appears when maxima is not compiled after a sbcl update.

@phantom: can you try:
sbcl --core /usr/lib/maxima/5.18.1/binary-sbcl/maxima.core --noinform --end-runtime-options --eval '(cl-user::run)' --end-toplevel-options -v '' ''
Comment by Gerardo Exequiel Pozzi (djgera) - Tuesday, 02 June 2009, 19:28 GMT
Confirmed, maxima-5.18.1-3 works fine in both 32 and 64 ;)

Only the weird message on exit from xmaxima(32,64) exist, but seems that "not is important". wxmaxima works fine on both(32,64)
Comment by Davorin Učakar (phantom) - Tuesday, 02 June 2009, 20:15 GMT
I have the same issue with xmaxima. Frontend window opens and the weird error message is printed on console soon after start. It doesn't respond to commands I write, so maxima backend probably isn't running or isn't connected.

I use i686 and I've deleted both ~/.maximarc and ~/.wxMaxima. maxima (the command-line) works fine.
Has anyone any idea what's going on?

@pressh:
I've just tried this -- maxima starts normally in command line.
Comment by Ronald van Haren (pressh) - Tuesday, 02 June 2009, 20:25 GMT
no I'm not too sure what is happening on your machine. On both my systems it behaves like Gerardo said.

There is another configuration file for xmaxima: ~/.xmaximarc. You can try removing that and start xmaxima. Does it give another error message?

If it does not work, can you try with a new user to rule out any configuration issues?

Loading...