Martin Schulze | 6 Oct 10:23 2003

BrailleSpeak Debian Mini-Distribution

FYI.

The BrailleSpeak Project have released its
NEW "BrlSpeak Debian-based Braille-Loopback Mini-Distribution".

This Debian-based loopback distribution of GNU/Linux is no longer
UMSDOS as by the past (cf. previous Slack-based BrlSpeak) but it still aims
to provide a (temporary) solution for those who want/need/prefer
installing/trying a mini-distribution on their FAT partition, without having
to repartition the hard disk.

http://www.brlspeak.net/
http://search.luky.org/cola.2003/msg01030.html
http://www.brlspeak.net/release

Regards,

	Joey

--

-- 
Everybody talks about it, but nobody does anything about it!  -- Mark Twain

Please always Cc to me when replying to me on the lists.

Attila Konietzka | 6 Oct 16:40 2003
Picon
Picon

gnome and debian + gnopernicus

hi,
Did anyone get gnome + gnopernicus up and running on debian testing?
I aks because i want to try it out, after the brand new garnome system gave
me errors after errors when installing and no hints to fix it up.
i grabbed:

# apt-get install gnome-core gnopernicus,

but still it isn't enough, i get errors like this:
gtk+-warning: can't open display.

So if anyone has an idea what to grab in order for gnome to work on debian
together with gnopernicus along with installation and configuration hints
and is willing to help me, i'd be very grateful.
Regards, Attila.

Mario Lang | 6 Oct 19:45 2003
Picon

Re: gnome and debian + gnopernicus

Attila Konietzka <attilakonietzka <at> gmx.net> writes:

> Did anyone get gnome + gnopernicus up and running on debian testing?
Last time I checked, it did work, yes.

> I aks because i want to try it out, after the brand new garnome system gave
> me errors after errors when installing and no hints to fix it up.
> i grabbed:
>
> # apt-get install gnome-core gnopernicus,
>
> but still it isn't enough, i get errors like this:
> gtk+-warning: can't open display.

When do you get this error message?  It sort of looks to me as if you
were trying to start gnopernicus from the normal (console) command line?
You need to start up GNOME, before you will be able to use the Gnopernicus
screen reader.  This also involves configuring a working X Windows System.

--

-- 
CYa,
  Mario | Debian Developer <URL:http://debian.org/>
        | Get my public key via finger mlang <at> db.debian.org
        | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44

Mario Lang | 6 Oct 22:34 2003
Picon

Re: gnome and debian + gnopernicus

Attila Konietzka <attilakonietzka <at> gmx.net> writes:

> On Mon, Oct 06, 2003 at 07:45:46PM +0200, Mario Lang wrote:
>> Attila Konietzka <attilakonietzka <at> gmx.net> writes:
>> 
>
>> > # apt-get install gnome-core gnopernicus,
>> >
>> > but still it isn't enough, i get errors like this:
>> > gtk+-warning: can't open display.
>> 
>> When do you get this error message?  It sort of looks to me as if you
>> were trying to start gnopernicus from the normal (console) command line?
>> You need to start up GNOME, before you will be able to use the Gnopernicus
>> screen reader.  This also involves configuring a working X Windows System.
>
> Well now i got x windows up and running and it seems to me that with alt+f7
> i change to the gdm-provided screen, but naturally i have no control after
> start until i press alt+ctrl+f1 for example, than i can login and type:
> # gnopernicus
> and still there are the same errors, allthough gdm is running in the
> background, and every time i switch to alt+f7 i hear my monitor clicking so it
> seems to me that whatever is running there is changing colors and
> resolutions and brightness somehow .

From your description it seems you did not set the $DISPLAY variable
correctly.  Normal consoles do not have the DISPLAY variable set, since
they are not opened from within X Windows.  You should probably
try and do something like:
# export DISPLAY=:0.0
(Continue reading)

Mario Lang | 7 Oct 13:38 2003
Picon

Re: gnome and debian + gnopernicus

Attila Konietzka <attilakonietzka <at> gmx.net> writes:

> On Mon, Oct 06, 2003 at 10:34:08PM +0200, Mario Lang wrote:
>> From your description it seems you did not set the $DISPLAY variable
>> correctly.  Normal consoles do not have the DISPLAY variable set, since
>> they are not opened from within X Windows.  You should probably
>> try and do something like:
>> # export DISPLAY=:0.0
>> # gnopernicus
>
> Well i did what you told but still the same errors including also:
> xlib: no protocol specified

Could you please post the complete output you get when launching Gnopernicus?
It is rather hard to figure out what is going on by just seeing a single
error message without any context.

> and other such messages. Is there anything i can do with the alt+f7 console?
> maybe logging in blind and then do something via alt+fa? or is the
> gnome-desktop not loaded at this moment?

