ubuntu 8.04.1 installer
Hi, On my laptop, both the option to install and the option to start the desktop work well (orca speaks). However, on my desktop, when I boot from the ubuntu 8.04.1 cd, press enter to select the english language, press down arrow to install option, f5, three down arrows to screen reader and two enters, the installer starts but orca doesn't speak. I did it with a sighted person, so I know I did it well. However, if I select the other option (to start the desktop), and after call orca, it speaks perfectly. What could be the problem? Or what can I do to help diagnosing the problem? Thanks Best regards Sérgio Neves -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: grub beep control-g
Hi, How are you able to navigate ithrough a document with down arrow? When I am on plain text view, orca doesn't only read the plain text portion, but also some hexadecimal portion, so it's difficult to locate certain line. Or do you use the search facility? Thanks Best regards Sérgio Neves - Original Message - From: Jonathan Chacón [EMAIL PROTECTED] To: 'E.J. Zufelt' [EMAIL PROTECTED]; 'Ubuntu Accessibility' ubuntu-accessibility@lists.ubuntu.com Sent: Saturday, June 07, 2008 6:00 AM Subject: RE: grub beep control-g -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de E.J. Zufelt Enviado el: sábado, 07 de junio de 2008 0:30 Para: Ubuntu Accessibility Asunto: grub beep control-g Good evening, Hi I am blind and running a dual-boot of Ubuntu and Windows. I would like to find a way to make the grub menu beep when it is loaded. I understand that this can be done by adding control-g at the beginning of one of the menu titles. However, I can't seem to produce the control-g code in either vi or vim through gnome-terminal. Any suggestions? You have to add the hexadecimal character 07 using a hexadecimal editor. You can use hexedit in Ubuntu: $ sudo aptitude install hexedit Hexedit is an easy editor with 2 views. First view is for plain text. The second one is for hexadecimal version. You can jump between views using tab key. You have to set the cursor on a space character in a line with the command Title. For example: Title Microsoft Windows XP You can set the cursor between Windows and XP. Next, press tab key to jump to hexadecimal view and type 07. Note, you have to type 0, right arrow and 7 because insert text mode is deactivated by default. When you had made the changes. Save the file pressing control+X Regards Jonathan Chacón -- 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 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
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
problems running speech-dispatcher 0.6.6
Hi, I have ubuntu 7.10 and I've tried to install and run speech-dispatcher 0.6.6. It compiles and installs well (I installed it on my home directory), but when I run it, it presents the following errors (I'm cutting some messages): [EMAIL PROTECTED]:~/bin $ ./speech-dispatcher -P /home/manuel/speechrun Error: can't open logging file /home/manuel/splog//speechd.log! Using stdout. speechd: ERROR: Openning debug file for espeak failed: (error=-1) No such file or directory speechd: Output module is logging to standard error output (stderr) It opens alsa successfully and starts espeak module successfully. After that, it performs the following tests: [Sun Feb 17 11:55:29 2008 : 914547] speechd: LINE here:|200-afrikaans af none| [Sun Feb 17 11:55:29 2008 : 914948] speechd: LINE here:|200-german de none| [Sun Feb 17 11:55:29 2008 : 915022] speechd: LINE here:|200-greek el none| [Sun Feb 17 11:55:29 2008 : 915097] speechd: LINE here:|200-default en none| [Sun Feb 17 11:55:29 2008 : 915186] speechd: LINE here:|200-en-rhotic en r| [Sun Feb 17 11:55:29 2008 : 915261] speechd: LINE here:|200-en-scottish en sc| ... [Sun Feb 17 11:55:29 2008 : 917420] speechd: LINE here:|200 OK VOICE LIST SENT| [Sun Feb 17 11:55:29 2008 : 917536] speechd: Module espeak started sucessfully with message: --- Espeak: Initialized successfully. --- Could anyone tell me how I solve the errors it gives me, mainly the fact that it can't open espeak's debug logfile and speech-dispatcher's log file? And onn this lines: [Sun Feb 17 11:55:29 2008 : 915097] speechd: LINE here:|200-default en none| What's the meaning of none word? Thanks Best regards Sérgio Neves -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: problems running speech-dispatcher 0.6.6
Hi, Oh, thanks, I thought speech-dispatcher created directories if they didn't exist. So this problem is solved. But I have another doubt: Now I have speech-dispatcher running well with espeak and orca, but when I type spd-say hello it says: spd-say: error while loading shared libraries: libspeechd.so.2: cannot open shared object file: No such file or directory. What does it mean? I don't find any file with this name. The file I hve on /usr/lib is libespeak.whatever, not libspeechd.whatever. Thanks Best regards Sérgio Neves - Original Message - From: Tomas Cerha [EMAIL PROTECTED] To: Sérgio Neves [EMAIL PROTECTED] Cc: ubuntu-accessibility@lists.ubuntu.com Sent: Sunday, February 17, 2008 3:57 PM Subject: Re: problems running speech-dispatcher 0.6.6 Sérgio Neves wrote: Error: can't open logging file /home/manuel/splog//speechd.log! Using stdout. Hello Sérgio, does the directory /home/manuel/splog exist and is it writable by the user, under which SD runs? Regards, Tomas. -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
ubuntu alternate cd - configuration and suggestions
Hi, I've installed ubuntu using the alternate cd and it did well. But the problem is the following: When I start my system, it always asks for my type of braille display, port, etc. What can I do to prevent this questions on each start up? As a suggestion, is it possible to improve the alternate cd so that it assumes the options that we made on the installation process and starts up the system with these options? I'd like to make another suggestion: In these braille options, is it possible to add the option to choose a braille table? Thanks for providing all of this Best regards Sérgio Neves -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
brltty.conf is altered
Hi, I have ubuntu 7.04 installed on my laptop and brltty and this issue arises whichever version of brltty is installed (3.7.2 or 3.8). I edit the /etc/brltty.conf file to put my preferences, for example, my braille table. When I restart the machine, brltty.conf is changed to a default which I don't know what, and I lost the changes I have made. The first line of /etc/brltty.conf is: # Created by /lib/brltty/brltty.sh What does it mean and what is the best way to stop changing the brltty.conf automatically on machine's restart? Thanks Best regards Sérgio Neves -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Error with braille display
Hi, I have an HP pavillion laptop and a focus 40 braille display (usb interface). I have ubuntu 7.04. When I boot this ubuntu version from the cd or from the hard drive where it is installed, I think brltty sstarts up with ubuntu and I don't need to do nothing. What happens is the following: In the normal cenarius, brltty presents the message brltty 3.7.2 then presents screen not in text mode because ubuntu starts with the graphical interface.. Then when orca starts, the braille display works too. Sometimes, instead of presenting screen not in text mode it presents 1 startup error and I cannot put orca working with the display. When in this situation, I typed dmesg filename.txt and the content from the beginning is: [ 738.22] usb 3-1: usbfs: process 3349 (brltty) did not claim interface 0 before use [ 738.26] usb 3-1: usbfs: process 3349 (brltty) did not claim interface 0 before use [ 738.30] usb 3-1: usbfs: process 3349 (brltty) did not claim interface 0 before use [ 738.34] usb 3-1: usbfs: process 3349 (brltty) did not claim interface 0 before use [ 738.38] usb 3-1: usbfs: process 3349 (brltty) did not claim interface 0 before use ... (it's the same thing till the end) Although in this situation it doesn't work with orca, it works with the textual consoles. What's the meaning of this? And what can I do to solve this? I don't have experience. Thanks for the attention Best regards Sérgio Neves-- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
