From kb8aey at verizon.net Mon Sep 1 04:48:03 2008 From: kb8aey at verizon.net (mike) Date: Sun, 31 Aug 2008 23:48:03 -0500 (CDT) Subject: I'm having problems with orca crashing when running admin apps Message-ID: <0K6I00DF32O2YSM0@vms173001.mailsrvcs.net> Hi, I can run most of the admin apps in the root account. But for some reason Orca seems to crash quite often after I have had one opened for a short time. For example, the login window app seems to crash Orca as does the package manager. Is this a known problem? One other thing. Why is it that the update manager gives a progress report when used in the root account, but in my account I get no progress report when it is downloading? The same is true when using add remove programs. The progress report is very handy, so I hope this can be corrected. If not, how about a beep instead. Mike. X-Antivirus: avast! (VPS 080831-0, 08/31/2008), Outbound message X-Antivirus-Status: Clean From kb8aey at verizon.net Mon Sep 1 04:52:04 2008 From: kb8aey at verizon.net (mike) Date: Sun, 31 Aug 2008 23:52:04 -0500 (CDT) Subject: is speakup in ubuntu Message-ID: <0K6I00IFY2USJLYL@vms173005.mailsrvcs.net> Hi, I think speakup use to be in ubuntu. Is it still included? If so, how do you start it? If it is included, can it be used on the alternate CD. This would be handy for installing ubuntu server. Mike. From kb8aey at verizon.net Mon Sep 1 17:53:31 2008 From: kb8aey at verizon.net (mike) Date: Mon, 01 Sep 2008 12:53:31 -0500 (CDT) Subject: I'm having a problem with sound settings Message-ID: <0K6J00HT9317TO93@vms173003.mailsrvcs.net> Hi, I went to change the login sound and discovered that there are no choices in the sound menu. The device menu in the sound setting still has it's menu. Has something changed in the sound settings? Or is this broken? Mike From kb8aey at verizon.net Mon Sep 1 23:28:08 2008 From: kb8aey at verizon.net (mike) Date: Mon, 01 Sep 2008 18:28:08 -0500 (CDT) Subject: Maybe someone can answer a question about wireless networks with ubuntu Message-ID: <0K6J0041UIITQ7VA@vms173005.mailsrvcs.net> Hi, I can now use Orca to connect to my wireless network using the included tools. Here is the problem I am having. My ubuntu machine connects to my router fine. But when I try to connect to a computer to computer network it will not connect. I know the key is right because my windows computers all connect fine. But for some reason the ubuntu computer won't connect. Has anyone else experimented with this? Mike. From crystallogic at ca.inter.net Tue Sep 2 06:22:33 2008 From: crystallogic at ca.inter.net (JM & Angel) Date: Tue, 2 Sep 2008 02:22:33 -0400 Subject: Speakup and Orca? Message-ID: <001401c90cc4$495b66e0$6502a8c0@winblows> Hello. First time writing to these lists, and I'm writing to both because although my main thrust is now trying to get speakup to work, I'm sure some ubuntu users out there are also working with (or wanting to work with) Orca as well. I've a few questions/thoughts/observations. I'm pretty new to Linux really, but I used the OS remotely through a shell in my early internet days of the mid-1990s. During that time I became a little bit familiar with the command line in Linux and some of the console-level relevant applications (pine, lynx, etc) .. at the time I found this stuff really great and I thought that it might be cool to have my own LInux box someday, but DOS was on the way out, Windows taking over in a big way and so on, and I was pretty resistant but eventually made the switch to Windows. Well, I finally got a second machine and someone installed Ubuntu 8.04 on it for me, and even built a kernel with speakup modules plugged in. This would be fantastic, if I could actually get speakup to work, but so far I haven't had any luck. I have no hardware synth, although I might be able to get a Dectalk Express soon, so I've been trying to use speakup with the espeakup module to work with the Espeak synthesiser, which I already have been using with Orca. The Espeak voice is something I've been having a surprisingluy hard time getting used to, and I wonder if I've been spoiled by Eloquence? I have been using Orca a bit with the Gnome desktop environment. Until recently it wasn't working too well, but I got the Orca-SVN package and now things seem to run a good deal faster and crash less often. However, the more I fiddle with these desktop xwindows environments, the more I think, that "well, this is nice enough, kind of like windows and all, but I think I'd really rather use the console for almost anything I can think of. Why should I be attached to a GUI, when so many applications don't even seem to work very well with Orca"? So, I guess my real questions revolve around wondering why I can't get Speakup to talk to me. Does espeakup replace speech-dispatcher? I read in the speakup documentation that you need SD running to use a software synth, but the person who installed this stuff for me seemed to indicate that SD conflicted with something or that espeakup somehow superceded it. I can't seem to find much clear information on this online, so any help would be appreciated. Right now my login session defaults to gnome; I try and kill orca and then exit to c onsole, but I get no speech, either before or after login. I feel like such a newby, but I really am at a loss as to what to do. Any thoughts? JM -------------- next part -------------- An HTML attachment was scrubbed... URL: From cerha at brailcom.org Tue Sep 2 07:51:20 2008 From: cerha at brailcom.org (Tomas Cerha) Date: Tue, 02 Sep 2008 09:51:20 +0200 Subject: Speakup and Orca? In-Reply-To: <001401c90cc4$495b66e0$6502a8c0@winblows> References: <001401c90cc4$495b66e0$6502a8c0@winblows> Message-ID: <48BCF078.3010001@brailcom.org> JM & Angel wrote: > Does espeakup replace speech-dispatcher? More precisely it replaces speechd-up. Speechd-up is a connector between speakup and Speech Dispatcher, while espeakup connects speakup directly (and solely) to the Espeak synthesizer. Espeakup is a single purpose solution omitting the Speech Dispatcher's abstraction layer completely. As such, it might be easier to set up if you don't have Speech Dispatcher installed, but it misses features supported by speechd-up/Speech Dispatcher, such as internationalization, independence on the synth engine and interoperation with other assistive technologies (Orca, Yasr and others) which also use Speech Dispatcher. > I read in the speakup documentation that you need SD running to use a software > synth, but the person who installed this stuff for me seemed to indicate > that SD conflicted with something or that espeakup somehow superceded > it. They should not conflict, bot only one of them may be used at a moment. Best regards, Tomas From kb8aey at verizon.net Wed Sep 3 01:19:28 2008 From: kb8aey at verizon.net (mike) Date: Tue, 02 Sep 2008 20:19:28 -0500 (CDT) Subject: is there still a way to make help axcessable? Message-ID: <0K6L002T6ICGJJI1@vms173001.mailsrvcs.net> Hi, some time ago someone had a way to make help accessible. I think he had a patch that worked with firefox to do this. I used it at the time and found it to work well, except that every time yelp was updated it had to be installed again. Anyway, I lost the link to the patch. Does anyone still have it? If so will this patch still work in intrepid? Mike From kb8aey at verizon.net Wed Sep 3 02:45:45 2008 From: kb8aey at verizon.net (mike) Date: Tue, 02 Sep 2008 21:45:45 -0500 (CDT) Subject: where can I download the ubuntu manual Message-ID: <0K6L0048EMC8Q85G@vms173005.mailsrvcs.net> Hi, There use to be a link to download the ubuntu documentation. I got a server guide and a desktop guide at that time. But I do not see a link for downloading the guides anymore. Does anyone know the currant link to them? Mike. From William.Walker at Sun.COM Wed Sep 3 11:32:06 2008 From: William.Walker at Sun.COM (Willie Walker) Date: Wed, 03 Sep 2008 07:32:06 -0400 Subject: is there still a way to make help axcessable? In-Reply-To: <0K6L002T6ICGJJI1@vms173001.mailsrvcs.net> References: <0K6L002T6ICGJJI1@vms173001.mailsrvcs.net> Message-ID: Hi Mike: This might help: http://live.gnome.org/Orca/Yelp Note also that we're really trying to get yelp working: http://bugzilla.gnome.org/show_bug.cgi?id=356041 Hope this helps, Will On Sep 2, 2008, at 9:19 PM, mike wrote: > Hi, some time ago someone had a way to make help accessible. I think > he had a patch that worked with firefox to do this. > I used it at the time and found it to work well, except that every > time yelp was updated it had to be installed again. > Anyway, I lost the link to the patch. Does anyone still have it? If so > will this patch still work in intrepid? > Mike > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility From labrad0r at edpnet.be Wed Sep 3 15:49:24 2008 From: labrad0r at edpnet.be (Labrador) Date: Wed, 3 Sep 2008 17:49:24 +0200 Subject: braille doesn't work at all under Ubuntu 8.04.1 Message-ID: <20080903154924.GB3751@starfish> 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/ From chmiel at phil.muni.cz Wed Sep 3 20:59:00 2008 From: chmiel at phil.muni.cz (Mgr. Janusz Chmiel) Date: Wed, 3 Sep 2008 22:59:00 +0200 Subject: braille doesn't work at all under Ubuntu 8.04.1 References: <20080903154924.GB3751@starfish> Message-ID: <05305FF012E942519835CDE082195629@alskdfffffffffffffffffffj> Dear master and all users and developers, I would like to suggest You constructive approach to solve all accessibility issues related to support for Orca and braille display. Firstly, I think, that core developers of Ubuntu could make new desktop link for starting Orca with brltty. I Am unfortunately not experienced Gnome user, but may be, that adding sudo brltty and followed with line orca could solve problems with automatic braille displays detection. I tried to type gnome-terminal followed by Enter I typed sudo brltty, and my USB connected Tieman braille voyager has been successfully detected, initialized, and Brltty displayed correctly its message screen is not in A text mode. So if Your model will not be automatically detected, may be, that You could try to study command line parameters for Brltty to enable Your specific model of braille display. And please, do not forget to type sudo brltty followed by A specific parameters. You also mentioned about issue, that Orca can not automatically use A correct braille table for selected language. If You meaned by this, that Orca should automatically select right braille table according to The language, which user selected in The boot menu, there is difficulty related to Brltty, not to The Orca Screen reader. Eventhough Programmers fortunately are having procedure for detecting, which language has been selected and they can automatically select specific Espeak person for A specific language, automatically select braille table is not so simply, as some users could think. If user want to use A specific braille table for A specific language, user must modifi The file brltty.conf, which is located in The etc Directory. So open /etc/brltty.conf And try to analyze this file for Your wanted language. The language can begin with # Character. To enable support for A specific language, remove The # character at The beginning of A line, which is assigning The specific language. Please, try to study manual for Brltty or try to directly communicate with developer of Brltty latest version about those changes or if Your language is not awailable. I Am aware, that modifiing this file is only possible, when Ubuntu Hardy Heron or newest Ubuntu live CD version is allready installed on A hard drive. My opinion is, that every think depends on The fact, how many languages are predefined and are awailable in The /etc/brltty.conf file. Please, I would like to please all users of Ubuntu to be more patient, core developers of Ubuntu are doing their best and during next week, problems related to accessibility will be solved. Even problem with Brltty could be I think solved without many problems. If is it possible to type sudo brltty Orca to The Gnome desktop link for starting Orca. In The Ubuntu Feisty and gutsi, Brltty has been started during booting up, much sooner than Gnome has been started. So I think, that brltty has been started with Linux kernel probably. So I Am very sorry, that I can not help You more. The kindness regards. Janusz Chmiel From labrad0r at edpnet.be Wed Sep 3 21:09:30 2008 From: labrad0r at edpnet.be (Labrador) Date: Wed, 3 Sep 2008 23:09:30 +0200 Subject: persistent brltty question at boot time while brltty already configured Message-ID: <20080903210930.GU3751@starfish> 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. From kb8aey at verizon.net Wed Sep 3 21:46:29 2008 From: kb8aey at verizon.net (mike) Date: Wed, 03 Sep 2008 16:46:29 -0500 (CDT) Subject: I'm having a problem with orca in intrepid. Message-ID: <0K6N001LR35HY5W5@vms046.mailsrvcs.net> Hi, after installing intrepid Orca worked fine. However, if I log out by using alt CTRL backspace, it starts asking me to pick a voice. Is this a known problem. Also the log out menu now says in accessible. Are they using a different program for this? Mike. From labrad0r at edpnet.be Wed Sep 3 22:35:46 2008 From: labrad0r at edpnet.be (Labrador) Date: Thu, 4 Sep 2008 00:35:46 +0200 Subject: braille doesn't work at all under Ubuntu 8.04.1 In-Reply-To: <05305FF012E942519835CDE082195629@alskdfffffffffffffffffffj> References: <20080903154924.GB3751@starfish> <05305FF012E942519835CDE082195629@alskdfffffffffffffffffffj> Message-ID: <20080903223546.GW3751@starfish> 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 Ubuntu Hardy > Heron or newest Ubuntu live CD version is allready installed on A hard > drive. My opinion is, that every think depends on The fact, how many > languages are predefined and are awailable in The /etc/brltty.conf > file. Mmm, no the question is: where does Ubuntu Installer register the resposne that a user gave him regarding country and keyboard ? if that information is used by the installer for installing the requested locale and language packages, it might be used for brailel translation tables too. > Please, I would like to please all users of Ubuntu to be more patient, core > developers of Ubuntu are doing their best and during next week, problems > related to accessibility will be solved. Even problem with Brltty could be > I think solved without many problems. If is it possible to type sudo brltty > Orca to The Gnome desktop link for starting Orca. > > In The Ubuntu Feisty and gutsi, Brltty has been started during booting up, > much sooner than Gnome has been started. So I think, that brltty has been > started with Linux kernel probably. BrlTty can be started very soon: under the Debian Etch Installer, brltty is imediately started when the installer starts, so after having entered brltty=bb,dd,tt (braille driver, device and table) after 1 second of startup you have braille, that's very nice! But first of all, the Ubuntu Accessibility team have to resolve all the problems regarding braille support since they are becoming greater instead of being resolved. The major responsible of this is the serial to usb option: I can't understand that choice; the most of current displays are USB, serial is no longer the standard, and bluetooth is very new but not the majority of displays are. So why doesn't they simply debugged the Gutsy way of doing and implemented that with the default locale-based texst-table ? Under Hardy we got braille with the us table, now I experienced what a catastrophe it is to have no braille at all. I now resolved my problem thanks to a sighted person: I installed ssh and openssh-server at the laptop, and was able to connect me remotely and edit then brltty.conf But the presistent question at boot time continues to block me and blocking the starting process. Aldo. From hammera at pickup.hu Thu Sep 4 08:22:21 2008 From: hammera at pickup.hu (Hammer Attila) Date: Thu, 04 Sep 2008 10:22:21 +0200 Subject: Gnome-orca launchpad repository Message-ID: <48BF9ABD.4050200@pickup.hu> Dear list! Luke, I tryed your Orca development repository. Some problems and questions: 1. I tryed apt-get update and apt-get upgrade commands. The gnome-orca package upgraded with development version, but not have hungarian localizations. Originaly, Hardy using gnome-orca package (2.22.3-1 if I remember correct version number). Possible you doing repack the gnome-orca package with actual translations? Or possible replace gnome-orca package with stable version? Now, this packages available your repository: Gnome-orca-stable (actual stable version) gnome-orca-devel (development version, latest version is 2.23.5-0ubuntu1~ppa1) gnome-orca (2.23.5-0ubuntu1~ppa1) gnome-orca-svn (2.23.5~4036-0ubuntu1~ppa1) 2. The packages not signed. Possible solve this problem? 3. What happen when coming out the 2.24 stable orca version, possible repack gnome-orca-stable with actual Orca translations with 2.24 branch (because language packs are different with Hardy and Intrepid release)? Thanks your ansvers, Attila From j.t.laurie at gmail.com Thu Sep 4 21:08:54 2008 From: j.t.laurie at gmail.com (J. T. Laurie) Date: Thu, 4 Sep 2008 16:08:54 -0500 Subject: orca keystrokes Message-ID: <002001c90ed2$70a65600$6501a8c0@Rosetta> Dear list, SOme time back someone mentioned to me that there is a way to turn off sound notifications in my orca preferences. I have no idea how to do this, and until it's done, orca won't speak but other sounds play. Is there anything that can be done? Thanks! Taylor laurie IMPORTANT: This email is intended for the use of the individual addressee(s) named above and may contain information that is confidential, privileged or unsuitable for overly sensitive persons with low self-esteem, no sense of humour or irrational religious beliefs. If you are not the intended recipient, any dissemination, distribution or copying of this email is not authorised (either explicitly or implicitly) and constitutes an irritating social faux pas. Unless the word absquatulation has been used in its correct context somewhere other than in this warning, it does not have any legal or no grammatical use and may be ignored. No animals were harmed in the transmission of this email, although the kelpie next door is living on borrowed time, let me tell you. Those of you with an overwhelming fear of the unknown will be gratified to learn that there is no hidden message revealed by reading this warning backwards, so just ignore that Alert Notice from Microsoft. -------------- next part -------------- An HTML attachment was scrubbed... URL: From labrad0r at edpnet.be Sun Sep 7 10:45:49 2008 From: labrad0r at edpnet.be (Labrador) Date: Sun, 7 Sep 2008 12:45:49 +0200 Subject: [Fwd:Re: [orca-list] brltty, ubuntu and orca] Message-ID: <20080907104549.GE3262@starfish> ----- Forwarded message from Labrador ----- 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/ From themuso at ubuntu.com Mon Sep 8 00:41:00 2008 From: themuso at ubuntu.com (Luke Yelavich) Date: Mon, 8 Sep 2008 10:41:00 +1000 Subject: is speakup in ubuntu In-Reply-To: <0K6I00IFY2USJLYL@vms173005.mailsrvcs.net> References: <0K6I00IFY2USJLYL@vms173005.mailsrvcs.net> Message-ID: <20080908004100.GD10062@brainz.yelavich.home> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Sep 01, 2008 at 02:52:04PM EST, mike wrote: > Hi, I think speakup use to be in ubuntu. Is it still included? If so, how do you start it? If it is included, can it be used on the alternate CD. This would be handy for installing ubuntu server. No, speakup is not included, and will not be included again unless speakup is merged into the mainline kernel, hosted at kernel.org. Luke -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIxHScjVefwtBjIM4RAutCAJ9vf1d3c/r07UMsqXr02QEjLCbbAwCg2KJ4 flDn8lWAvwwJeHmX1WdN1yw= =sNoX -----END PGP SIGNATURE----- From themuso at ubuntu.com Mon Sep 8 00:40:07 2008 From: themuso at ubuntu.com (Luke Yelavich) Date: Mon, 8 Sep 2008 10:40:07 +1000 Subject: I'm having problems with orca crashing when running admin apps In-Reply-To: <0K6I00DF32O2YSM0@vms173001.mailsrvcs.net> References: <0K6I00DF32O2YSM0@vms173001.mailsrvcs.net> Message-ID: <20080908004007.GC10062@brainz.yelavich.home> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Mike On Mon, Sep 01, 2008 at 02:48:03PM EST, mike wrote: > Hi, I can run most of the admin apps in the root account. But for some reason Orca seems to crash quite often after I have had one opened for a short time. > For example, the login window app seems to crash Orca as does the package manager. Is this a known problem? Could you please outline how you manage to crash orca? A list of steps to take would be helpful, as I would like to reproduce this myself if possible. > One other thing. Why is it that the update manager gives a progress report when used in the root account, but in my account I get no progress report when it is downloading? The same is true when using add remove programs. The progress report is very handy, so I hope this can be corrected. If not, how about a beep instead. This is to do with GNOME's accessibility architecture. When running update-manager from your user account, the progress report is not accessible because it is running as root. Other than setting things up to allow root accessibility windows to be usable from your user account, the only way this can be changed is by changing the update-manager code to run the UI as the user, and the actual updating as root. Luke -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIxHRnjVefwtBjIM4RAjKVAKCMtJT2eK3SZhOOJ4UHxCbJZ6iLAgCgxZl6 EKEH/irjeWsYgJ6X08A90xA= =Oc78 -----END PGP SIGNATURE----- From themuso at ubuntu.com Mon Sep 8 00:42:00 2008 From: themuso at ubuntu.com (Luke Yelavich) Date: Mon, 8 Sep 2008 10:42:00 +1000 Subject: I'm having a problem with sound settings In-Reply-To: <0K6J00HT9317TO93@vms173003.mailsrvcs.net> References: <0K6J00HT9317TO93@vms173003.mailsrvcs.net> Message-ID: <20080908004200.GE10062@brainz.yelavich.home> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Sep 02, 2008 at 03:53:31AM EST, mike wrote: > Hi, I went to change the login sound and discovered that there are no choices in the sound menu. > The device menu in the sound setting still has it's menu. Has something changed in the sound settings? Or is this broken? What version of Ubuntu are you running? If intrepid, this is known, and a few issues need to be resolved regarding this. Remember, if you use intrepid and something breaks, at this stage of development, you get to keep both pieces. Luke -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIxHTYjVefwtBjIM4RAoEqAKCNK65ceI++55aMyYEE/Ae3m2CDAgCgmACg MijhSBdsgIV3tpc/zO4f+Wg= =wM+i -----END PGP SIGNATURE----- From themuso at ubuntu.com Mon Sep 8 00:43:15 2008 From: themuso at ubuntu.com (Luke Yelavich) Date: Mon, 8 Sep 2008 10:43:15 +1000 Subject: Maybe someone can answer a question about wireless networks with ubuntu In-Reply-To: <0K6J0041UIITQ7VA@vms173005.mailsrvcs.net> References: <0K6J0041UIITQ7VA@vms173005.mailsrvcs.net> Message-ID: <20080908004315.GF10062@brainz.yelavich.home> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Sep 02, 2008 at 09:28:08AM EST, mike wrote: > Hi, I can now use Orca to connect to my wireless network using the included tools. > Here is the problem I am having. My ubuntu machine connects to my router fine. But when I try to connect to a computer to computer network it will not connect. I know the key is right because my windows computers all connect fine. But for some reason the ubuntu computer won't connect. > Has anyone else experimented with this? This may have something to do with network manager, which was recently updated to 0.7. I suggest you have a look to see if anybody has reported this problem at https://launchpad.net/ubuntu/+source/network-manager/+bugs. If nobody has reported this, you may want to report it yourself. Luke -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIxHUjjVefwtBjIM4RAuSJAJ9lATpbjw688RxOAxk+imabi4eNPQCbBUti tjf8LnjeGe3Z6siXnCm4/e0= =BjKF -----END PGP SIGNATURE----- From themuso at ubuntu.com Mon Sep 8 00:44:40 2008 From: themuso at ubuntu.com (Luke Yelavich) Date: Mon, 8 Sep 2008 10:44:40 +1000 Subject: where can I download the ubuntu manual In-Reply-To: <0K6L0048EMC8Q85G@vms173005.mailsrvcs.net> References: <0K6L0048EMC8Q85G@vms173005.mailsrvcs.net> Message-ID: <20080908004440.GG10062@brainz.yelavich.home> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Sep 03, 2008 at 12:45:45PM EST, mike wrote: > Hi, There use to be a link to download the ubuntu documentation. I got a server guide and a desktop guide at that time. > But I do not see a link for downloading the guides anymore. > Does anyone know the currant link to them? On what page are you on when trying to find the link? Its likely easy enough to google for, using the terms "Ubuntu manual" you will surely find something. Luke -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIxHV4jVefwtBjIM4RAtw+AJ0S/uN2EYdOLg2qvMNiaNRLFCFLjwCcCFR3 sy8iMzi7Lu/40cMzRxY74uo= =dAAn -----END PGP SIGNATURE----- From themuso at ubuntu.com Mon Sep 8 00:50:15 2008 From: themuso at ubuntu.com (Luke Yelavich) Date: Mon, 8 Sep 2008 10:50:15 +1000 Subject: persistent brltty question at boot time while brltty already configured In-Reply-To: <20080903210930.GU3751@starfish> References: <20080903210930.GU3751@starfish> Message-ID: <20080908005015.GH10062@brainz.yelavich.home> -----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----- From themuso at ubuntu.com Mon Sep 8 00:52:42 2008 From: themuso at ubuntu.com (Luke Yelavich) Date: Mon, 8 Sep 2008 10:52:42 +1000 Subject: I'm having a problem with orca in intrepid. In-Reply-To: <0K6N001LR35HY5W5@vms046.mailsrvcs.net> References: <0K6N001LR35HY5W5@vms046.mailsrvcs.net> Message-ID: <20080908005242.GI10062@brainz.yelavich.home> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Sep 04, 2008 at 07:46:29AM EST, mike wrote: > Hi, after installing intrepid Orca worked fine. However, if I log out by using alt CTRL backspace, it starts asking me to pick a voice. Is this a known problem. Yes, when setting up intrepid on a machine last week, I experienced this problem, and intend to look into it. Note you shouldn't need to use control + alt + backspace unless GNOME/X/Orca has totally frozen, and you can't log out safely. > Also the log out menu now says in accessible. Are they using a different program for this? Again, its known. Shortcut keys still work however, so you simply need to make sure the logout window has focus, and then press alt + L to log out. Hope this helps. Luke -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIxHdajVefwtBjIM4RAogAAKCtylgaeWPZTFcOdWq2xkuVFyF+fgCgpyTw bI6WFwSg2efSkMDRfG9LTJU= =v5I3 -----END PGP SIGNATURE----- From tony.bernedal at gmail.com Tue Sep 9 17:47:59 2008 From: tony.bernedal at gmail.com (Tony Bernedal) Date: Tue, 9 Sep 2008 19:47:59 +0200 Subject: accessible install of ubuntu 8.04 server Message-ID: Hi. I want to install ubuntu 8.04 server with brltty but I can't figure out the steps to get it work. In 7.10 the install process work perfect pressing f5 and then 4, or maybe it was 5 and brltty started fine. but that don't work in 8.04. Can anyone tell me the steps to start the installer, if it is possible to use brltty with it. All the best. Tony From aeclist at candt.waitrose.com Wed Sep 10 09:38:11 2008 From: aeclist at candt.waitrose.com (alan c) Date: Wed, 10 Sep 2008 10:38:11 +0100 Subject: where can I download the ubuntu manual In-Reply-To: <0K6L0048EMC8Q85G@vms173005.mailsrvcs.net> References: <0K6L0048EMC8Q85G@vms173005.mailsrvcs.net> Message-ID: <48C79583.5080403@candt.waitrose.com> mike wrote: > Hi, There use to be a link to download the ubuntu documentation. I got a server guide and a desktop guide at that time. > But I do not see a link for downloading the guides anymore. > Does anyone know the currant link to them? > Mike. > I believe it would be https://wiki.ubuntu.com/Training and specifically https://wiki.ubuntu.com/Training?action=AttachFile&do=view&target=student-7.10.pdf However, the links do not seem to be working - fo rme anyway. Maybe I am doing something wrong -- alan cocks Kubuntu user#10391 Linux user #360648 From aeclist at candt.waitrose.com Wed Sep 10 21:10:02 2008 From: aeclist at candt.waitrose.com (alan c) Date: Wed, 10 Sep 2008 22:10:02 +0100 Subject: where can I download the ubuntu manual In-Reply-To: <48C79583.5080403@candt.waitrose.com> References: <0K6L0048EMC8Q85G@vms173005.mailsrvcs.net> <48C79583.5080403@candt.waitrose.com> Message-ID: <48C837AA.20006@candt.waitrose.com> alan c wrote: > mike wrote: >> Hi, There use to be a link to download the ubuntu documentation. I got a server guide and a desktop guide at that time. >> But I do not see a link for downloading the guides anymore. >> Does anyone know the currant link to them? >> Mike. >> > > I believe it would be > https://wiki.ubuntu.com/Training > and specifically > https://wiki.ubuntu.com/Training?action=AttachFile&do=view&target=student-7.10.pdf > > However, the links do not seem to be working - fo rme anyway. Maybe I > am doing something wrong Ah! I recall that this is also available as a torrent download (In fact I am one of the several people who are seeding this torrent) please see http://ww.mininova.org/det/1635675 and use the torrent file to get the student.pdf. If you have any questions please ask? -- alan cocks Kubuntu user#10391 Linux user #360648 From labrad0r at edpnet.be Sat Sep 13 21:39:36 2008 From: labrad0r at edpnet.be (Labrador) Date: Sat, 13 Sep 2008 23:39:36 +0200 Subject: new (fresh) reinstall test for brltty at Ubuntu (confirm: problem in Ubuntu not in brltty) Message-ID: <20080913213936.GA3615@starfish> 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. -------------- next part -------------- # Created by /lib/brltty/brltty.sh braille-driver al braille-device usb: text-table de # corrected by me -------------- next part -------------- # Created by /lib/brltty/brltty.sh braille-driver al braille-device serial:ttyUSBusb: # built by Ubuntu itself ... and completely wrong -------------- next part -------------- # 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-driver bd # Braudi #braille-driver bl # BrailleLite #braille-driver bm # Baum #braille-driver bn # BrailleNote #braille-driver cb # CombiBraille #braille-driver ec # EcoBraille #braille-driver eu # EuroBraille #braille-driver fs # FreedomScientific #braille-driver ht # HandyTech #braille-driver il # IrisLinux #braille-driver lb # Libbraille #braille-driver lt # LogText #braille-driver mb # MultiBraille #braille-driver md # MDV (protocol 5) #braille-driver mn # MiniBraille #braille-driver pm # Papenmeier #braille-driver tn # TechniBraille #braille-driver ts # TSI #braille-driver tt # TTY #braille-driver vd # VideoBraille #braille-driver vo # Voyager #braille-driver vr # Virtual #braille-driver vs # VisioBraille #braille-driver xw # XWindow # The braille-device directive specifies the device to which the braille # display is connected. The generic syntax is type:device. The device # type is optional, and, for backward compatibility, defaults to serial. # The following devices are supported (brackets indicate optionality): # serial:path (relative paths are anchored at "/dev") # usb:[serial-number] # bluetooth:address # If not specified, "usb:" will be used. # (can be overridden with the -d [--braille-device=] option) #braille-device serial: # First serial device. #braille-device usb: # First USB device matching braille driver. #braille-device usb:nnnnn # Specific USB device by serial number. #braille-device bluetooth:xx:xx:xx:xx:xx:xx # Specific bluetooth device by address. # The release-device directive specifies whether or not the device to which the # braille display is connected is to be released when the current screen or # window can't be read by BRLTTY. If not specified, "on" will be used on Windows # platforms and "off" will be used on all other platforms. # (can be overridden with the -r [--release-device] option) #release-device on # Release the device. #release-device off # Don't release the device. # The text-table directive specifies which text translation table to # use. Relative paths are anchored at "/etc/brltty". If not specified, # "$(SRC_TOP)$(TBL_DIR)/text.nabcc.tbl" will be used. # (can be overridden with the -t [--text-table=] option) #text-table cz # Czech (iso-8859-2) #text-table da # Danish #text-table de # German #text-table en_UK # English (United Kingdom) #text-table en_US # English (United States) #text-table es # Spanish #text-table fr_CA # French (Canada) #text-table fr_FR # French (France) #text-table fr-2007 # French (Unified) #text-table fr-cbifs # French (Code Braille Informatique Français Standard) #text-table it # Italian #text-table nabcc # North American Braille Computer Code #text-table no-h # Norwegian and German #text-table no-p # Norwegian #text-table pl # Polish (iso-8859-2) #text-table pt # Portuguese (iso-8859-1) #text-table ru # Russian (koi8-r) #text-table se # Swedish (1996 standard) #text-table se-old # Swedish (1989 standard) #text-table vni # Vietnamese # The attributes-table directive specifies which attributes translation # table to use. Relative paths are anchored at "/etc/brltty". If not # specified, "$(SRC_TOP)$(TBL_DIR)/attributes.tbl" will be used. # (can be overridden with the -a [--attributes-table=] option) #attributes-table attributes.tbl # #attributes-table attrib.tbl # # The contraction-table directive specifies which braille contraction # table to use. Relative paths are anchored at "/etc/brltty". If not # specified, no contraction table will be available. # (can be overridden with the -c [--contraction-table=] option) #contraction-table compress # Remove excess white space. #contraction-table en-uebc-g2 # Grade 2 Unified English Braille Code #contraction-table en-us-g2 # Grade 2 American English #contraction-table fr-abrege # Contracted French #contraction-table fr-integral # Uncontracted French #contraction-table zh-tw-big5 # Taiwanese Chinese (using BIG5 characters) #contraction-table zh-tw-gb2312 # Taiwanese Simplified Chinese #contraction-table zh-tw-ucb # Taiwanese Unique Chinese Braille #contraction-table zh-tw-utf8 # Taiwanese Chinese (using UTF-8 characters) ############################# # Braille Driver Parameters # ############################# # The braille-parameters directive passes non-generic parameters through # to the braille driver. # (can be overridden with the -B [--braille-parameters=] option) #braille-parameters driver:parameter=setting,... # BrlAPI Braille Driver Parameters #braille-parameters ba:Auth=/etc/brlapi.key #braille-parameters ba:Host=:0 # BrailleLite Braille Driver Parameters #braille-parameters bl:BaudRate=9600 # [300,600,1200,2400,4800,9600,19200,38400] #braille-parameters bl:KbEmu=yes # [yes,no] # Baum Braille Driver Parameters #braille-parameters bm:Protocols=default # [default,all,native] #braille-parameters bm:VarioKeys=no # [no,yes] # BrailleNote Braille Driver Parameters #braille-parameters bn:StatusCells=0 # FreedomScientific Braille Driver Parameters #braille-parameters fs:DebugPackets=no # [no,yes] #braille-parameters fs:StatusCells= # [0,n,-n] # HandyTech Braille Driver Parameters #braille-parameters ht:InputMode=no # [no,yes] # Libbraille Braille Driver Parameters #braille-parameters lb:Device=/dev/ttyS0 # #braille-parameters lb:Driver=auto # #braille-parameters lb:Table=us.tbl # # Papenmeier Braille Driver Parameters #braille-parameters pm:ConfigFile=/etc/brltty/brltty-pm.conf #braille-parameters pm:DebugKeys=no # [no,yes] #braille-parameters pm:DebugReads=no # [no,yes] #braille-parameters pm:DebugWrites=no # [no,yes] # TTY Braille Driver Parameters #braille-parameters tt:Baud=9600 # #braille-parameters tt:CharSet=ISO8859-1 # #braille-parameters tt:Columns=40 # [1-80] #braille-parameters tt:Lines=1 # [1-3] #braille-parameters tt:Locale= # #braille-parameters tt:Term=vt100 # [terminfo] # VisioBraille Braille Driver Parameters #braille-parameters vs:Baud=57600 # #braille-parameters vs:DisplaySize=40 # [20-40] #braille-parameters vs:PromVersion=4 # [3-6] # Voyager Braille Driver Parameters #braille-parameters vo:InputMode=no # [no,yes] #braille-parameters vo:StatusCells=3 # [0,n,-n] # XWindow Braille Driver Parameters #braille-parameters xw:Columns=40 # [1-80] #braille-parameters xw:Input=off # [off,on] #braille-parameters xw:Lines=1 # [1-3] #braille-parameters xw:Model=bare # [bare] #braille-parameters xw:TkParms= # ########################### # Generic Speech Settings # ########################### # The speech-driver directive specifies the two-letter driver # identification code of the driver for the speech synthesizer. # If not specified, autodetection will be performed. # (can be overridden with the -s [--speech-driver=] option) #speech-driver auto # autodetect #speech-driver al # Alva #speech-driver bl # BrailleLite #speech-driver cb # CombiBraille #speech-driver es # ExternalSpeech (executes /usr/local/bin/externalspeech) #speech-driver fl # FestivalLite (text to speech engine) #speech-driver fv # Festival (text to speech engine) #speech-driver gs # GenericSay (pipes to /usr/local/bin/say) #speech-driver mp # Mikropuhe (text to speech engine) #speech-driver sd # SpeechDispatcher (text to speech server) #speech-driver sw # Swift (text to speech engine) #speech-driver th # Theta (text to speech engine) #speech-driver vv # ViaVoice (text to speech engine) # The speech-fifo directive specifies the path to the FIFO used by the speech # pass-through facility. Relative paths are anchored at "/etc/brltty". # If not specified, the speech pass-through facility isn't enabled. # (can be overridden with the -F [--speech-fifo=] option) #speech-fifo spk ############################ # Speech Driver Parameters # ############################ # The speech-parameters directive passes non-generic parameters through # to the speech driver. # (can be overridden with the -S [--speech-parameters=] option) #speech-parameters driver:parameter=setting,... # ExternalSpeech Speech Driver Parameters #speech-parameters es:Program=/usr/local/bin/externalspeech #speech-parameters es:Uid=65534 #speech-parameters es:Gid=65534 # Festival Speech Driver Parameters #speech-parameters fv:Command=festival # [/path/to/command] #speech-parameters fv:Name= # [kevin,kal] # FestivalLite Speech Driver Parameters #speech-parameters fl:Pitch=100 # [50-200] # GenericSay Speech Driver Parameters #speech-parameters gs:Command=/usr/local/bin/say # Mikropuhe Speech Driver Parameters #speech-parameters mp:Name= # [/path/to/mikropuhe/name.pu5] #speech-parameters mp:Pitch=0 # [-10-10] # SpeechDispatcher Speech Driver Parameters #speech-parameters sd:Language= # [two-letter language code] #speech-parameters sd:Module= # [flite,festival,epos-generic,dtk-generic,...] #speech-parameters sd:Port=6560 # [1-65535] # [1-65535] #speech-parameters sd:Voice= # [male1,female1,male2,female2,male3,female3,child_male,child_female] # Swift Speech Driver Parameters #speech-parameters sw:Name= # [voice,/path/to/voice] # Theta Speech Driver Parameters #speech-parameters th:Age= # [1-99,-1--99] #speech-parameters th:Gender= # [male,female,neuter] #speech-parameters th:Language= # [two-letter language code] #speech-parameters th:Name= # [voice,/path/to/voice] #speech-parameters th:Pitch=0.0 # [-2.0-2.0] # ViaVoice Speech Driver Parameters #speech-parameters vv:IniFile=/usr/lib/ViaVoiceTTS/eci.ini #speech-parameters vv:SampleRate= # [8000,11025,22050] #speech-parameters vv:AbbreviationMode= # [on,off] #speech-parameters vv:NumberMode= # [word,year] #speech-parameters vv:SynthMode= # [sentence,none] #speech-parameters vv:TextMode= # [talk,spell,literal,phonetic] #speech-parameters vv:Language= # [AmericanEnglish,BritishEnglish,CastilianSpanish,MexicanSpanish,StandardFrench,CanadianFrench,StandardGerman,StandardItalian,SimplifiedChinese,BrazilianPortuguese] #speech-parameters vv:Voice= # [AdultMale,AdultFemale,Child,ElderlyFemale,ElderlyMale] #speech-parameters vv:VocalTract= # [male,female] #speech-parameters vv:Breathiness= # [0-100] #speech-parameters vv:HeadSize= # [0-100] #speech-parameters vv:PitchBaseline= # [0-100] #speech-parameters vv:PitchFluctuation= # [0-100] #speech-parameters vv:Roughness= # [0-100] ################## # Sound Settings # ################## # The pcm-device directive specifies the device to use for soundcard # digital audio. If not specified, a method- and system-dependent # default will be used. # (can be overridden with the -p [--pcm-device=] option) #pcm-device /path/to/device # most methods #pcm-device pcm-handle-id # ALSA (see second parameter of snd_pcm_open) # The pcm-device directive specifies the device to use for the Musical # Instrument Digital Interface. If not specified, a method- and # system-dependent default will be used. # (can be overridden with the -m [--midi-device=] option) #midi-device /path/to/device # most methods #midi-device client:port # ALSA (may use number or case-sensitive substring of name) ########################## # Miscellaneous Settings # ########################## # The library-directory directive specifies the absolute path to the # directory which contains the dynamically loadable drivers. If not # specified, /lib/brltty will be used. # (can be overridden with the -L [--library-directory=] option) #library-directory /lib/brltty # The writable-directory directive specifies the absolute path to a directory # which can be written to (creation of missing but needed resources, etc). If # not specified, "/lib/brltty/rw" will be used. # (can be overridden with the -W [--writable-directory=] option) #writable-directory /lib/brltty/rw # The data-directory directive specifies the absolute path to the directory # which contains driver data files (help files, configuration files, etc.). If # not specified, "/etc/brltty" will be used. # (can be overridden with the -D [--data-directory=] option) #data-directory /etc/brltty # The tables-directory directive specifies the absolute path to the directory # which contains the text and attributes tables. If not specified, # "/etc/brltty" will be used. # (can be overridden with the -T [--tables-directory=] option) #tables-directory /etc/brltty # The contractions-directory directive specifies the absolute path to the # directory which contains the contraction tables. If not specified, # "/etc/brltty" will be used. # (can be overridden with the -C [--contractions-directory=] option) #contractions-directory /etc/brltty ################################################ # Application Programming Interface Parameters # ################################################ # The api-parameters directive passes parameters to the Application # Programming Interface. # (can be overridden with the -A [--api-parameters=] option) #api-parameters parameter=setting,... #api-parameters Auth=/etc/brlapi.key #api-parameters Host=:0 #api-parameters StackSize=65536 ########################### # Generic Screen Settings # ########################### # The screen-driver directive specifies the two-letter driver # identification code of the driver for the console screen. # (can be overridden with the -x [--screen-driver=] option) #screen-driver as # AtSpi #screen-driver pb # PCBIOS #screen-driver hd # Hurd #screen-driver lx # Linux #screen-driver sc # Screen #screen-driver wn # Windows ############################ # Screen Driver Parameters # ############################ # The screen-parameters directive passes non-generic parameters through # to the screen driver. # (can be overridden with the -X [--screen-parameters=] option) #screen-parameters driver:parameter=setting,... # AtSpi Screen Driver Parameters #screen-parameters as:Type=text+terminal # [text,terminal,all] # Linux Screen Driver Parameters #screen-parameters lx:Acm=auto # [auto,iso01,vt100,cp437,user] #screen-parameters lx:DebugAcm=no # [no,yes] #screen-parameters lx:DebugSfm=no # [no,yes] #screen-parameters lx:DebugCtt=no # [no,yes] #screen-parameters lx:Hfb=auto # [auto,vga,fb,0-7] # Windows Screen Driver Parameters #screen-parameters wn:Root=no # [no,yes] -------------- next part -------------- # menu.lst - See: grub(8), info grub, update-grub(8) # grub-install(8), grub-floppy(8), # grub-md5-crypt, /usr/share/doc/grub # and /usr/share/doc/grub-doc/. ## default num # Set the default entry to the entry number NUM. Numbering starts from 0, and # the entry number 0 is the default if the command is not used. # # You can specify 'saved' instead of a number. In this case, the default entry # is the entry saved with the command 'savedefault'. # WARNING: If you are using dmraid do not use 'savedefault' or your # array will desync and will not let you boot your system. default 0 ## timeout sec # Set a timeout, in SEC seconds, before automatically booting the default entry # (normally the first entry defined). timeout 10 ## hiddenmenu # Hides the menu by default (press ESC to see the menu) #hiddenmenu # Pretty colours #color cyan/blue white/blue ## password ['--md5'] passwd # If used in the first section of a menu file, disable all interactive editing # control (menu entry editor and command-line) and entries protected by the # command 'lock' # e.g. password topsecret # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/ # password topsecret # # examples # # title Windows 95/98/NT/2000 # root (hd0,0) # makeactive # chainloader +1 # # title Linux # root (hd0,1) # kernel /vmlinuz root=/dev/hda2 ro # # # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST ### BEGIN AUTOMAGIC KERNELS LIST ## lines between the AUTOMAGIC KERNELS LIST markers will be modified ## by the debian update-grub script except for the default options below ## DO NOT UNCOMMENT THEM, Just edit them to your needs ## ## Start Default Options ## ## default kernel options ## default kernel options for automagic boot options ## If you want special options for specific kernels use kopt_x_y_z ## where x.y.z is kernel version. Minor versions can be omitted. ## e.g. kopt=root=/dev/hda1 ro ## kopt_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root=UUID=c86895ce-0e3c-4f62-92b9-6f4d0574c085 ro ## Setup crashdump menu entries ## e.g. crashdump=1 # crashdump=0 ## default grub root device ## e.g. groot=(hd0,0) # groot=(hd0,1) ## should update-grub create alternative automagic boot options ## e.g. alternative=true ## alternative=false # alternative=true ## should update-grub lock alternative automagic boot options ## e.g. lockalternative=true ## lockalternative=false # lockalternative=false ## additional options to use with the default boot option, but not with the ## alternatives ## e.g. defoptions=vga=791 resume=/dev/hda5 # defoptions=quiet splash braille=ask ## should update-grub lock old automagic boot options ## e.g. lockold=false ## lockold=true # lockold=false ## Xen hypervisor options to use with the default Xen boot option # xenhopt= ## Xen Linux kernel options to use with the default Xen boot option # xenkopt=console=tty0 ## altoption boot targets option ## multiple altoptions lines are allowed ## e.g. altoptions=(extra menu suffix) extra boot options ## altoptions=(recovery) single # altoptions=(recovery mode) single ## controls how many kernels should be put into the menu.lst ## only counts the first occurence of a kernel, not the ## alternative kernel options ## e.g. howmany=all ## howmany=7 # howmany=all ## should update-grub create memtest86 boot option ## e.g. memtest86=true ## memtest86=false # memtest86=true ## should update-grub adjust the value of the default booted system ## can be true or false # updatedefaultentry=false ## should update-grub add savedefault to the default options ## can be true or false # savedefault=false ## ## End Default Options ## title Ubuntu 8.04.1, kernel 2.6.24-19-generic  root (hd0,1) kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=c86895ce-0e3c-4f62-92b9-6f4d0574c085 ro quiet splash initrd /boot/initrd.img-2.6.24-19-generic quiet title Ubuntu 8.04.1, kernel 2.6.24-19-generic (recovery mode) root (hd0,1) kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=c86895ce-0e3c-4f62-92b9-6f4d0574c085 ro single initrd /boot/initrd.img-2.6.24-19-generic title Ubuntu 8.04.1, memtest86+ root (hd0,1) kernel /boot/memtest86+.bin quiet ### END DEBIAN AUTOMAGIC KERNELS LIST # This is a divider, added to separate the menu items below from the Debian # ones. title Other operating systems: root # This entry automatically added by the Debian installer for a non-linux OS # on /dev/sda1 title Microsoft Windows XP Professional root (hd0,0) savedefault makeactive chainloader +1 -------------- next part -------------- # menu.lst - See: grub(8), info grub, update-grub(8) # grub-install(8), grub-floppy(8), # grub-md5-crypt, /usr/share/doc/grub # and /usr/share/doc/grub-doc/. ## default num # Set the default entry to the entry number NUM. Numbering starts from 0, and # the entry number 0 is the default if the command is not used. # # You can specify 'saved' instead of a number. In this case, the default entry # is the entry saved with the command 'savedefault'. # WARNING: If you are using dmraid do not use 'savedefault' or your # array will desync and will not let you boot your system. default 0 ## timeout sec # Set a timeout, in SEC seconds, before automatically booting the default entry # (normally the first entry defined). timeout 10 ## hiddenmenu # Hides the menu by default (press ESC to see the menu) #hiddenmenu # Pretty colours #color cyan/blue white/blue ## password ['--md5'] passwd # If used in the first section of a menu file, disable all interactive editing # control (menu entry editor and command-line) and entries protected by the # command 'lock' # e.g. password topsecret # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/ # password topsecret # # examples # # title Windows 95/98/NT/2000 # root (hd0,0) # makeactive # chainloader +1 # # title Linux # root (hd0,1) # kernel /vmlinuz root=/dev/hda2 ro # # # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST ### BEGIN AUTOMAGIC KERNELS LIST ## lines between the AUTOMAGIC KERNELS LIST markers will be modified ## by the debian update-grub script except for the default options below ## DO NOT UNCOMMENT THEM, Just edit them to your needs ## ## Start Default Options ## ## default kernel options ## default kernel options for automagic boot options ## If you want special options for specific kernels use kopt_x_y_z ## where x.y.z is kernel version. Minor versions can be omitted. ## e.g. kopt=root=/dev/hda1 ro ## kopt_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root=UUID=c86895ce-0e3c-4f62-92b9-6f4d0574c085 ro ## Setup crashdump menu entries ## e.g. crashdump=1 # crashdump=0 ## default grub root device ## e.g. groot=(hd0,0) # groot=(hd0,1) ## should update-grub create alternative automagic boot options ## e.g. alternative=true ## alternative=false # alternative=true ## should update-grub lock alternative automagic boot options ## e.g. lockalternative=true ## lockalternative=false # lockalternative=false ## additional options to use with the default boot option, but not with the ## alternatives ## e.g. defoptions=vga=791 resume=/dev/hda5 # defoptions=quiet splash braille=ask ## should update-grub lock old automagic boot options ## e.g. lockold=false ## lockold=true # lockold=false ## Xen hypervisor options to use with the default Xen boot option # xenhopt= ## Xen Linux kernel options to use with the default Xen boot option # xenkopt=console=tty0 ## altoption boot targets option ## multiple altoptions lines are allowed ## e.g. altoptions=(extra menu suffix) extra boot options ## altoptions=(recovery) single # altoptions=(recovery mode) single ## controls how many kernels should be put into the menu.lst ## only counts the first occurence of a kernel, not the ## alternative kernel options ## e.g. howmany=all ## howmany=7 # howmany=all ## should update-grub create memtest86 boot option ## e.g. memtest86=true ## memtest86=false # memtest86=true ## should update-grub adjust the value of the default booted system ## can be true or false # updatedefaultentry=false ## should update-grub add savedefault to the default options ## can be true or false # savedefault=false ## ## End Default Options ## title Ubuntu 8.04.1, kernel 2.6.24-19-generic root (hd0,1) kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=c86895ce-0e3c-4f62-92b9-6f4d0574c085 ro quiet splash braille=ask initrd /boot/initrd.img-2.6.24-19-generic quiet title Ubuntu 8.04.1, kernel 2.6.24-19-generic (recovery mode) root (hd0,1) kernel /boot/vmlinuz-2.6.24-19-generic root=UUID=c86895ce-0e3c-4f62-92b9-6f4d0574c085 ro single initrd /boot/initrd.img-2.6.24-19-generic title Ubuntu 8.04.1, memtest86+ root (hd0,1) kernel /boot/memtest86+.bin quiet ### END DEBIAN AUTOMAGIC KERNELS LIST # This is a divider, added to separate the menu items below from the Debian # ones. title Other operating systems: root # This entry automatically added by the Debian installer for a non-linux OS # on /dev/sda1 title Microsoft Windows XP Professional root (hd0,0) savedefault makeactive chainloader +1 From kb8aey at verizon.net Mon Sep 15 01:22:43 2008 From: kb8aey at verizon.net (mike) Date: Sun, 14 Sep 2008 20:22:43 -0500 (CDT) Subject: has anyone had problems with the configuration server in intrepid? Message-ID: <0K7700A6OQHV03LD@vms044.mailsrvcs.net> Hi, I am getting a message after I enter my password that says there is a problem with the configuration server. Pressing enter again causes this message to go away, and everything works fine. Has anyone else had this problem in intrepid. I did install some plug ins, and think this is when the message came. But, uninstalling the plug ins didn't correct the problem. The wireless network is the only difference between that computer and the other one I have intrepid on. But the wireless seems to work fine once the system loads. Mike. From themuso at ubuntu.com Mon Sep 15 01:36:28 2008 From: themuso at ubuntu.com (Luke Yelavich) Date: Mon, 15 Sep 2008 11:36:28 +1000 Subject: has anyone had problems with the configuration server in intrepid? In-Reply-To: <0K7700A6OQHV03LD@vms044.mailsrvcs.net> References: <0K7700A6OQHV03LD@vms044.mailsrvcs.net> Message-ID: <20080915013628.GA30409@brainz.yelavich.home> On Mon, Sep 15, 2008 at 11:22:43AM EST, mike wrote: > Hi, I am getting a message after I enter my password that says there is a problem with the configuration server. Pressing enter again causes this message to go away, and everything works fine. > Has anyone else had this problem in intrepid. I did install some plug ins, and think this is when the message came. But, uninstalling the plug ins didn't correct the problem. > The wireless network is the only difference between that computer and the other one I have intrepid on. But the wireless seems to work fine once the system loads. Unfrotunately I need a bit more information to try and work out exactly what you are talking about. When you are logging in, are you talking about logging into GNOME? If so, I think I know what you are talking about regarding the configuration server, and no, I haven't seen it before. The only thing I can suggest, is deleting all .gconf and .gnome2 related directories from your home directory. You will have to re-enable accessibility after doing this however. Luke From kb8aey at verizon.net Mon Sep 15 01:56:54 2008 From: kb8aey at verizon.net (mike) Date: Sun, 14 Sep 2008 20:56:54 -0500 (CDT) Subject: I found the configuration problem, this may be of interest to others. Message-ID: <0K770047XS2TR00C@vms173003.mailsrvcs.net> Hi Luke and List. I just found the problem with the configuration server. Luke, I remembered that I tried a feature I saw in Orca in the root account. Orca now has it's own box you can check to have it start when you login. I did this in the root account, but not in my account because I had speech enabled when I installed intrepid. Anyway, wondering if that was the problem, I unchecked that box in Orca in the root account. Guess what? The problem went away. The strange thing is this happened on my laptop. But I also have the login box in Orca checked in the root account on my desktop and have had no problems. The only thing I can think of is the installation on the laptop was done using a older live CD. But I do have all updates. Anyway, apparently the check box in Orca can cause problems. By the way, I never did get that message when logging in to the root account. Mike. From christian08 at runbox.com Mon Sep 15 12:10:38 2008 From: christian08 at runbox.com (Christian) Date: Mon, 15 Sep 2008 14:10:38 +0200 Subject: Making the CD boot menu more accessible Message-ID: <200809151410380484.00074813@127.0.0.1> Hi all, I think this has already been discussed before, but just wanted to hear if there are any planns to make the CD boot menu more accessible? It would be nice if there was a beep telling the user that the CD has finished booting and its ready to take user input. Normally I have been able to boot the CD but on different machines I haave been waiting too long or been too fast. What do you all think? All the best, Christian From christian08 at runbox.com Mon Sep 15 12:13:05 2008 From: christian08 at runbox.com (Christian) Date: Mon, 15 Sep 2008 14:13:05 +0200 Subject: Problems with the console in Intrepid Message-ID: <200809151413050671.00098706@127.0.0.1> Hi all, If I press Ctrl-Alt-F1 to bring up the first console I only get dots on my braille display. I don't have Intrepid installed right now, but when I tried it I had this problem. Has something been changed? I don't see this in Hardy where it's working fine. Many thanks, Christian From christian08 at runbox.com Wed Sep 17 10:16:44 2008 From: christian08 at runbox.com (Christian) Date: Wed, 17 Sep 2008 12:16:44 +0200 Subject: Making the CD boot menu more accessible In-Reply-To: <48CF037C.9080308@gmail.com> References: <200809151410380484.00074813@127.0.0.1> <48CF037C.9080308@gmail.com> Message-ID: <200809171216440484.0028B61E@127.0.0.1> Yes, that would be a very nice thing to have. But some kind of notification that the CD has finished booting at least would be apreciated. All the best, Christian On 2008-09-15 at 19:53 Mike Reiser wrote: >I agree, and maybe a talking boot menu like in open suse? > >Mike From labrad0r at edpnet.be Wed Sep 17 14:40:43 2008 From: labrad0r at edpnet.be (Labrador) Date: Wed, 17 Sep 2008 16:40:43 +0200 Subject: Making the CD boot menu more accessible In-Reply-To: <200809171216440484.0028B61E@127.0.0.1> References: <200809151410380484.00074813@127.0.0.1> <48CF037C.9080308@gmail.com> <200809171216440484.0028B61E@127.0.0.1> Message-ID: <20080917144043.GC3182@starfish> On Wed, Sep 17, 2008 at 12:16:44PM +0200, Christian wrote: > Yes, that would be a very nice thing to have. But some kind of notification that the CD has finished booting at least would be apreciated. > All the best, > Christian > Hi, as I said in a previous mail I posted privately: do fix first and brainstorm later! I mean: its 3 times I install an Ubuntu, and three time I got the same problems: - braille=ask in grub's menu.lst to remove - /etc/brltty.conf to re-edit and remove the nonsense params who are dropped there - or activating braille to have it at boot time This is a problem I personally will see fixed before making plans around any other kind of ideas. I had never got such problems with Debian's Etch installer, nor Blindia (a little alternate Sarge installer). Please fix problems first, I'm tired to see permanently having problems since Feisty, Gutsy then now Hardy. I'm also tired to need a sighted person each time I have to install Ubuntu. L. From esj at harvee.org Thu Sep 18 12:57:40 2008 From: esj at harvee.org (Eric S. Johansson) Date: Thu, 18 Sep 2008 08:57:40 -0400 Subject: support for speech recognition Message-ID: <48D25044.4020001@harvee.org> NaturallySpeaking 10 is working reasonably well under wine (if you use the bleeding edge git code). I have some ideas on how to bridge the barrier between linux and wine but I'd like to learn what facilities are native in the current gnome accessibility toolkit. The last time I read the documentation, it was almost entirely focused on the visually impaired. If I've misinterpreted the documentation, I'd like to learn where I went wrong. Thanks ---eric From s.bienlein at gmx.de Thu Sep 18 15:52:53 2008 From: s.bienlein at gmx.de (Simon Bienlein) Date: Thu, 18 Sep 2008 17:52:53 +0200 Subject: Questions about Intrepid Ibex Message-ID: <00f501c919a6$9cec30c0$6401a8c0@simonlaptop> Hi everyone, I am interested in the upcoming Ubuntu release and I have got some questions about it. Will the brltty boot parameter not be evaluated anymore? I already noticed about the Ubuntu version 8.04 that the indication is not being evaluated. BrlTTY is not started although I entered the brltty parameter at the boot prompt. If I start BrlTTy manually it does not work on the console. If I switch to a console by pressing Strg+Alt+F1, nothing is being shown on the Braille display. Do these problems continue in Intrepid? Another note about the orca setup: the available options are being read by the voice output. However, one cannot interrupt the voice. This is especially impractical with long lists as one can have already entered his/her choice but still has to wait for the end of the list. If one installs Ubuntu with a Braille display, it should be secured that BrlTTY is being started while booting. Especially for beginners it is unpleasant if they are left without a Braille display right after the installation and are possibly dependent on help from someone who can see. Especially the alternate install CD offers a great support of Braille, but it is a pity if one is able to install the system software independently but then already meets the first obstacles. I would appreciate it if these problems would be fixed in the final version. Thanks in advance for your help. Simon From kb8aey at verizon.net Sun Sep 21 23:20:11 2008 From: kb8aey at verizon.net (mike) Date: Sun, 21 Sep 2008 18:20:11 -0500 (CDT) Subject: I'm having trouble getting to the top panel. Message-ID: <0K7K005Y1JGXP3L3@vms046.mailsrvcs.net> Hi I did something in one of my intrepid installations, and now I can't get to the top panel by pressing CTRL alt tab. Does anyone have any ideas? I did play with the appearance settings, and one of them doesn't show up anymore. Mike. From William.Walker at Sun.COM Sun Sep 21 23:41:10 2008 From: William.Walker at Sun.COM (Willie Walker) Date: Sun, 21 Sep 2008 19:41:10 -0400 Subject: I'm having trouble getting to the top panel. In-Reply-To: <0K7K005Y1JGXP3L3@vms046.mailsrvcs.net> References: <0K7K005Y1JGXP3L3@vms046.mailsrvcs.net> Message-ID: <48D6DB96.6060006@sun.com> Compiz doesn't seem to support Ctrl+Alt+Tab to get to the top panel. If you've accidentally enabled Compiz, you need to get back to metacity. One way to do this is go to the "Visual Effects" tab of the appearance settings and select "None". Will mike wrote: > Hi I did something in one of my intrepid installations, and now I can't get to the top panel by pressing CTRL alt tab. > Does anyone have any ideas? I did play with the appearance settings, and one of them doesn't show up anymore. > Mike. > From kb8aey at verizon.net Mon Sep 22 15:48:55 2008 From: kb8aey at verizon.net (mike) Date: Mon, 22 Sep 2008 10:48:55 -0500 (CDT) Subject: compiz Message-ID: <0K7L00A02T9JX304@vms042.mailsrvcs.net> Hi, I turned compiz on by mistake. Does anyone know how to turn it off? The setting I was experimenting with in appearance no longer has any choices since I did this. Mike. From kristian at bohemians.org Mon Sep 22 16:00:10 2008 From: kristian at bohemians.org (=?UTF-8?Q?Kristian_Lyngst=C3=B8l?=) Date: Mon, 22 Sep 2008 18:00:10 +0200 Subject: compiz In-Reply-To: <0K7L00A02T9JX304@vms042.mailsrvcs.net> References: <0K7L00A02T9JX304@vms042.mailsrvcs.net> Message-ID: <6c4f32ea0809220900k56fbdfceue0dfef9bec0c4a24@mail.gmail.com> On Mon, Sep 22, 2008 at 5:48 PM, mike wrote: > Hi, I turned compiz on by mistake. Does anyone know how to turn it off? The setting I was experimenting with in appearance no longer has any choices since I did this. Should be a matter of setting "Visual Effects" in appearance to None. Are you saying this setting is gone? A temporary solution is to start metacity from a terminal with 'metacity --replace'... - Kristian From rkcole72984 at gmail.com Mon Sep 22 19:45:07 2008 From: rkcole72984 at gmail.com (Robert Cole) Date: Mon, 22 Sep 2008 12:45:07 -0700 Subject: compiz In-Reply-To: <0K7L00A02T9JX304@vms042.mailsrvcs.net> References: <0K7L00A02T9JX304@vms042.mailsrvcs.net> Message-ID: <48D7F5C3.7000806@gmail.com> An HTML attachment was scrubbed... URL: From kb8aey at verizon.net Fri Sep 26 15:55:51 2008 From: kb8aey at verizon.net (mike) Date: Fri, 26 Sep 2008 10:55:51 -0500 (CDT) Subject: How do I get speech-dispatcher to work in intrepid? Message-ID: <0K7T001CL88Y5MX3@vms173001.mailsrvcs.net> Hi, I installed speech-dispatcher in intrepid, and added it to sessions. But I do not see it as a choice in the Orca menu. How do I get it to work? Or is speech-dispatcher not working in intrepid? Mike. From cerha at brailcom.org Fri Sep 26 17:11:12 2008 From: cerha at brailcom.org (Tomas Cerha) Date: Fri, 26 Sep 2008 19:11:12 +0200 Subject: How do I get speech-dispatcher to work in intrepid? In-Reply-To: <0K7T001CL88Y5MX3@vms173001.mailsrvcs.net> References: <0K7T001CL88Y5MX3@vms173001.mailsrvcs.net> Message-ID: <48DD17B0.1050608@brailcom.org> mike napsal(a): > Hi, I installed speech-dispatcher in intrepid, and added it to sessions. But I do not see it as a choice in the Orca menu. Hello Mike, you also need the python-speechd package. Also see http://live.gnome.org/Orca/SpeechDispatcher for troubleshooting tips. Regards, Tomas From kb8aey at verizon.net Fri Sep 26 18:38:16 2008 From: kb8aey at verizon.net (mike) Date: Fri, 26 Sep 2008 13:38:16 -0500 (CDT) Subject: OPEN OFFICE Message-ID: <0K7T001TAFRR6694@vms173001.mailsrvcs.net> Hi, does anyone have a link for the open office 3 beta? I am assuming this can be installed in intrepid and should work better with Orca. Mike. From eheil at sdf.lonestar.org Fri Sep 26 19:36:04 2008 From: eheil at sdf.lonestar.org (Erik Heil) Date: Fri, 26 Sep 2008 15:36:04 -0400 (EDT) Subject: OPEN OFFICE In-Reply-To: <0K7T001TAFRR6694@vms173001.mailsrvcs.net> References: <0K7T001TAFRR6694@vms173001.mailsrvcs.net> Message-ID: Hi their. I don't see any reason why the new Openoffice.org wont' work with the new and upcoming version of Ubuntu. Some helpful notes though that may make you're experience a bit smoother. Note that I don't run Ubuntu at all at present on amy of my machines, but the advice applies to all distros that are managed by a package management system. You will want to install into some place like /opt. That way it will not be hard at all to maintain two different versions of openoffice.org. Next it is very important to get a statically compiled version of openoffice.org 3.0. The reason is that runtime dependencies may have changed and they might not be in Ubuntu's reposirities. When Openoffice.org 3.0 becomes stable, it will be a trivial task to remove you're local version and install it via you're distrobution's packagement management system. Also, it may be more well integrated than the stock binaries. i.e. Ubuntu-specific patches that may not be committed upstream. On Fri, 26 Sep 2008, mike wrote: > Date: Fri, 26 Sep 2008 13:38:16 -0500 (CDT) > From: mike > To: ubuntu > Subject: OPEN OFFICE > > Hi, does anyone have a link for the open office 3 beta? I am assuming this can be installed in intrepid and should work better with Orca. > Mike. > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > eheil at sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org From kb8aey at verizon.net Sat Sep 27 18:23:41 2008 From: kb8aey at verizon.net (mike) Date: Sat, 27 Sep 2008 13:23:41 -0500 (CDT) Subject: I Need some info on harddrives Message-ID: <0K7V00GL09RHWRNZ@vms173005.mailsrvcs.net> Hi, I know this is a little off topic, but maybe someone out there can give me some ideas. Ubuntu and Orca helped me out again today, but I have never ran into this before. A friend had a new dell computer with windows vista. He wants to use windows xp instead. The problem I ran into was that when the windows xp disk boots, it says it can't find a hard drive in the computer. The drive is a 320 gb drive. So, I booted intrepid, and it finds the drive with no problems. Using Orca and cfdisk I had no problems removing the partitions. But windows xp still says it can't find a hard drive. Maybe I can convince him to use ubuntu instead. But has anyone else ever ran into this before? I even tried partitioning the drive using ubuntu in to small partitions, because I have heard there is a limit on the size drive windows xp will see. But that didn't work either. This brings up another thing. Is there a limit on the size hard drive ubuntu can see? Mike. From aeclist at candt.waitrose.com Sat Sep 27 20:45:26 2008 From: aeclist at candt.waitrose.com (alan c) Date: Sat, 27 Sep 2008 21:45:26 +0100 Subject: I Need some info on harddrives In-Reply-To: <0K7V00GL09RHWRNZ@vms173005.mailsrvcs.net> References: <0K7V00GL09RHWRNZ@vms173005.mailsrvcs.net> Message-ID: <48DE9B66.6030600@candt.waitrose.com> mike wrote: > Hi, I know this is a little off topic, but maybe someone out there can give me some ideas. Ubuntu and Orca helped me out again today, but I have never ran into this before. > A friend had a new dell computer with windows vista. He wants to use windows xp instead. The problem I ran into was that when the windows xp disk boots, it says it can't find a hard drive in the computer. The drive is a 320 gb drive. > So, I booted intrepid, and it finds the drive with no problems. Using Orca and cfdisk I had no problems removing the partitions. But windows xp still says it can't find a hard drive. > Maybe I can convince him to use ubuntu instead. But has anyone else ever ran into this before? I even tried partitioning the drive using ubuntu in to small partitions, because I have heard there is a limit on the size drive windows xp will see. But that didn't work either. This brings up another thing. Is there a limit on the size hard drive ubuntu can see? > Mike. What comes to mind is something to do with the bios. Examine th ebios setup screens to verify th ebios can see and recognise the HD? If it is a bios (an old machine?? but this is a new machine!) where the bios can only recognise HDs of up to a certain size, then even if you installed ubuntu it could not boot from the HD because the bios - which kicks things off initially, could not see the HD containing the booting partition. I have had this type of prob with older machines so I retained the old 10GB HD for booting - only a small booting partition is needed - and used a 320GB HD for the rest of the installation including the system partition/s. I am not sure if this could be to do with the problem you see though. hth good luck -- alan cocks Kubuntu user#10391 Linux user #360648 From stormdragon2976 at gmail.com Mon Sep 29 22:54:56 2008 From: stormdragon2976 at gmail.com (Storm Dragon) Date: Mon, 29 Sep 2008 18:54:56 -0400 Subject: Upgrade to Intrepid Alpha6 Message-ID: <1222728896.11813.11.camel@stormdragon-laptop> Hi, I upgraded to Intrepid last night. The strange thing is, I ended up having to manually upgrade ubuntu-desktop and gnome-orca after everything was finished. I am not sure why they didn't upgrade along with everything else. So far, everything is working great except Orca seems to skip somethings when arrowing through menus at first, I thought I was just hitting the button twice, but it happens more often than would account for something like that. Also, was wondering if the log in music has changed for Ubuntu? It almost seems like I am getting the standard Gnome music but I am not sure. Storm -------------- next part -------------- An HTML attachment was scrubbed... URL: