On Thursday, April 11, 2002, at 11:10 AM, Bakul Shah wrote:
>> However, once I start it, I get a complaint about ".../maxima_saved"
>> not
>> being found (I think that's the name). Does anyone know what might be
>> going wrong here? This is complicated by the fact that, once I dismiss
>> the timeout alert that follows the complaint, the whole desktop is
>> blown
>> away, and my login environment is restarted.
>
> These are familiar symptoms (on a FreeBSD system)! xmaxima
> seems to assume gcl is used (unfortunately only clisp works
> on FreeBSD at present). However,
> xmaxima -lisp clisp
> cured it.
That had an effect: I no longer get the complaining about
'.../maxima_saved'. However, the rest is still an issue. The GUI is
essentially non-functional (as far as double-clicking is concerned), and
I do still get the timeout dialog (waiting for maxima to start), after
which, the login environment bails. This could be an XonX problem, but
I don't get the reason for the timeout.
Also, I get this on startup of xmaxima:
errno = EILSEQ: Invalid multibyte or wide character.
Alas, the console log doesn't have anything useful in it, and it gets
killed right away, so I don't know if there would be anything useful in
it. The system log is likewise devoid of useful info.
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics | When LuteFisk is outlawed
| Only outlaws will have
| LuteFisk
*--------------------------------------*-------------------------------*--