[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Axiom-developer] Re: Bug#328480: axiom: Still seems to be a problem
From: |
Camm Maguire |
Subject: |
[Axiom-developer] Re: Bug#328480: axiom: Still seems to be a problem |
Date: |
01 Nov 2006 10:16:19 -0500 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 |
reopen 328480
forwarded 328480 address@hidden
thanks
Greetings, and thanks so much for your feedback!
Colin Turner <address@hidden> writes:
> Hi Camm,
>
> Camm Maguire wrote:
> > Greetings!
> >
> > OK, just double checked with the latest 20050901-7, and I cannot
> > reproduce. I think this must be come xserver/configuration problem.
>
> Possible, I suppose it might have coincided with an xorg upgrade;
> however, the issue is exactly as identified in previous bug report -
> it's also exactly replicated on several machines on which I have axiom,
> and it all worked in the past.
>
> I can't now test Tim's num-lock theory for the reasons stated below.
> However, I was able to change the cell of focus with the mouse, but no
> keys produced any output, on the keypad or otherwise.
>
> > There is an axiom wiki for frequently encountered problems. Can you
> > identify anything there with something similar? Can you try asking at
> > <address@hidden>?
>
> I've just had a look through it. I don't see anything yet.
>
> >> I'm still experiencing this bug in version 20050901-6.
> >> As before no input in the areas in hyperdoc is accepted.
>
> Unfortunately, in 20050901-7 I'm having a different problem.
>
> If I go to reference -> search in the hyperdoc system, I *can* enter text.
>
OK, so this issue would appear closed.
> However, if I for example go to
>
> Settings -> Settings
>
> or
>
> Basic Commands -> Calculus -> Differentiate
>
> an hourglass appears, never dismisses and
>
> (1) ->
> (1) ->
> >> System error:
> Unexpected end of #<string-input stream from " ...">.
>
> (1) ->
>
> appears in the console (which is still active). Again, this happens on
> two machines I have dist-upgraded. Num-lock makes no difference for this
> at least.
>
OK, sock_get_string_buf, which appears correctly prototyped, is
returning 0, which from the code appears to indicate a socket read
error in one of the routines in sockio-c.c.
Fellow axiom developers -- any ideas here?
Take care,
> I'll keep searching the wiki. Thanks for the help.
>
> CT.
>
>
>
--
Camm Maguire address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Axiom-developer] Re: Bug#328480: axiom: Still seems to be a problem,
Camm Maguire <=