Vinux users have a problem with speakup possibly

[Georgina Joyce]

Hi All

A Vinux user seems to have a problem and wondered if any you guys have
any idea of whats going on?  Vinux is using a recent checkout of speakup
from git.

Hi Georgina, Speakup is not crashing whilst in use. It is very fast and
stable when in console mode. The problem seems to be that when you are
in a Gnome session for a long time when you try to switch to console
mode you can't unless you actually log out of the gnome session first.
However even though you can then get into console mode you can't then
get back to a GUI session either. The third symptom is that sometimes
when shutting down the computer dosesn't shut down but reports a
software bug, saying that speakup has failed to respond for 61 secs, and
this message just keeps looping every sixty seconds until you physically
turn off the machine. This is why I was asking about ways to kill
speakup. I will make sure that I get the exact message next time it
happens, but because I can't get into console mode I can't see what the
error message is, it is probably in a log file somewhere - any idea
where?
> 
> drbongo
> 
> On Fri, Sep 4, 2009 at 9:58 PM, Georgina Joyce <r2gl at o2.co.uk> wrote:
>         
>         Hi
>         
>         Not sure what a long time is but I've not experienced speakup
>         crashing.
>         Nor have I seen it mentioned on the speakup list.  I know that
>         Kirk runs
>         speakup 24-7 and others use it for system admin.  They would
>         really
>         appreciate feedback of such problems. 
>         
>         
>         
>         
>         four kinds of freedom, for the users of the software:
>         
>             * The freedom to run the program, for any purpose (freedom 0).
>             * The freedom to study how the program works, and adapt it to your
>         needs (freedom 1). Access to the source code is a precondition for this.
>             * The freedom to redistribute copies so you can help your neighbor
>         (freedom 2).
>             * The freedom to improve the program, and release your improvements
>         to the public, so that the whole community benefits (freedom 3). Access
>         to the source code is a precondition for this.
>         
>         Richard Matthew Stallman