Lucid and brltty v. 4.1 - bug in brltty.conf
Hi, as long as I kept Serial: as param for the braille-device in the Ubuntu Lucid brltty.conf instead of /dev/ttyS0, my Alva ABT380 wasn't starting, even if the RUN_BRLTTY=yes in /etc/default/brltty. Why not fixing such a bad bug definitely, or explaining why puting Serial: as default (probably wrong) param ? Labrador -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: karmic problem is somewhat fixed
Hi, I'm asking myself what to do and how to do so that that big ch... of Pulse should be removed and replaced again by ALSA in future distros ? why did they changed something who worked nicely by something who make from the Linux system soething unusable regarding sound/audio ? Can they imagine what this should make as impression by ex Windows users ? On Debian it's still ALSA in the stable one and that is working very nicely, also the author of Vinux (now also Debian based) had to do the same, removing Pulse and installing ALSA; so let's remove the ch... definitely, isn't it ? what to do, where to post and who's responsible for Pulse ? Who decided that it was good enough to be imposed while it's so bad ? Labrador On Mon, Nov 02, 2009 at 10:28:42AM -0600, mike wrote: Hi, removing pulse audio did seem to make things a little better. I ran spd-conf and set up a new config. All at the moment works except for two things. 1, no volume control. 2, in movie player Orca crashes if I search for something on u tube and try to play it. But this has been a problem for some time. Mike. -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility -- Dig that crazy beat on the drums: VINUX !!! The best is getting better! --http://vinux.org.uk-- -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Compiling Compiz from source
On Sat, Jul 04, 2009 at 10:22:17AM -0400, Bill Cox wrote: Sorry for this newbie package question. I am trying to track down some Comiz issues on Ubuntu 9.04 x64 in communicating with Orca. Compiz is a problem for Orca and it can be simply resolved by removing all compiz-related packages already installed on Ubuntu, doing this will stop with making crash or block Orca at boot time, by me it was stopping with talking at the welcome message (intrepid distro), after I removed all compiz packs I can boot my system and it talks and works again; idem I did the same on the pc of my wife with the same effect. So as blind you don't need compiz, and the best thing to do is removing it asap. Labrador -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
new (fresh) reinstall test for brltty at Ubuntu (confirm: problem in Ubuntu not in brltty)
Hi Dave, hi everybody, sorry for my long absence and silence since a few days ago, I don't forgot you, I simply have been busy. Even if I wrote all your mails, I tried today to REinstall a fresh Ubuntu 8.04.1 distro (desktop version) on my Asus laptop. These are the new results of my experience: How do I proceeded ? - the CD starts up and points me for the desired language; at that point I do 1x right.arr and 5x down.arr for Dutch, enter - with F3 and in this case 4x left.arr I choose for Belgian keyboard, enter (1st BUG observed, see below) - now I switch to F5 + 4x down.arr for selecting braille, enter - and F6 where I enter: brltty=al,usb:,de then I press enter: Ubuntu live starts up and I got braille with the right table at the end of that process, except (bug nr2) that it asked for re-entering the model and device before he REALLY started-up. Now I didn't found the Install button, so my partner started the real installer using the mouse; in fact at that moment Orca is completely blind and can't follow: no braille no voice (bug nr3). After finishing installation, Ubuntu was rebooted and I got *no braille* (bug nr4, see below): I will attach here the reasons (/the right files) so everybody can see that there is a real BIG problem in Ubuntu Hardy. Finally, I encountered again the braille=ask bug in Grub's menu.lst (bug nr5). How did I fixed that ? - first by opening blindly a console, running a killall brltty, then restarting brltty with -b al -d usb: -t de to check if it worked, and he did! - then I edited /boot/grub/menu.lst to suppress that absurd / uncomprehensive and totally blindUNfriendly braille=ask - and finally I edited /etc/brltty.conf to correct the device line who was *and still is* completely wrong and unusable, see attached file. - I also checked if /etc/default/brltty was OK, and it said Yes so that is OK. Bugs: 1: you may do and redo your kbd selection, each time you leave F3 then press F3 again, it resets itself to US keyboard. 2: why asking for brl type and dev since you already choosed it in F5 and entered by the way your params in F6 ? 3: no braille nor speech during installation even when having braille in the started live CD... 4: no braille due to a wrongly edited /etc/brltty.conf file by Ubuntu itself, cf. attach, and read please the line above, its clearly mentionned what/who did that... + brltty.conf.orig is already present and is the template but Ubuntu doesn't touched that template, it only dropped a 2 à 3 lines wrong config-file instead... 5: braille=ask in menu.lst causes a major problem when rebooting the system blindly; I attached that menu.lst file created by Ubntu itself. Fixing now! Is someone here familiar enough with Launchpad and other Bugzilla services to help with reporting the problems to the right person at the right place: five bugs are more than enough IMHO to urge for fixing it and asking for adding the fixes in the next LTS 8.04.2 CD. Grtnx, and once again sorry for delay. Osvaldo La Rosa. # Created by /lib/brltty/brltty.sh braille-driver al braille-device usb: text-table de # corrected by me # Created by /lib/brltty/brltty.sh braille-driver al braille-device serial:ttyUSBusb: # built by Ubuntu itself ... and completely wrong # This is a configuration file template for the BRLTTY application. # Uncomment those entries which apply to your personal needs and system # requirements. # BRLTTY expects to find its configuration file in /etc/brltty.conf # (can be overridden with the -f [--configuration-file=] option). # If it doesn't exist, then BRLTTY silently continues but may require # that certain command line options be explicitly supplied. # Blank lines are ignored. The character '#', anywhere on a line, # initiates a comment; all characters from it to the end of that line # are ignored. # Each configuration entry consists of a keyword followed by its operand. # An arbitrary amount of white space, (blanks and/or tabs), may occur # before the keyword, as well as before and after the operand. Keyword # processing is not case sensitive. Examples of valid entries are: # # Braille-Driver pm # Papenmeier braille displays. # braille-device serial: # The first serial device. # SPEECH-DRIVER fv # The Festival Text to Speech System. # The default settings given within the following descriptions assume no # special build options (see ./configure --help in the top-level # directory of the source tree. # Generic Braille Settings # # The braille-driver directive specifies the two-letter driver # identification code of the driver for the braille display. # If not specified, autodetection will be performed. # (can be overridden with the -b [--braille-driver=] option) #braille-driver auto# autodetect #braille-driver al # Alva #braille-driver at # Albatross #braille-driver ba # BrlAPI
[Fwd:Re: [orca-list] brltty, ubuntu and orca]
- Forwarded message from Labrador labrad0r edpnet be - From: Labrador Date: Sun, 7 Sep 2008 12:42:33 +0200 Subject: Re: [orca-list] brltty, ubuntu and orca User-Agent: Mutt/1.5.9i Hi Cheryl, On Sat, Sep 06, 2008 at 04:57:10PM -0500, Cheryl Homiak wrote: Is there a way to start brltty automatically when starting orca in ubuntu? On my debin box, I have brltty starting at bootup; it works in the consoles and once I start orca it also works there. But in ubuntu I don't see how to start brltty at bootup; I've resorted to starting brltty with sudo in a console and then logging in to orca. Refering to a current discuttion at the BrlTty ML, it seems there is a MEGA / GIGA BUG IN UBUNTU's 8.04.1 CD: when even you select Orca to startup with the session, you WON'T have braille through BrlTty AS LONG AS THAT PROBLEM ISN'T FIXED. Until now I wrote to Luke Yelavicz and also to the Ubuntu-Accessibility list and as answer I get NO ANSWER until now. So maybe all unhappy people should post and repost their claims to that list or someone from that team should do the effort to clear-up the situation ??? The problem is probably the /lib/brltty/brltty.sh script: this is doing abnormal things, and that script was also causing problems in the previous distro (Gutsy). BTW, try to remove completely brltty + brltty-x11 from Ubuntu Hardy: it STILL CONTINUES TO ASK ABOUT WHAT KIND OF DISPLAY AND if it is an U)sb or Bluetooth or S)erial; pressing eX)it will proceed with continuing to boot-up, but at each boot you will be stolked by that infernal question while we can't see anything at that moment. So: ther is NO problems with Orca nor Gnome, No problem with BrlTty itself, there is only a GREAT GREAT and urgent to fix proble min Ubuntu's brltty.sh script, and probably more ... (open /etc/brltty.Conf and see the syntax used, it is TOTALLY UNUSABLE). So I insist: post to Ubuntu-Accessibility, and I will do so until I obtain any answer about how to fix that problem. Aldo. - End forwarded message - -- 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
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
persistent brltty question at boot time while brltty already configured
Hi, I just resolved a problem that happened during the installation of Ubuntu Hardy from a fresh 8.04.1 CD: the brltty.conf wasn't correct: the USB Alva SAtellite I use was not detected. Finally after discussing this point at the Brltty list, it seems that we must enter usb: without capital letters nor quotes in the /etc/brltty.conf file. Now it workx again, but Ubuntu is persistently asking at eacht boot time for which kind of display I'm using, and pointing me for answering S for serial, U for USB, B for Bluetooth or X for exit. I'd like to resolve asap this stupid problem, since my display is finally detected and started as needed: how does I remove that persistent question screen ? it's very not blind friendly because at that moment you can't ready anything. BTW it would be nie to fix definitely all brltty related problems present in the Ubuntu installer or at boot time, this is an inferno and I still encountered problems with Gutsy. I encourage you, fix them all definitely! many thanx Aldo. -- 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
Re: OCR
Hi, regarding conversion...: On Tue, May 22, 2007 at 09:24:59AM -0400, Jason Grieves wrote: The OCR software actually integrates nicely with XSANE. I was able to get a txt file very quickly with my Epson scanner. I did not see a way to convert it into a pdf or open document with the text already converted. Try convert (from the imagemagick package): convert something.tiff to.pdf or if the goals is different, try using TeX/LaTeX (cf. texlive or tetex package) to create a .tex document you can later convert into ps, pdf or other... L:~$ -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
installing Ubuntu with X and no assistance
Hi, I'm new to this forum. A few months ago a sighted friend helped me with installing on his demo-pc some Ubuntu distribution with Gnopernicus. But should there be a way to do the same without any assistance ? Does the latest Ubuntu Edgy Eft come with Orca ? Or only Gnopernicus ? Any suggestions welcome. Thanks. Greetings, Labrador -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
