Re: kde install accessibility experience
I've read a message on another list tonight that kccm needs to be run in a terminal and the accessibility box needs to be checked before it is shut down. There was something else that needed starting so gpg would work too. Some stuff works once all of this is done but kmail does not yet talk. On Sat, 14 Jan 2017, Keith Bainbridge wrote: Date: Sat, 14 Jan 2017 01:45:32 From: Keith Bainbridge To: Jude DaShiell Cc: Debian Lists Subject: Re: kde install accessibility experience Suggest you contact Klaus Knopper of knoppix, who had similar issues with a better half if I remember. Keith Bainbridge 0447667468 keithrbaugro...@gmail.com Sent from my APad On 10 Jan 2017 18:06, "Jude DaShiell" wrote: Earlier I wrote the kde-accessibility list and asked how to get kde accessibility working with kde installed on a system specifically screen reading accessibility. I was advised I would need to install the whole orca dependency stack and get orca up and running and from orca then get kdespeech started. I was also told kdespeech would read qt stuff orca cannot read but wouldn't do much more beyond that. I tried it and had an interesting install failure experience. First going into console and installing orca dependency stack on the kde installation that had already got done was no problem. The problem started on rebootand I got the graphical environment running and I know that because espeakup stopped working like it does in the console. So next I start orca up and that worked too and I was thinking I'm just about home free here. Wrong! What came up talking on the screen was I suppose you could call it a dialog to set the system date. I tried several times to set the system date in that calendar dialog and though I was able to set the date, I found no control or way to close the calendar dialog and go beyond the calendar dialog to get any of kde's accessibility up and working. Since then I have read about some variables that may be helpful exporting before I start up the graphical environment on next installation try. Understand, I do my own stuff with computers and do not have sighted assistance to help out when I do it let alone someone experienced with kde who can see so that's the explanation for this failed kde accessibility install experience. -- --
Re: kde install accessibility experience
Suggest you contact Klaus Knopper of knoppix, who had similar issues with a better half if I remember. Keith Bainbridge 0447667468 keithrbaugro...@gmail.com Sent from my APad On 10 Jan 2017 18:06, "Jude DaShiell" wrote: > Earlier I wrote the kde-accessibility list and asked how to get kde > accessibility working with kde installed on a system specifically screen > reading accessibility. I was advised I would need to install the whole > orca dependency stack and get orca up and running and from orca then get > kdespeech started. I was also told kdespeech would read qt stuff orca > cannot read but wouldn't do much more beyond that. > I tried it and had an interesting install failure experience. > First going into console and installing orca dependency stack on the kde > installation that had already got done was no problem. > The problem started on rebootand I got the graphical environment running > and I know that because espeakup stopped working like it does in the > console. So next I start orca up and that worked too and I was thinking > I'm just about home free here. Wrong! What came up talking on the screen > was I suppose you could call it a dialog to set the system date. I tried > several times to set the system date in that calendar dialog and though I > was able to set the date, I found no control or way to close the calendar > dialog and go beyond the calendar dialog to get any of kde's accessibility > up and working. Since then I have read about some variables that may be > helpful exporting before I start up the graphical environment on next > installation try. > Understand, I do my own stuff with computers and do not have sighted > assistance to help out when I do it let alone someone experienced with kde > who can see so that's the explanation for this failed kde accessibility > install experience. > > > > -- > >
Re: kde install accessibility experience
This was an issue in Jessie Stable I hadn't downloaded the Stretch iso before I had that install failure. On Wed, 11 Jan 2017, kamaraju kusumanchi wrote: Date: Wed, 11 Jan 2017 22:23:08 From: kamaraju kusumanchi To: Jude DaShiell , "debian-user@lists.debian.org" Subject: Re: kde install accessibility experience On Tue, Jan 10, 2017 at 2:05 AM, Jude DaShiell wrote: Earlier I wrote the kde-accessibility list and asked how to get kde accessibility working with kde installed on a system specifically screen reading accessibility. I was advised I would need to install the whole orca dependency stack and get orca up and running and from orca then get kdespeech started. I was also told kdespeech would read qt stuff orca cannot read but wouldn't do much more beyond that. I tried it and had an interesting install failure experience. I do not have any suggestion for your problem. But it probably will help someone else facing a similar issue if you could tell whether this is an issue in Jessie (currently stable) or in Stretch (currently testing) installation. --
Re: kde install accessibility experience
On Tue, Jan 10, 2017 at 2:05 AM, Jude DaShiell wrote: > Earlier I wrote the kde-accessibility list and asked how to get kde > accessibility working with kde installed on a system specifically screen > reading accessibility. I was advised I would need to install the whole orca > dependency stack and get orca up and running and from orca then get > kdespeech started. I was also told kdespeech would read qt stuff orca > cannot read but wouldn't do much more beyond that. > I tried it and had an interesting install failure experience. I do not have any suggestion for your problem. But it probably will help someone else facing a similar issue if you could tell whether this is an issue in Jessie (currently stable) or in Stretch (currently testing) installation. -- Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
Re: kde install accessibility experience
What follows is likely no more than tangentially related to the subject line or
the OP, but might be of use to anyone seriously challenged visually.
I spent about 6 hours today at the home of a previously sighted long-time Linux
user whose macular degeneration is nearly complete. We have multiboot on his
machine, primarily openSUSE, which he started using long before I started using
Linux at all, at least 15 years ago. Right now he has openSUSE 13.1, 13.2 and
42.1, plus Stretch, all bootable from one Grub menu that I configure manually.
In 13.1 he has KDE3. In 13.2 he has KDE3 and KDE4. In 42.1 and Stretch he has
TDE, a very mature fork of KDE3. We've never been able to get everything he
needs to work from any single DE, which is why we have the four installations.
Up until today, he hasn't put Stretch to use. 13.1 has gone out of support, and
13.2 is on the out of support doorstep, so 42.1 and/or Stretch need to be doing
at least as well as the older openSUSE versions did.
Today we got over one big hump. KDE3 and TDE have KTTS (which provides speech in
conjunction with Festival voices), but it stopped working with the upgrade from
13.1 to 13.2, and still would not work in 42.1, because Festival got upgraded
from 2.1.something to 2.4.something[1]. Before today we had KTTS working in
Stretch, but he wasn't using it because of other things I never got finished
getting to work in Stretch. Today I got all but one of those other things to
work in Stretch, so that's what was running when I wore out and came home. The
hump was proper migration of KMail, which resulted from using TDE's migration
utility that I hadn't previously known existed, migratekde3.
So, what still does not work is Audible.com. It works fine in Firefox ESR 38 in
13.1 and 13.2, will not play what matters in 42.1 or Stretch. Its sample media,
which are tiny sound files embedded in the logged in home page, play just fine
in both Firefox ESR 45 and Chromium in 42.1 and Stretch, but the books he has
subscribed and paid for, which live in "the cloud", error in trying to play
("problem connecting to server. Please click to try again."). Audible tech
support does not support Linux, even though it previously worked, and works in
older versions, in Linux. NAICT, the problem is CORS related, but I had to quit
before making any significant progress trying to figure out if a solution exists.
[1] https://bugzilla.opensuse.org/show_bug.cgi?id=981271
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
kde install accessibility experience
Earlier I wrote the kde-accessibility list and asked how to get kde accessibility working with kde installed on a system specifically screen reading accessibility. I was advised I would need to install the whole orca dependency stack and get orca up and running and from orca then get kdespeech started. I was also told kdespeech would read qt stuff orca cannot read but wouldn't do much more beyond that. I tried it and had an interesting install failure experience. First going into console and installing orca dependency stack on the kde installation that had already got done was no problem. The problem started on rebootand I got the graphical environment running and I know that because espeakup stopped working like it does in the console. So next I start orca up and that worked too and I was thinking I'm just about home free here. Wrong! What came up talking on the screen was I suppose you could call it a dialog to set the system date. I tried several times to set the system date in that calendar dialog and though I was able to set the date, I found no control or way to close the calendar dialog and go beyond the calendar dialog to get any of kde's accessibility up and working. Since then I have read about some variables that may be helpful exporting before I start up the graphical environment on next installation try. Understand, I do my own stuff with computers and do not have sighted assistance to help out when I do it let alone someone experienced with kde who can see so that's the explanation for this failed kde accessibility install experience. --
