braille doesn't work at all under Ubuntu 8.04.1
Hi, First of all I ignore if the problem comes from brltty only, or from brltty + Ubuntu; anyway I posted this mail to both, Dave and Luke from the respective accessibility lists (in BCC). The facts now: brltty 3.9.6 seems not to get started on the Ubuntu Hardy O S I freshly installed yesterday (together with a sighted person) on a laptop: A) it doesn't autodetects my Alva Satellite 544, that's a big problem and IMHO an important *regression*, sorry : it auto was causing some problems, the serial-usb now causes 100% of problems, what IMHO cannot be seen as a progress in a11y! B) it also points now for configuring the display **each time I boot up** my system: that annoying situation forces me to press (blindly) X or to try U (usb) but in both cases **there's no braille started**, even when I hear the Ubuntu tune. BTW on screen it seems to tell that brltty is already configured: well it is! but it doesn't fit my display's spex so it won't work, while Ubuntu Gutsy did, except for an apropriate braille table (but that's another discussion for later...) What now ? what can I do except reinstalling a Gutsy and updating then to Hardy ? Btw I can't login through ssh to my lap, probably because I wasn't able to add (blindly) the ssh and openssh-server packages (also a point of discussion IMHO) I'm really becoming depressed when I see such things: problems are becoming bigger and complicated while the previous version should have worked if the bug in it had been fixed, simply and efficiently. Now nothing workx, not even if I enter USB: in the brltty.conf Sorry if it's not always in my best English, I did my best to explain a permanent problem of a bugged brltty or bugged Ubuntu install session, since Feisty, now more than 1 year ago; I wish one will fix this for now and forever if possible. Aldo. -- https://bugs.launchpad.net/ubuntu/+bug/1 : Micro$oft has a majority market share in the new desktop PC marketplace. This is a bug, which Ubuntu is designed to fix ! http://www.ubuntu.com/ -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: braille doesn't work at all under Ubuntu 8.04.1
Dear master and all users and developers, I would like to suggest You constructive approach to solve all accessibility issues related to support for Orca and braille display. Firstly, I think, that core developers of Ubuntu could make new desktop link for starting Orca with brltty. I Am unfortunately not experienced Gnome user, but may be, that adding sudo brltty and followed with line orca could solve problems with automatic braille displays detection. I tried to type gnome-terminal followed by Enter I typed sudo brltty, and my USB connected Tieman braille voyager has been successfully detected, initialized, and Brltty displayed correctly its message screen is not in A text mode. So if Your model will not be automatically detected, may be, that You could try to study command line parameters for Brltty to enable Your specific model of braille display. And please, do not forget to type sudo brltty followed by A specific parameters. You also mentioned about issue, that Orca can not automatically use A correct braille table for selected language. If You meaned by this, that Orca should automatically select right braille table according to The language, which user selected in The boot menu, there is difficulty related to Brltty, not to The Orca Screen reader. Eventhough Programmers fortunately are having procedure for detecting, which language has been selected and they can automatically select specific Espeak person for A specific language, automatically select braille table is not so simply, as some users could think. If user want to use A specific braille table for A specific language, user must modifi The file brltty.conf, which is located in The etc Directory. So open /etc/brltty.conf And try to analyze this file for Your wanted language. The language can begin with # Character. To enable support for A specific language, remove The # character at The beginning of A line, which is assigning The specific language. Please, try to study manual for Brltty or try to directly communicate with developer of Brltty latest version about those changes or if Your language is not awailable. I Am aware, that modifiing this file is only possible, when Ubuntu Hardy Heron or newest Ubuntu live CD version is allready installed on A hard drive. My opinion is, that every think depends on The fact, how many languages are predefined and are awailable in The /etc/brltty.conf file. Please, I would like to please all users of Ubuntu to be more patient, core developers of Ubuntu are doing their best and during next week, problems related to accessibility will be solved. Even problem with Brltty could be I think solved without many problems. If is it possible to type sudo brltty Orca to The Gnome desktop link for starting Orca. In The Ubuntu Feisty and gutsi, Brltty has been started during booting up, much sooner than Gnome has been started. So I think, that brltty has been started with Linux kernel probably. So I Am very sorry, that I can not help You more. The kindness regards. Janusz Chmiel -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: braille doesn't work at all under Ubuntu 8.04.1
Hi, On Wed, Sep 03, 2008 at 10:59:00PM +0200, Mgr. Janusz Chmiel wrote: I would like to suggest You constructive approach to solve all accessibility issues related to support for Orca and braille display. I'm only reporting facts which make me victime of them: I'm a visually impaired user. Firstly, I think, that core developers of Ubuntu could make new desktop link for starting Orca with brltty. I Am unfortunately not experienced Gnome user, but may be, that adding sudo brltty and followed with line orca could solve problems with automatic braille displays detection. Sorry but the problem I encountered was only brltty and Ubuntu related, not Orca-related; let me explain: - I resolved now the problem by providing the right line into brltty.conf: braille-device usb: But initially, Ubuntu provided a line as serial:ttyUSB:/ttyUSB: or so who is a total nonsense; and then when I tried USB: with capital letters, it still didn't worked while it had to do so... Now I provided usb: in lowercas, spontaneously it works. That's not normal - now it is corrected, I have braille as well under console as under Orca, so that's why I say this is not an Orca + brltty related problem, but only an Ubuntu + brltty problem - last but least, even if I replaces the word auto by al for my Alva braille-display, Ubuntu still continues to ask for which display it is at any reboot time: this is an Ubuntu issue and an annoying bug, especially if you are blind and can't see what hes's asking for on screen (no brailel at that moment). I tried to type gnome-terminal followed by Enter I typed sudo brltty, and my USB connected Tieman braille voyager has been successfully detected, initialized, and Brltty displayed correctly its message screen is not in A text mode. Well, under Gutsy I also had braille, with no need to type anything; the problem is coming up now after installing Hardy from the last iso image. So if Your model will not be automatically detected, may be, that You could try to study command line parameters for Brltty to enable Your specific model of braille display. No, the model is al, I tried -b al and tried then -d usb: in lowercase, and then I discovered what the bug was: USB: will not work, usb: will. And please, do not forget to type sudo brltty followed by A specific parameters. I did first a sudo su so I was permanently root. You also mentioned about issue, that Orca can not automatically use A correct braille table for selected language. If You meaned by this, that Orca should automatically select right braille table according to The language, which user selected in The boot menu, there is difficulty related to Brltty, not to The Orca Screen reader. You're right, this is brltty-related: it is brltty who must autodetect braille dispaly, and usb or so port, and forcing a certain brailel table depending on the locale installed for the first Ubuntu account, that would be logical. BTW yesterday I discovered that Orca started in Dutch and that was the language we choosed here for our installation; so I was wondered to see this progress; this is logical but isn't currently for brltty, while I have nothing to do with the us table. Eventhough Programmers fortunately are having procedure for detecting, which language has been selected and they can automatically select specific Espeak person for A specific language, automatically select braille table is not so simply, as some users could think. OK but for Orca+eSpeak it seems a workarfound have been done, or is it a miracle that my Dutch Ubuntu was talking in Dutch too? If user want to use A specific braille table for A specific language, user must modifi The file brltty.conf, which is located in The etc Directory. Well that's not logical: if someone choosed fr_FR for his installation, there exist a fr_FR table for brltty, so it would be logical to match the brltty table with the locale. So open /etc/brltty.conf And try to analyze this file for Your wanted language. The language can begin with # Character. To enable support for A specific language, remove The # character at The beginning of A line, which is assigning The specific language. Please, try to study manual for Brltty or try to directly communicate with developer of Brltty latest version about those changes or if Your language is not awailable. I mean the translation table or text-table: here in the North of Belgium we do use the de tbl, whle at Brussels and the french part of Belgium they prefer the fr tbl; well in fact that's absolutely not a problem: if the locale is fr_BE then brltty must be default set to fr_FR tbl, while if the locale is nl_BE then brltty shall be set for the de tbl. I suppose there is a similar choice in other countries, so applying the technik of following the default locale may definitely resolve this problem for all non-us countries. I Am aware, that modifiing this file is only possible, when
