Re: Orca Brltty and Ubuntu 18.04
Well, I made /etc/brlapi.key world readable. It is not the most secure solution but it works. Vojta Dne 18. 10. 18 v 12:14 Anders Holmberg napsal(a): > Hi! > Try to put the brlapi.key in your home folder. > See if that works. > /A > >> 17 okt. 2018 kl. 20:25 skrev Vojtěch Polášek : >> >> Hi guys, >> >> is there anything special I need to do for Orca to work with braille >> displays in Ubuntu 18.04? >> >> To be more exact, I am using Accessible Coconut 18.04.4. >> >> Brltty works, for example braille in virtual text console works. But >> Orca does not display anything in braille even if braille support is >> enabled. >> >> My braille display shows only "screen not in text mode". >> >> I guess there is some trick with /etc/brlapi.cookie or something like >> that, but I am not sure. Any tips? >> >> Thanks, >> >> Vojta >> >> >> -- >> Ubuntu-accessibility mailing list >> Ubuntu-accessibility@lists.ubuntu.com >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Orca Brltty and Ubuntu 18.04
Hi guys, is there anything special I need to do for Orca to work with braille displays in Ubuntu 18.04? To be more exact, I am using Accessible Coconut 18.04.4. Brltty works, for example braille in virtual text console works. But Orca does not display anything in braille even if braille support is enabled. My braille display shows only "screen not in text mode". I guess there is some trick with /etc/brlapi.cookie or something like that, but I am not sure. Any tips? Thanks, Vojta -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Brltty 5.4 backported to Xenial.
I just upgraded to brltty 5.4 from the ppa and am still seeing problems. The system does not want to recognize my usb-to-serial and there is more than one copy of brltty running. Results of "ps -aux | grep brltty": root 2682 0.1 0.2 399444 9616 ?D Hi all. As some of you are experiencing problems with BrlTTY, I decided to go ahead and backport 5.4 from yakkety to xenial. As per usual, these packages are available from the Ubuntu Accessibility dev PPA, https://launchpad.net/~accessibility-dev/+archive/ppa. BrlTTy will be built and available shortly. Luke -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Brltty 5.4 backported to Xenial.
Hi all. As some of you are experiencing problems with BrlTTY, I decided to go ahead and backport 5.4 from yakkety to xenial. As per usual, these packages are available from the Ubuntu Accessibility dev PPA, https://launchpad.net/~accessibility-dev/+archive/ppa. BrlTTy will be built and available shortly. Luke -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
brltty
hi. i installed Ubuntu 16.04 a few weeks ago. I have some problems with braile. it starts but I can't use the buttons on the display to move farther in a line longer than the display. is there any fix for this? regards Oskar. -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Brltty question
I seem to have two copies of brltty running. From ps -aux command I get: root 3050 0.2 0.1 333892 7188 ?DThis seems to be causing great confusion for the OS and causing problems with my usb ports. If I try to kill the one with the -n -p options it gets restarted. Can anyone tell me why this is happening and what I can do about it? Tom -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Possible problem with brltty
I am running Ubuntu 16.04 using brltty with a Varioulta 40 cell display. I have 4 consoles open and of course the desktop (I prefer working at the console to using terminals). I see the following in my syslog which appears to be causing issues with using a usb-to-serial converter among other things. Can anyone tell me what is causing these messages and what the solution is? Aug 23 11:51:10 Tom-M2800 brltty[8283]: USB configuration set error 16: Device or resource busy. Aug 23 11:51:10 Tom-M2800 kernel: [ 1601.748128] usb 3-6: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 Aug 23 11:51:10 Tom-M2800 brltty[8283]: USB interface in use: 0 (usbfs) Aug 23 11:51:10 Tom-M2800 brltty[8283]: possible cause: another brltty process may be accessing the same device Aug 23 11:51:10 Tom-M2800 brltty[8283]: USB interface claim error 16: Device or resource busy. Aug 23 11:51:15 Tom-M2800 brltty[8283]: USB configuration set error 16: Device or resource busy. Aug 23 11:51:15 Tom-M2800 kernel: [ 1606.796074] usb 3-6: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 Aug 23 11:51:15 Tom-M2800 brltty[8283]: USB interface in use: 0 (usbfs) Aug 23 11:51:15 Tom-M2800 brltty[8283]: possible cause: another brltty process may be accessing the same device Aug 23 11:51:15 Tom-M2800 brltty[8283]: USB interface claim error 16: Device or resource busy. Aug 23 11:51:20 Tom-M2800 brltty[8283]: USB configuration set error 16: Device or resource busy. Aug 23 11:51:20 Tom-M2800 brltty[8283]: USB interface in use: 0 (usbfs) Aug 23 11:51:20 Tom-M2800 brltty[8283]: possible cause: another brltty process may be accessing the same device Aug 23 11:51:20 Tom-M2800 brltty[8283]: USB interface claim error 16: Device or resource busy. Aug 23 11:51:20 Tom-M2800 kernel: [ 1611.793902] usb 3-6: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 Aug 23 11:51:25 Tom-M2800 brltty[8283]: USB configuration set error 16: Device or resource busy. Aug 23 11:51:25 Tom-M2800 brltty[8283]: USB interface in use: 0 (usbfs) Aug 23 11:51:25 Tom-M2800 brltty[8283]: possible cause: another brltty process may be accessing the same device Aug 23 11:51:25 Tom-M2800 brltty[8283]: USB interface claim error 16: Device or resource busy. Aug 23 11:51:25 Tom-M2800 kernel: [ 1616.797770] usb 3-6: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 Aug 23 11:51:30 Tom-M2800 brltty[8283]: USB configuration set error 16: Device or resource busy. Aug 23 11:51:30 Tom-M2800 brltty[8283]: USB interface in use: 0 (usbfs) Aug 23 11:51:30 Tom-M2800 brltty[8283]: possible cause: another brltty process may be accessing the same device Aug 23 11:51:30 Tom-M2800 brltty[8283]: USB interface claim error 16: Device or resource busy. Aug 23 11:51:30 Tom-M2800 kernel: [ 1621.796714] usb 3-6: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 Aug 23 11:51:35 Tom-M2800 brltty[8283]: USB configuration set error 16: Device or resource busy. Aug 23 11:51:35 Tom-M2800 kernel: [ 1626.791619] usb 3-6: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 Aug 23 11:51:35 Tom-M2800 brltty[8283]: USB interface in use: 0 (usbfs) Aug 23 11:51:35 Tom-M2800 brltty[8283]: possible cause: another brltty process may be accessing the same device Aug 23 11:51:35 Tom-M2800 brltty[8283]: USB interface claim error 16: Device or resource busy. Aug 23 11:51:40 Tom-M2800 brltty[8283]: USB configuration set error 16: Device or resource busy. Aug 23 11:51:40 Tom-M2800 brltty[8283]: USB interface in use: 0 (usbfs) Aug 23 11:51:40 Tom-M2800 brltty[8283]: possible cause: another brltty process may be accessing the same device Aug 23 11:51:40 Tom-M2800 brltty[8283]: USB interface claim error 16: Device or resource busy. Aug 23 11:51:40 Tom-M2800 kernel: [ 1631.792459] usb 3-6: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 Aug 23 11:51:45 Tom-M2800 brltty[8283]: USB configuration set error 16: Device or resource busy. Aug 23 11:51:45 Tom-M2800 brltty[8283]: USB interface in use: 0 (usbfs) Aug 23 11:51:45 Tom-M2800 brltty[8283]: possible cause: another brltty process may be accessing the same device Aug 23 11:51:45 Tom-M2800 brltty[8283]: USB interface claim error 16: Device or resource busy. Aug 23 11:51:45 Tom-M2800 kernel: [ 1636.792486] usb 3-6: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 Aug 23 11:51:50 Tom-M2800 brltty[8283]: USB configuration set error 16: Device or resource busy. Aug 23 11:51:50 Tom-M2800 kernel: [ 1641.791259] usb 3-6: usbfs: interface 0 claimed by usbfs while 'brltty' sets config #1 Aug 23 11:51:50 Tom-M2800 brltty[8283]: USB interface in use: 0 (usbfs) Aug 23 11:51:50 Tom-M2800 brltty[8283]: possible cause: another brltty process may be accessing the same device Aug 23 11:51:50 Tom-M2800 brltty[8283]: USB interface claim error 16: Device or resource busy. Aug 23 11:51:55 Tom-M2800 brltty[8283]: USB configuration set error 16
Re: brltty
On Fri, 15 Jul 2016 21:48:02 +0200 mattias <mjonsson1...@gmail.com> wrote: > ubuntu arm version? > > are brltty compiled for it? > > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility The package is compiled for it according to packages.ubuntu.com http://packages.ubuntu.com/xenial/brltty -- Brendan Perrine <walteror...@gmail.com> -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
brltty
ubuntu arm version? are brltty compiled for it? -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Ubuntu 16.04 Braille users, please help test proposed BrlTTY update.
Hey folks. Further to the email I recently sent about a broken brlTTy package in Ubuntu 16.04, and the subsequent availability of a fixed package in the Ubuntu Accessibility dev PPA, I have submitted the fixed package as an update for 16.04. This fixed package is actually slightly better than what is in the PPA, because I discovered one small issue during testing when getting this update ready for submission. if you could please help test the update, feel free to go to https://bugs.launchpad.net/bugs/1574538 and read through the bug. The last post contains instructions on how to test the proposed update. Once you have tested, please make sure you reply to the bug and indicate whether the updated package works for you. Do not forget to disable the proposed repository on your system once you have finished testing. I will be testing myself, but the more testers that can verify the update the better. Thanks in advance. Luke -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
14.04, orca, brltty
Starting especially yesterday but off and on since I updated to 14.04 orca has stopped working with the braille display. I see nothing in any of the logs that gives a clue as to what is happening. When I get to the log in screen everything is working fine. When it goes to the desktop braille is no longer working. Sometimes a reboot of the machine does help. I am also noticing odd behavior at the console where occasionally my display cursor movement keys do not work or all of a sudden it will decide to just run everything to the bottom of the screen like I was holding down the down key on the display. The only way I have found to resolve these issues is to disconnect and reconnect the display and/or restart brltty. My display is an Alve BC640. Tom -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: BRLTTY does not start automatically since upgrade of my system
Hi all, Since my last mail i've tried several things to get my braille display starting automatically again. First i thought that brltty might not start automatically. So i added it to my /etc/rc.local After rebooting i issued the command ps -A | grep -i .*brltty to see if it is running. To my suprise it was even running twice :-) So i removed it from the rc.local again. IN the next step i tried removing and reinstalling the package. When i started aptitude remove brltty it complained about brltty-x11 is broken. After confirming it removed the packages (brltty and brltty-x11). Now i installed brltty and brltty-x11 again. But unfortunatelly without any success.. Currently i have installed brltty 4.1. Would it make sense to install a newer version of it? And how could i get it? I'd prefer to use no testing repositories or something like this bc i use my ubuntu on a daily basis ... Any help / new ideas would be appreciated! Best wishes Marion Am 28.01.2011 14:42, schrieb Marion Peterreins: Hi all, Since I've upgraded my system brltty does not start automatically. What can I do to make it start automatically again? Ubuntu 10.4 Orca 2.30.2 Thanks in advance, Marion! -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
BRLTTY does not start automatically since upgrade of my system
Hi all, Since I've upgraded my system brltty does not start automatically. What can I do to make it start automatically again? Ubuntu 10.4 Orca 2.30.2 Thanks in advance, Marion! -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Brltty?
Can i install ubuntu 10.04 with brltty like in 8.10 and 8.04 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
brltty
Are brltty included in the alternate cd yet I meen 10.04 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
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
Installing Intrepid with BRLTTY
Hi all, I am not able to boot the live CD so I downloaded the alternate CD. When I booted the CD I first press enter. Then I press F6 after I type: install brltty=ts,ttyS0,de Isn't this correct? Nothing seems to happen. Many thanks, Christian -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
SV: Installing Intrepid with BRLTTY
If you have a voyager you only need to enter brltty If i remember right -Ursprungligt meddelande- Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] För Christian Skickat: den 20 november 2008 20:59 Till: ubuntu-accessibility@lists.ubuntu.com Ämne: Installing Intrepid with BRLTTY Hi all, I am not able to boot the live CD so I downloaded the alternate CD. When I booted the CD I first press enter. Then I press F6 after I type: install brltty=ts,ttyS0,de Isn't this correct? Nothing seems to happen. Many thanks, Christian -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Cannot install Intrepid with BRLTTY
Hi all, When I launch BRLTTY I get the scren not in text mode message when I type: install brltty=ts,ttyS0 after pressing F6 after I have booted the CD and pressed enter. Is this broken? Many thanks, Christian -- 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 #braille
[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
Re: persistent brltty question at boot time while brltty already configured
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Sep 04, 2008 at 07:09:30AM EST, Labrador wrote: 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. Somehow, the command-line arguments passed to the kernel at boot has had braille=ask added. To immediately solve this problem, I suggest you open the file /boot/grub/menu.lst as root, and search for braille-ask, and delete it. Do not delete the entire line, just delete that part of the line. Then as root, run the command update-grub. This should stop the constant prompting at boot. I would also like to know what CD you used to install Ubuntu, so I can attempt to track down that problem, and make sure it is fixed for future Ubuntu releases. Hope this helps. Luke -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIxHbHjVefwtBjIM4RAqNLAJwIrpolmGSSIz7LK7Mkf19l+Wzf5QCg2v6h b6oEBU/I9ZOMwfTxAGC8snY= =oDxr -END PGP SIGNATURE- -- 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
brltty autostart
Greetings, I have recently been working at getting my braillenote set up as a braille display with Ubuntu (7.10 gutsy). I have the brltty checkbox marked in the services manager (located under the administration menu item on the top bar). But brltty doesn't seam to be starting correctly. A: when the computer gets to the login prompt, instead of the drum-beat, the computer beeps (sounds like the system beep; ASCII character 7). b: to initiate brltty I still have to login as administrator and run sudo brltty from the command prompt. Is there a way to get brltty to start automatically so I don't need to login as administrator and logout/login as non-administrator to use brltty under my non-administrator account? (I'm still aclimmating to linux/ubuntu and I like to do most of my work as non-administrator for my own protection.) It's not a major issue (the process does result in a working brltty), but it'd be just that much more convenient to login straight away under the account I'm going to use. thank you:-) _ Spell a grand slam in this game where word skill meets World Series. Get in the game. http://club.live.com/word_slugger.aspx?icid=word_slugger_wlhm_admod_april08 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[j.orcau...@gmail.com: Re: BrlTty defunct after upgrading Gutsy to Hardy]
Sorry, I replied to the wrong list. -Jon - Forwarded message from Jon [EMAIL PROTECTED] - Date: Tue, 29 Apr 2008 18:57:46 +0100 From: Jon [EMAIL PROTECTED] To: Y P [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: BrlTty defunct after upgrading Gutsy to Hardy Reply-To: Jon [EMAIL PROTECTED] Hi, in gutsy: When i tried to upgrade to brltty 3.9, brltty 3.7.2 didnt uninstall correctly, i had to undo the modifications to /etc/init.d/brltty before the package would uninstall. After this brltty 3.9 installed without any problems. Then a while later i decided to attempt to upgrade to hardy, modifying /etc/apt/sources.list and doing an upgrade all worked fine, except that orca didnt ever seem to talk to the braille display. Brltty is running, works in terminal mode, the python brlapi bindings where installed, but still no braille and orca. I did a update/upgrade cycle every few days, but nothing happend in this regard. With all the debate about speech output options, and the various hacks that needs doing, its currently on a todo-list for a reinstall of good old gutsy. So our experiences seem to have coincided. rest of reply in-body: On Tue 29/04/2008 at 19:23:52, Y P wrote: Hi, I've upgraded a laptop from Gutsy to Hardy using this method: sudo aptitude update sudo aptitude full-upgrade to first full upgrade Gutsy. Then: sudo aptitude install update-manager-core sudo do-release-upgrade For brltty it proposed me to keep the current one, idem for the brltty.conf, that's the standard action; I ignore what to do so I simply pressed ENTER. The current brltty seems to be 3.9, so in fact it has upgraded it anyway. Why answering then things if it upgrades anyway? Jon: its because it recognized that there is a difference between your brltty.conf and the one that comes with the package, so it asked if you wanted to keep your own one, which is configured with your preferences. But now there is no any brltty when booting; and whe doing ps ax |grep -i brl ENTER for checking if it is started, I can't see any process started automatically. jon: what happens when you simply type brltty in a terminal? any output? And I still have the same brltty.conf as before with my de (german) table. Note: due to the bug in the Gutsy, at that moment I had recommented some raws to prevent some actions but I don't remember in which file it was and if that have caused tje problem now? jon: it did for me, but cant say for sure, in your case. Here are my conf files in attach. Y P -Jon - End forwarded message - -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: [j.orcau...@gmail.com: Re: BrlTty defunct after upgrading Gutsy to Hardy]
Hi, my problem seems to be solved: removing the three # in /etc/init.d/brltty and I had already copied brltty.conf.dpkg.dist over brltty.conf and begun again the config. Now it works here with the right table. Thanks a lot. PS: still not understand why dpkg -l |grep brltty shows a brltty package in iF so it is installed but F what's that ? Y P On Tue, Apr 29, 2008 at 07:23:45PM +0100, Jon wrote: Sorry, I replied to the wrong list. -Jon - Forwarded message from Jon [EMAIL PROTECTED] - Date: Tue, 29 Apr 2008 18:57:46 +0100 From: Jon [EMAIL PROTECTED] To: Y P [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: BrlTty defunct after upgrading Gutsy to Hardy Reply-To: Jon [EMAIL PROTECTED] Hi, in gutsy: When i tried to upgrade to brltty 3.9, brltty 3.7.2 didnt uninstall correctly, i had to undo the modifications to /etc/init.d/brltty before the package would uninstall. After this brltty 3.9 installed without any problems. Then a while later i decided to attempt to upgrade to hardy, modifying /etc/apt/sources.list and doing an upgrade all worked fine, except that orca didnt ever seem to talk to the braille display. Brltty is running, works in terminal mode, the python brlapi bindings where installed, but still no braille and orca. I did a update/upgrade cycle every few days, but nothing happend in this regard. With all the debate about speech output options, and the various hacks that needs doing, its currently on a todo-list for a reinstall of good old gutsy. So our experiences seem to have coincided. rest of reply in-body: On Tue 29/04/2008 at 19:23:52, Y P wrote: Hi, I've upgraded a laptop from Gutsy to Hardy using this method: sudo aptitude update sudo aptitude full-upgrade to first full upgrade Gutsy. Then: sudo aptitude install update-manager-core sudo do-release-upgrade For brltty it proposed me to keep the current one, idem for the brltty.conf, that's the standard action; I ignore what to do so I simply pressed ENTER. The current brltty seems to be 3.9, so in fact it has upgraded it anyway. Why answering then things if it upgrades anyway? Jon: its because it recognized that there is a difference between your brltty.conf and the one that comes with the package, so it asked if you wanted to keep your own one, which is configured with your preferences. But now there is no any brltty when booting; and whe doing ps ax |grep -i brl ENTER for checking if it is started, I can't see any process started automatically. jon: what happens when you simply type brltty in a terminal? any output? And I still have the same brltty.conf as before with my de (german) table. Note: due to the bug in the Gutsy, at that moment I had recommented some raws to prevent some actions but I don't remember in which file it was and if that have caused tje problem now? jon: it did for me, but cant say for sure, in your case. Here are my conf files in attach. Y P -Jon - End forwarded message - -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
BRLTTY problems
Hi all, Just wanted to try alpha6 of Ubuntu just to see if my hardware is working now. It didn't work that good with the 7.10 release. Isn't BRLTTY included on the alternate CD? I tried running install brltty=ts,ttyS0 but nothing happens. Many thanks, Christian -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re[2]: BRLTTY problems
Hi, I type that as soon as the cd boots up. On 2008-03-08 at 16:13 Samuel Thibault wrote: Christian, le Sat 08 Mar 2008 17:09:19 +0100, a écrit : Just wanted to try alpha6 of Ubuntu just to see if my hardware is working now. It didn't work that good with the 7.10 release. Isn't BRLTTY included on the alternate CD? Should be I tried running install brltty=ts,ttyS0 How do you type that? Samuel -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
BrlTTY package testing.
Hi, I tried to update brltty adding the line you said to /etc/apt/sources.list, but brltty 3.9 doesn't appear. With my browser, I went to http://ppa.launchpad.net/themuso/ubuntu/dists/gutsy/main/binary-i386/packages, but brltty doesn't appear there. What am I doing wrong? Best regards Sérgio Neves -- Original Message - From: Luke Yelavich [EMAIL PROTECTED] To: Orca screen reader developers [EMAIL PROTECTED]; Ubuntu Accessibility Mailing List ubuntu-accessibility@lists.ubuntu.com Sent: Friday, February 29, 2008 10:26 AM Subject: [orca-list] BrlTTY package testing. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all I am writing to request that all of you who have braille displays, particularly if your display is USB, test an updated BrlTTY package. I've fixed one or two issues in this package, and would like to get user testing before I put it into hardy. I've made it available for both gutsy and hardy, to get wider testing. Add one of the following lines to your /etc/apt/sources.list file to get the newer BrlTTY. gutsy: http://ppa.launchpad.net/themuso/ubuntu gutsy main hardy: http://ppa.launchpad.net/themuso/ubuntu hardy main One issue that I am pretty sure I have resolved, is the issue whereh the configuration file gets overwritten at every boot. Please in particular see if this issue is resolved for you. Please give this package a good test with your display, and let me know if you find any issues. This is the best time to get BrlTTY fixed up as well as is possible for Ubuntu hardy, and the more issues we can get fixed now, the better. Thanks in advance for your help. Luke -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHx93djVefwtBjIM4RAjhxAKC6CrPfc3EEFS1dv4FfhBmMdBXarwCfcVA7 TPDdeR3eDmdQ3U7c4zt15sk= =3u56 -END PGP SIGNATURE- ___ Orca-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
BrlTTY package testing.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all I am writing to request that all of you who have braille displays, particularly if your display is USB, test an updated BrlTTY package. I've fixed one or two issues in this package, and would like to get user testing before I put it into hardy. I've made it available for both gutsy and hardy, to get wider testing. Add one of the following lines to your /etc/apt/sources.list file to get the newer BrlTTY. gutsy: http://ppa.launchpad.net/themuso/ubuntu gutsy main hardy: http://ppa.launchpad.net/themuso/ubuntu hardy main One issue that I am pretty sure I have resolved, is the issue whereh the configuration file gets overwritten at every boot. Please in particular see if this issue is resolved for you. Please give this package a good test with your display, and let me know if you find any issues. This is the best time to get BrlTTY fixed up as well as is possible for Ubuntu hardy, and the more issues we can get fixed now, the better. Thanks in advance for your help. Luke -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHx93djVefwtBjIM4RAjhxAKC6CrPfc3EEFS1dv4FfhBmMdBXarwCfcVA7 TPDdeR3eDmdQ3U7c4zt15sk= =3u56 -END PGP SIGNATURE- -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: [orca-list] BrlTTY package testing.
Hi, Is it recommended to remove the old brltty with sudo apt-get --purge remove brltty or this new brltty replaces completely the other? Thanks Best regards Sérgio Neves - Original Message - From: Luke Yelavich [EMAIL PROTECTED] To: Orca screen reader developers [EMAIL PROTECTED]; Ubuntu Accessibility Mailing List ubuntu-accessibility@lists.ubuntu.com Sent: Friday, February 29, 2008 10:26 AM Subject: [orca-list] BrlTTY package testing. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all I am writing to request that all of you who have braille displays, particularly if your display is USB, test an updated BrlTTY package. I've fixed one or two issues in this package, and would like to get user testing before I put it into hardy. I've made it available for both gutsy and hardy, to get wider testing. Add one of the following lines to your /etc/apt/sources.list file to get the newer BrlTTY. gutsy: http://ppa.launchpad.net/themuso/ubuntu gutsy main hardy: http://ppa.launchpad.net/themuso/ubuntu hardy main One issue that I am pretty sure I have resolved, is the issue whereh the configuration file gets overwritten at every boot. Please in particular see if this issue is resolved for you. Please give this package a good test with your display, and let me know if you find any issues. This is the best time to get BrlTTY fixed up as well as is possible for Ubuntu hardy, and the more issues we can get fixed now, the better. Thanks in advance for your help. Luke -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHx93djVefwtBjIM4RAjhxAKC6CrPfc3EEFS1dv4FfhBmMdBXarwCfcVA7 TPDdeR3eDmdQ3U7c4zt15sk= =3u56 -END PGP SIGNATURE- ___ Orca-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: [orca-list] BrlTTY package testing.
Sérgio Neves, le Fri 29 Feb 2008 14:39:47 -, a écrit : Is it recommended to remove the old brltty with sudo apt-get --purge remove brltty or this new brltty replaces completely the other? It should nicely replace the old one. Samuel -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[wishlist] brltty
Hi all, Hi developers and/or maintainers/coworkers, After having commented the right (3) lines in /etc/init.d/brltty as indicated at http://live.gnome.org/Orca/Braille my Ubntu Gutsy Gibbon *finally* booted-up without overriding my personalized /etc/brltty.conf But now I have three proposals for the Ubuntu-Accessibility team/brltty maintainer(s): 1* first, make us a nice Christmas surprise: do debug it and publish a new package with the hal/brltty bug fixed ! 2* btw, publish a recent version since 3.7.2 seems to be quite old enough... 3* last but not least, I presume autodetection is something important, but why not making the default text-table then dependent of the /etc/default/locale ? OK there are more locales and lang support under Linux than Braille tables, but that's absolutely not a problem since countries_linguistic parts like de_de or nl_nl or nl_be probably historically prefer a certain braille table as default, here de, just like for example fr_fr or fr_mc or fr_be or fr_ca prefer the fr table. Isn't this an idea ? Finally you must know that a non-US blind user like me reads yp|ubuntu56 instead of [EMAIL PROTECTED]:~$ when brltty's us table is default: it's not a problem for five minutes but unusable for a long working day... And we shouldn't talk then about numbers... I know this is a comlicated problem, but this is a suggestion + an urgent wishlist: feel free to discuss about it. GrtnX Y P -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
TR: big problem with BrlTty under Gutsy
Hi, I have Ubuntu 7.10 Gutsy Gibbon pre-installed on my new Asus laptop. Ubuntu starts-up correctly but I encountered a BIG annoying problem with my Alva Satellite 544: the display is recognized but I doesn't like the us table and I wasn't able to find the efficient method to prevent hal to redetect the Alva or to override my /etc/brltty.conf: even if I mv /etc/udev/rules.d/85-brltty.rules or block /lib/brltty/brltty.sh or provide the same text-table de to both /etc/brltty.conf + /etc/brltty.conf.orig, it *still* continues to start with us table and to override /etc/brltty.conf Please it would be very nice to resolve this very big bug and publish asap a new brltty package update: I'm becoming crazy! If someone can tell me step by step what to do (since my English is not famous) I will try to do that, but please resolve the problem, it's awful and I can't help other peoplee as long as I can't help resolving my own problem. ThnX Y P -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: TR: big problem with BrlTty under Gutsy
Hi, The answer you are looking for is on the orca braille wikipage. http://live.gnome.org/Orca/Braille its under the heading: /etc/brltty.conf is overwritten Hope that the solution presented works for you. but you are right, it should be resolved by package maintainers. -Jon On Wed 21/11/2007 at 20:55:15, Y P wrote: Hi, I have Ubuntu 7.10 Gutsy Gibbon pre-installed on my new Asus laptop. Ubuntu starts-up correctly but I encountered a BIG annoying problem with my Alva Satellite 544: the display is recognized but I doesn't like the us table and I wasn't able to find the efficient method to prevent hal to redetect the Alva or to override my /etc/brltty.conf: even if I mv /etc/udev/rules.d/85-brltty.rules or block /lib/brltty/brltty.sh or provide the same text-table de to both /etc/brltty.conf + /etc/brltty.conf.orig, it *still* continues to start with us table and to override /etc/brltty.conf Please it would be very nice to resolve this very big bug and publish asap a new brltty package update: I'm becoming crazy! If someone can tell me step by step what to do (since my English is not famous) I will try to do that, but please resolve the problem, it's awful and I can't help other peoplee as long as I can't help resolving my own problem. ThnX Y P -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: problem installing brltty 3.9 in ubuntu gutsy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Nov 07, 2007 at 01:21:19AM EST, Sauro Cesaretti wrote: Hello everyone, I tried to compile and install brltty 3.9 the newer version available in the official web site. It works when I compile and install the daemon. but when I tried to start it and checked the version, I noticed that I still have the old version 3.7.2. do you know the reason? Its more than likely that you still have the brltty 3.7.2 packages from gutsy installed. You will need to remove these before attempting to use your locally built copy of BrlTTY. - -- Luke Yelavich GPG key: 0xD06320CE (http://www.themuso.com/themuso-gpg-key.txt) Email MSN: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHMMyZjVefwtBjIM4RAsvJAKDxXrgAGgt8gWm3EheLmJa0stws7QCgrw7H jdiNdAY5MqRmW/9ZWnAjhgo= =ZvPb -END PGP SIGNATURE- -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Updating orca and brltty in ubuntu gutsy
Hi everyone, I've just installed ubuntu 7.10 yesterday and I saw that it is still using brltty 3.7. And orca is not updated as well. I tried to install brltty from the source when gutsy was still in beta and it seems that the driver didn't work. Could I update these software from the source? Have you tried to do that? Should I follow a particular procedure? thank you in advance best regards, Sauro -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Problems encountered with gutsy and brltty
Hello everyone, I've just tried live cd of butsy with a supervario display and I still having the some problems that I had with ubuntu feisty. The brltty support starts twice and the second time I can read 1 startup problem and when I'll reach the graphical interface, orca screen reader doesn't work. I even made another test, I started the live cd without activating the accessibility support and the braille display was disconnected, after that I selected the text console With ctrl+alt+f1 and I connected the brialle display Because I'd like to start brltty manually, But I noticed that the support was already active. What does it depend of? I even saw that in this case, I didn't get the startup problem message. hope it will help to solve these problems. Thanks so much in advance for your support. Best regards, Sauro No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.488 / Virus Database: 269.13.33/1036 - Release Date: 28/09/2007 15.40 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
problem loading brltty in ubuntu 7.04
Hello everyone, I'm a new user of ubuntu and I don't know if I'm in the right list. I have a problem loading the brltty support in ubuntu. I have a baum supervario display connected to the usb interface and it seems that the daemon reset the display every time that I'm going to run the brltty daemon and it never works properly in the end. I tried to disconnect and reconnect again and it starts. The problem is that I should exectute this pocedure everytime. After that,I tried to download,compile and install the last version of brltty from the official website but it seems that it's worst than before, because it doesn't work even if I'm going to disconnect and reconect again. I saw a kind of this problem in another distro but it semms to work correctly after that I updated the kernel. Is there any possible way to avaoid to recompile the entire kernel? Have you ever encountered this problem before? I hope that you can help me thanks in advance best regards, Sauro No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.488 / Virus Database: 269.13.33/1034 - Release Date: 27/09/2007 17.00 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: brltty issue on ubuntu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Sep 21, 2007 at 02:49:01PM EST, Sérgio Neves wrote: So, I'd like to know whether this is a problem or bug or not. Could people that made this scripts or other knowledgeable people see what happens and why or forward this message to them? Ubuntu has made changes to the brltty package to allow for easier configuration of brltty from the live CD, and for install. I wasn't the one who wrote the code, but I'll have a look at the package and see if I can find out why this is done, and will see if I can talk to the person who implemented it, to work out a solution. - -- Luke Yelavich GPG key: 0xD06320CE (http://www.themuso.com/themuso-gpg-key.txt) Email MSN: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG81NojVefwtBjIM4RAiMbAJ9Ve2gDGcEYxjEsAh1HLaxlhZBDkwCguxjV 0uiU2vKoxF5fOwkNGFDDKuc= =tQ0F -END PGP SIGNATURE- -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[EMAIL PROTECTED]: Re: [BRLTTY] brltty.conf is altered]
Hi. I'm forwarding this message because I no longer run Ubuntu so my information on updating the initrd won't be correct. Would someone more knowledgeable please help? It is really annoying to have something break your accessibility. Kenny - Forwarded message from Sérgio Neves [EMAIL PROTECTED] - From: Sérgio Neves [EMAIL PROTECTED] Subject: Re: [BRLTTY] brltty.conf is altered Hi Kenny, Sorry for emailing you directly, but I don't want to fill the list of unecessary emails. Can you explain me what is initrd image, this function and how do I access it? Or a web site where I can learn it in a easy way? Sorry for this stupid question, but I don't dominate this subject. Thanks and best regards Sérgio Neves - Original Message - From: Kenny Hitt [EMAIL PROTECTED] To: Informal discussion between users and developers of BRLTTY. [EMAIL PROTECTED] Sent: Wednesday, September 19, 2007 10:12 AM Subject: Re: [BRLTTY] brltty.conf is altered i. It looks like Ubuntu has a copy of brltty.conf on there initrd. Probably the best solution is to cp your updated brltty.conf from /etc to the copy on the initrd image. then your changes will exist in both copies. The other option is to comment out the lines in brltty.sh that do the copy. Kenny ___ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [EMAIL PROTECTED] For general information, go to: http://mielke.cc/mailman/listinfo/brltty - End forwarded message - -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
brltty 3.7.2 startup issues
Hi, Just was wondering, if someone could share some light on this: Fresh ubuntu install on my laptop always boots with 2 instances of brltty, whereas the same setup on the desktop machine only has one instance of brltty running. I have done a fresh reinstall on both to see if it was some setting or file that i might have modified by accident, but the behavior persists. In all cases, the brltty starts before orca is started. Thank you -Jon -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Problems in ubuntu with orca and brltty
Hello, I've just installed ubuntu feisty 7.04 and I need your help. First, I can't use the braille support in orca, even if it's enalbed in the braille panel. Second, when the distro is starting-up I can see one message in braille display when it's inizialized. The message is:1 startup problem. How can I identify what is the problem? I'm using one supervario 40 cells display braille and It's connected at usb port. Thanks in advance for all information. Best regards, Sauro -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Running BRLTTY on startup
Hi all, How do I make BRLTTY starting with the system? Running latest ubuntu 7.04. many thanks, Christian -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Beta version of Feisty Fawn: problems with BRLTTY and Orca
Hi Luke, How did you start the live CD? Did you choose any of the options from the Accessibility boot menu? I did not choose an option but entered the CD and waited. Unfortunately, one cannot clearly make out when one actually is in the boot menu. The CD only stops spinning for an instant and then continues rather quickly. Possibly, one could improve the CD's accessibility by having a blip played out by the PC speaker and by setting up a longer timeout. This is how the Oralux CD works. Which option should I choose? Being in a rush, I was not able to find any recent information on the Ubuntu website. Simon -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Beta version of Feisty Fawn: problems with BRLTTY and Orca
Hi, I tested the beta version with my Braille display that is connected to the laptop via USB. BRLTTY was started and accepted the Braille display. I wanted to switch to the virtual console with Alt+F1 in order to start Orca. I was not shown a prompt. Thus, I switched to Gnome with Alt+F7 and pressed Alt+F2. Then, I entered orca and ran through the setup with the voice output. Subsequently, I answered the question whether I would like to logout with 'yes'. I did not hear a drumbeat and was not logged out and in properly. As I acted on the assumption of a problem report I pressed Enter. With Alt+F1 I was able to switch to the console, where, however, I still was not shown a prompt. It would be nice if this problem could be solved. At the moment it seems like one cannot test Orca at all. Simon -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Beta version of Feisty Fawn: problems with BRLTTY and Orca
On Tue, Mar 27, 2007 at 07:56:37PM EST, Simon Bienlein wrote: Hi, I tested the beta version with my Braille display that is connected to the laptop via USB. BRLTTY was started and accepted the Braille display. How did you start the live CD? Did you choose any of the options from the Accessibility boot menu? -- Luke Yelavich GPG key: 0xD06320CE (http://www.themuso.com/themuso-gpg-key.txt) Email MSN: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] signature.asc Description: Digital signature -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: Beta version of Feisty Fawn: problems with BRLTTY and Orca
On Tue, Mar 27, 2007 at 09:58:45PM EST, Samuel Thibault wrote: Hi, Simon Bienlein, le Tue 27 Mar 2007 11:56:37 +0200, a écrit : I wanted to switch to the virtual console with Alt+F1 in order to start Orca. I was not shown a prompt. I can confirm this: they seem to have _dropped_ the text console logins... To my mind, this really has to be reverted. According to the core development team,this is a known bug, and should be fixed soon. -- Luke Yelavich GPG key: 0xD06320CE (http://www.themuso.com/themuso-gpg-key.txt) Email MSN: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] signature.asc Description: Digital signature -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: BRLTTY ignores option for attributes table
Simon Bienlein wrote: Hi, I tested BRLTTY and Orca with the ubuntu cd of October 8. After the jingle, I pressed strg+alt+F1 and entered the following command: sudo brltty -a text.de -b ht -d ttyS0 The German attributes table was not loaded. Is this a bug or did I do something wrong? I'm not very familiar with brltty, but it seems like -a wants the full path to the attributes table. The default path mentioned in /etc/brltty.conf is used (the /etc/brltty/) in ubuntu. Perhaps the filename needs to be text.de.tbl ? Henrik -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: BRLTTY ignores option for attributes table
Hi, Henrik Nilsen Omma, le Wed 18 Oct 2006 15:48:49 +0200, a écrit : Simon Bienlein wrote: I tested BRLTTY and Orca with the ubuntu cd of October 8. After the jingle, I pressed strg+alt+F1 and entered the following command: sudo brltty -a text.de -b ht -d ttyS0 The German attributes table was not loaded. Is this a bug or did I do something wrong? I'm not very familiar with brltty, but it seems like -a wants the full path to the attributes table. Simon, are you sure you're talking about the attribute table (-a), and not about the text table (-t)? What I guess you want is brltty -t de -a attributes.tbl Samuel -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: BrlTTY / orca
Hi, Veli-Pekka Tätilä, le Wed 04 Oct 2006 16:45:18 +0300, a écrit : I'm natively running Windows XP and Dolphin Supernova 7, which is a combined screen reader and magnifier. WIthin WIndows I have a pair of virtual serial ports com 1 and com 2 that are connected like a null-modem cable. Additionally, I'm running VmWare Server 1.01 which runs Ubuntu Dapper as a guest OS. There's a serial port in that Linux virtual machine which is connected to the host machine's com2 port. The last component of the puzzle is the terminal emulator TeraTerm which monitors the com 1 port, that being the other end of the virtual null modem cable. Ah, ok. I can understand this much better now :) VmWare server also supports USB devices and if my WIndows reader is not using it, the LINux virtual machine can see my Braille display (Tieman Voyager). What I'd like to do would be to get brlTTY working Doesn't this already work? I mean, if you cut down your windows reader, BrlTTY should be able to grab the device, and give you a reading of the console, and once orca/gnopernicus run, get their reading of the gnome session. I've already got Gnopernicus speaking but it says it cannot find the braillle display. As gnopernicus probably said, the checklist is - /etc/brlapi.key exists and is not empty. - you have read right on /etc/brlapi.key - brltty is running with API enabled. Another possibility would be to run brltty natively inside windows, and have gnopernicus connect to it through network. A bit tricky, but not that much (you just need to set the BRLAPI_HOSTNAME environment variable to host:0 where you replace host by the name of your windows machine, or its IP). Samuel -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Bug 58718] brltty must be started with sudo
Public bug reported: Permissions in Ubuntu seem to be prganised such that brltty (the braille system) must always be started as root (sudo). Please consider adding a device type that normal users can have the appropriate permissions for to fix this. $ brltty brltty: BRLTTY 3.7.2 brltty: Linux Screen Driver brltty: Cannot open screen device: /dev/vcsa: Permission denied brltty: cannot read screen. ** Affects: brltty (Ubuntu) Importance: Untriaged Status: Unconfirmed -- brltty must be started with sudo https://launchpad.net/bugs/58718 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Bug 58718] Re: [Bug 58718] brltty must be started with sudo
Henrik Nilsen Omma, le Sun 03 Sep 2006 14:21:10 -, a écrit : Permissions in Ubuntu seem to be prganised such that brltty (the braille system) must always be started as root (sudo). Please consider adding a device type that normal users can have the appropriate permissions for to fix this. $ brltty brltty: BRLTTY 3.7.2 brltty: Linux Screen Driver brltty: Cannot open screen device: /dev/vcsa: Permission denied brltty: cannot read screen. Mmm, being able to read the console is quite dangerous: via an ssh account, it's just spying. And being able to insert keypresses on the console is even more dangerous. I'd suggest to rather add a brl group that would have such permissions (so as to limit people who have such powerful permissions). Samuel -- brltty must be started with sudo https://launchpad.net/bugs/58718 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: [BRLTTY] Brltty on ubuntu cd
Hi, Cheryl Homiak, le Wed 23 Aug 2006 12:09:11 -0500, a écrit : Wasn't sure on which list this was most appropriate, so hope nobody will mind my posting here. There is an ubuntu-accessibility lists, so I'm forwarding this. My question is: is there a way at boot to specify the braille-driver on the ubuntu cd? If one cuses f5 and the blindness choice for accessibility, brltty will, if I understand correctly, be looking for the braille display as a usb device. If one has a serial or usbserial device, one needs to be able to specify this device instead. It wasn't clear to me whether, before hitting the final enter for ubuntu to start booting, there was provision for entering the brltty driver information. Please Ubuntu guys answer this ;) Samuel -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Bug 56589] Re: brltty: Request for sponsorship of this package upload.
Samuel, in my haste I uploaded an incorrect version (that Adam kindly pointed out). The fixed version was uploaded shortly afterward [0]. [0] https://lists.ubuntu.com/archives/edgy- changes/2006-August/003939.html -- brltty: Request for sponsorship of this package upload. https://launchpad.net/bugs/56589 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Bug 56589] Re: brltty: Request for sponsorship of this package upload.
Debdiff between old Ubuntu, and merged package. -- brltty: Request for sponsorship of this package upload. https://launchpad.net/bugs/56589 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Bug 56589] Re: brltty: Request for sponsorship of this package upload.
Luke, it would be easiest if you generated a correct debdiff between the current Debian version and the newer merged ones; changelog entries seem to be missing. -- brltty: Request for sponsorship of this package upload. https://launchpad.net/bugs/56589 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Bug 56589] Re: brltty: Request for sponsorship of this package upload.
Fixed debdiff between Debian and Ubuntu merged package -- brltty: Request for sponsorship of this package upload. https://launchpad.net/bugs/56589 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Bug 56589] Re: brltty: Request for sponsorship of this package upload.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 Aug 2006 22:57:14 +1000 Source: brltty Binary: libbrlapi1 brltty-flite brltty-udeb libbrlapi1-dev brltty brltty-x11 Architecture: source Version: 3.7.2-3.1ubuntu1 Distribution: edgy Urgency: low Maintainer: Mario Lang [EMAIL PROTECTED] Changed-By: Luke Yelavich [EMAIL PROTECTED] Description: brltty - Access software for a blind person using a soft braille terminal brltty-flite - Access software for a blind person using a soft braille terminal brltty-udeb - Access software for a blind person using a soft braille terminal brltty-x11 - Access software for a blind person using a soft braille terminal libbrlapi1 - braille display access via BRLTTY - shared library libbrlapi1-dev - Library for communication with BRLTTY - static libs and header s Closes: 376863 Changes: brltty (3.7.2-3.1ubuntu1) edgy; urgency=low . * Merge from Debian unstable. * Move /lib/libbrlapi.so symbolic link from libbrlapi1-dev to libbrlapi1 to make sure that gnome-orca can work with braille support. * Commented out the include for linux/compiler.h in Programs/usb_linux.c. . brltty (3.7.2-3.1) unstable; urgency=low . * Non-maintainer upload. * changing build-depends from libbluetooth1-dev to libbluetooth2-dev | libbluetooth-dev as suggested by Felipe Augusto van de Wiel and Rudy Godoy. (Closes: #376863) Thanks! Files: 4bea2f9cda55840fc91a5b8280ac6d56 771 admin extra brltty_3.7.2-3.1ubuntu1.dsc e92bdee36b9482a8f3dce288462490ce 44030 admin extra brltty_3.7.2-3.1ubuntu1.diff .gz Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFE4+hZe9GwFciKvaMRAh+pAJ9E3SPC9p+aL6rAbyMzno5X/ONB9gCfRUtm kWWvxddzaxgl5yMYiDEmtdo= =N+fo -END PGP SIGNATURE- ** Changed in: brltty (Ubuntu) Status: Unconfirmed = Fix Released -- brltty: Request for sponsorship of this package upload. https://launchpad.net/bugs/56589 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Bug 40245] Re: CPU usage of idle brltty is too high
*** This bug is a duplicate of bug 40174 *** ** This bug has been marked a duplicate of bug 40174 Serious Memory Leak -- CPU usage of idle brltty is too high https://launchpad.net/bugs/40245 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Bug 39332] Re: brltty needs to install non-interactively
** Bug 39872 has been marked a duplicate of this bug -- brltty needs to install non-interactively https://launchpad.net/malone/bugs/39332 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Bug 39332] Re: brltty needs to install non-interactively
Henrik and everybody else of the ubuntu-accessibility list: how worthwhile would the package be, without flite and the brltty-flite package? Is that route worth pursuing or should we try to get it off ubuntu-desktop? We almost definitely can't add the flite suite due to size constraints. -- brltty needs to install non-interactively https://launchpad.net/malone/bugs/39332 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Bug 39332] Re: brltty needs to install non-interactively
Yes I agree that it should be configured so that it is inactive for most people. It should not raise any dialog box. It should only be activated when the user selects the 'Blindness' option on the Live CD or activates AT features manually post-install. -- brltty needs to install non-interactively https://launchpad.net/malone/bugs/39332 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: [Bug 39332] Re: brltty needs to install non-interactively
Henrik Nilsen Omma, le Thu 13 Apr 2006 08:52:16 -, a écrit : Yes I agree that it should be configured so that it is inactive for most people. It can be left in autodetect mode. Whenever a USB braille device is plugged-in, it wakes up. Regards, Samuel -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Bug 26995] Re: brltty: Does not support USB for Alva devices - please upgrade
Thanks Matt. Please sync brltty 3.7.2-2 from Sid, ok to override Ubuntu changes. -- brltty: Does not support USB for Alva devices - please upgrade https://launchpad.net/malone/bugs/26995 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Bug 39332] Re: [Dapper] brltty should provide 'none' as reader
** Changed in: brltty (Ubuntu) Target: None = ubuntu-6.06 ** Summary changed: - [Dapper] brltty should provide 'none' as reader + brltty needs to install non-interactively ** Changed in: brltty (Ubuntu) Assignee: (unassigned) = Tollef Fog Heen -- brltty needs to install non-interactively https://launchpad.net/malone/bugs/39332 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
RE: [Bug 26995] Re: brltty: Does not support USB for Alva devices - please upgrade
Hi Luke, After checking both the dapper version and the Debian Sid version of brltty, it appears that the newest version in Debian is a new upstream release. I am wondering whether this would simply be better to sync to the latest Debian release? This seems logical it would also make sense to update the configuration script to include the new configuration script to include the latest supported displays and devices. If you want me to test any packages just let me know. Thanks for the quick response. Also, thanks for creating the gnome-orca package. It's really great to see people trying and giving feedback on where we are so far. Mike -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