You should check that the default window manager is set to metacity.
You can check this by executing
# update-alternatives --display x-window-manager
If it does not say something like
"Current `best' version is /usr/bin/metacity."
you can do something like
# update-alternatives --config x-window-manager
and select metacity.

(Continue reading)

Mario Lang | 10 Oct 01:38 2003
Picon

Bug#215039: at-spi: Gnopernicus >0.3.4 segfaults on window-switch event

Package: at-spi
Version: 1.1.9-1
Severity: important

I am unable to upload any newer version than Gnopernicus 0.3.4 to
the archives (0.7.1 is current), since every later version I tried
segfaults with the same backtrace.  According to the backtrace, it seems
to be an at-spi problem.  I have already reported this problem to
the g-a-devel mailing list, but no one was able to identify responsible code.
However, people seem to have no problem using later Gnopernicus versions on
other systems than Debian.

When starting gnopernicus, I see this:
# gnopernicus
GTK Accessibility Module initialized
Bonobo accessibility support initialized

**********************
* SCREEN READER CORE *
**********************

Bonobo accessibility support initialized
GTK Accessibility Module initialized
BrlAPI detected a 40x1 display

** BRAILLE initialization succeded for BRLTTY device on port 1.
   To see something you must have a Braille device connected to your computer.
   To change one or more settings use gnopernicus UI.

(srcore:614): gnopernicus-WARNING **: Callbacks are NOT supported by "V0 Kevin - Festival GNOME Speech
(Continue reading)

Mario Lang | 12 Oct 00:09 2003
Picon

Precompiled 2.4.22-speakup packages


Hi.

Since there has been no real progress on the speakup front recently, I
decided to do an update of the kernel-image-speakup-i386 packages.

Find a preliminary version of the upcoming 2.4.22-speakup kernel packages
at http://people.debian.org/~mlang/speakup-2.4.22/

Please let me now about any positive or negative test results.
At least with my DoubleTalk LT, it seems to work fine.

--

-- 
CYa,
  Mario | Debian Developer <URL:http://debian.org/>
        | Get my public key via finger mlang <at> db.debian.org
        | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
Mike Mattice | 12 Oct 21:52 2003

Re: Precompiled 2.4.22-speakup packages

On Sun, Oct 12, 2003 at 12:09:23AM +0200, Mario Lang wrote:
> Since there has been no real progress on the speakup front recently, I
> decided to do an update of the kernel-image-speakup-i386 packages.
> 
> Find a preliminary version of the upcoming 2.4.22-speakup kernel packages
> at http://people.debian.org/~mlang/speakup-2.4.22/

What version of speakup did you end up using with this?  Also, where's the
kernel-source package and the patch you're using?

Thanks,
Mike

--

-- 
Mike Mattice - Debian Developer
mailto: mike plus ldo at milliways dot cx mattice plus ldo at debian dot org
1024D/137A955E print 050C 2D2F A95A 25BB B61F  CD16 EC3B CAC4 137A 955E

Mario Lang | 13 Oct 01:12 2003
Picon

Re: Precompiled 2.4.22-speakup packages

mike <at> milliways.cx (Mike Mattice) writes:

> On Sun, Oct 12, 2003 at 12:09:23AM +0200, Mario Lang wrote:
>> Since there has been no real progress on the speakup front recently, I
>> decided to do an update of the kernel-image-speakup-i386 packages.
>> 
>> Find a preliminary version of the upcoming 2.4.22-speakup kernel packages
>> at http://people.debian.org/~mlang/speakup-2.4.22/
>
> What version of speakup did you end up using with this?

The version of the packages currently at the URL I posted is compiled
with the kernel-patch-speakup package version 20021221 (effectively
speakup-1.5).  However, since then I updated the kernel-patch package
to current speakup CVS, since the differences between 1.5 and current CVS
are really quite significant.  Especially the fact that in current CVS, there
are no keymap modifications via loadkeys necessary.  This should make
proper interaction with various user-space situations more robust.
I am currently testing the speakup cvs (version 2.0) patched kernel, and
will upload the new stuff to same the location including source packages soon.

--

-- 
CYa,
  Mario | Debian Developer <URL:http://debian.org/>
        | Get my public key via finger mlang <at> db.debian.org
        | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44

Nath | 16 Oct 10:23 2003
Picon

Gnome 2 + Gnopernicus + Gnome-speech

Hello,

An advice please :

can you tell me what is the best approach today to install gnome 2 from
debian packages with Gnopernicus 0.7.1 and Gnome-speech 0.2.7 ? 
Is it really possible or may we absolutely build Gnome 2 from scratch ? 
I ask because it seems the newest Gnopernicus release is not packaged
for debian and the last time I tried there was a problem with ATK (the
version packaged for debian was too old). 
So, please, let me know if things are better now ?
Thanx in advance,

--

-- 
Nath


Gmane