Re: running speakup on f17 beta
Josh Boyer writes: > You would contact the fedora kernel list. They would tell you that > Fedora doesn't enable staging drivers except in very specific cases. Hmmm, I presume there's a document describing the selection criteria? Janina -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Email: jan...@rednote.net The Linux Foundation Chair, Open Accessibility: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Protocols & Formats http://www.w3.org/wai/pf Indie UIhttp://www.w3.org/WAI/IndieUI/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [orca-list] BEWARE: Fedora 15 & 16 Unusable for the Speech Dependent Orca User
Jason White writes: > Have you tried configuring speech-dispatcher to use a network socket rather > than a UNIX socket, e.g., 127.0.0.1? That might give you a work-around until > the real issue is fixed. > Good idea. Turns out this is fairly simple. In my /etc/speech-dispatcher/speechd.conf, I do: CommunicationMethod "inet_socket" I believe the following two are default, but just in case, I uncomment them as well: Port 6560 LocalhostAccessOnly 1 Now, I'm somewhat concerned that 'nmap -P0 localhost' doesn't show port 6560. Nevertheless, I try my spd-say command after rebooting ... > Also, speech-dispatcher should report the error if it can't access the socket; > it shouldn't hang, in which case there's a bug pertinent to the lack of error > checking in addition to whatever the underlying problem is. > Indeed, there seems such a bug as hang is what it did. But, now I get errors as follows. I don't know where to take this. Advice much appreciated. janina@sonata 19:02:08 ~$spd-say hello 2>&1 Failed to connect to Speech Dispatcher: Error: Can't connect to unix socket /home/janina/.speech-dispatcher/speechd.sock: Connection refused. Autospawn: Autospawn failed. Speech Dispatcher refused to start with error code, stating this as a reason: Error: can't open logging file /var/log/speech-dispatcher//speechd.log! Using stdout. Thu Oct 27 19:02:22 2011 [184686] ALSA ERROR: Cannot open audio device plughw:2,0 (Device or resource busy) Thu Oct 27 19:02:22 2011 [184717] ALSA ERROR: Cannot initialize Alsa device 'plughw:2,0': Can't open. festival_client: connect to server failed Error: can't open logging file /var/log/speech-dispatcher//speechd.log! Using stdout. Autospawn failed: Mismatch in communication methods. Client requests unix_socket, most probably due to its configuration or the value of the SPEECHD_ADDRESS environment variable, but the server is configured to provide the inet_socket method. How so still looking for unix sockets? And how so can't write a log? Checking the log directory is owned by root, gid root. Directory is set 700, and file is 660. Seems root should be able to write. Or, is SD not running as root? Janina -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Chair, Open Accessibility jan...@a11y.org Linux Foundationhttp://a11y.org Chair, Protocols & Formats Web Accessibility Initiativehttp://www.w3.org/wai/pf World Wide Web Consortium (W3C) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [orca-list] BEWARE: Fedora 15 & 16 Unusable for the Speech Dependent Orca User
Hi, Jason: Jason White writes: > Janina Sajka wrote: > > > Issuing the following command as root works as expected. Issuing this > > command as an ordinary user hangs until a Ctrl-C. > > Perhaps it would be a good idea to run these commands with strace, capture the > output and add it to the bug report. > Already done. Also, I've verified that selinux isn't the problem, and I've provided ls -lZ and ls -ldZ output for ~/.speech-dispatcher inasmuch as the strace seemed to suggest the problem was a "connection refused" accessing the socket in that directory. I'm pleased to report I have had good followup from Red Hat this evening, so I'm hopeful. But, no solution yet. Janina > ___ > orca-list mailing list > orca-l...@gnome.org > http://mail.gnome.org/mailman/listinfo/orca-list > Visit http://live.gnome.org/Orca for more information on Orca. > The manual is at > http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html > The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions > Netiquette Guidelines are at > http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines > Log bugs and feature requests at http://bugzilla.gnome.org > Find out how to help at http://live.gnome.org/Orca/HowCanIHelp -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Chair, Open Accessibility jan...@a11y.org Linux Foundationhttp://a11y.org Chair, Protocols & Formats Web Accessibility Initiativehttp://www.w3.org/wai/pf World Wide Web Consortium (W3C) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
BEWARE: Fedora 15 & 16 Unusable for the Speech Dependent Orca User
If you depend on speech-dispatcher for screen reader access, e.g. with Orca, stay away from Fedora 15 and the upcoming Fedora 16 until there's a fix for bug 743762: https://bugzilla.redhat.com/show_bug.cgi?id=743762 Unfortunately, there has been no activity on this bug since it was reported several weeks ago. Please note, furthermore, that there is no longer any other speech option for Orca The old gnome-speech option will not function over D-Bus, and should, frankly, have been removed. Symptoms Speech Dispatcher will only speak for the root user. It will not speak for an ordinary user. This does not appear to be a problem with the graphical environment, however, as it can be demonstrated from the console using spd-say. Issuing the following command as root works as expected. Issuing this command as an ordinary user hangs until a Ctrl-C. Furthermore, the audio device remains "busy" until the offending orphaned pid is manually killed. Stopping Speech-Dispat cher will not kill this pid. Lastly, the problem does not appear to be with Speech-Dispatcher itself, inasmuch as the build provided on F-15 dates to March last, and worked satisfactorally until approximately one month ago. Janina -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Chair, Open Accessibility jan...@a11y.org Linux Foundationhttp://a11y.org Chair, Protocols & Formats Web Accessibility Initiativehttp://www.w3.org/wai/pf World Wide Web Consortium (W3C) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: grub2 confusion
Michael Schwendt writes: > The symlink target is read-only as another reminder that one should > not edit it with an editor but only via the fragments in /etc/grub.d/ > > -- Seems clear enough, as is also the unambiguous header in grub.cfg, until one reads the Grub manual which clearly and unambiguously says: "In the meantime, those who feel that it would be easier to write grub.cfg directly are encouraged to do so." http://www.gnu.org/software/grub/manual/grub.html#Simple-configuration Are we to edit directly? Or not? Are we to use update-grub (as the file grub.cfg says)? Or grub-mkconfig (as the manual says)? Or grub2-mkconfig (as actually exists in the fs)? Seems clear as mud, and I've only been studying grub2 for less than an hour. Which is, actually, making me a bit nervous about grub2. Janina > Fedora release 16 (Verne) - Linux 3.1.0-0.rc8.git0.1.fc16.x86_64 > loadavg: 0.32 0.08 0.07 > -- > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Chair, Open Accessibility jan...@a11y.org Linux Foundationhttp://a11y.org Chair, Protocols & Formats Web Accessibility Initiativehttp://www.w3.org/wai/pf World Wide Web Consortium (W3C) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Procmail's stopped processing
Daniel J Walsh writes: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 10/06/2011 03:08 AM, Adam Pribyl wrote: > > On Wed, 5 Oct 2011, Janina Sajka wrote: > > > >> Janina Sajka writes: > >>> I can't be the only one who's run into this? > >>> > >>> > >>> My procmail setup has not changed fundamentally in well over a > >>> decade. I use INCLUDERC directives in my ~/.procmailrc so that > >>> I can keep my various recipies in separate files. It's worked > >>> perfectly well forever -- until my install of Tuesday's F-16 > >>> beta, that is. > >>> > >>> Argh. All my mail is landing in my inbox! > >>> > >> > >> I neglected to say that my /home is a separate partition which > >> was NOT formatted during the F-16 beta install, though my / was a > >> clean install. > >> > >> My /home is btrfs, if that matters, though this problem wasn't > >> around the past weeks whilst I've been running F-16 Alpha > >> (installed via yum). > >> > >> I've filed: https://bugzilla.redhat.com/show_bug.cgi?id=743775 > >> > >> Sorry for the duplicate message. I should be going to bed! > > > > Just a guess: Do you have SELinux enabled? > > My bad. All fixed by running restorecon on the included recipie files. It's not anything I've had to do before, so I seems btrfs was the difference. Sorry for being a slow learner, but appreciate the easy fix. Janina > >>> Janina > > > > Adam Pribyl > > If this is an SELinux issue, the first thing I would do would be to run > > restorecon -R -v /home > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk6NrrEACgkQrlYvE4MpobP91wCfZBld1NyJwAcemGyKfOj9yIgo > TeoAoKrs59vEC0A2RnG9rXm2vkC+U9dC > =zEA+ > -END PGP SIGNATURE- > -- > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Chair, Open Accessibility jan...@a11y.org Linux Foundationhttp://a11y.org Chair, Protocols & Formats Web Accessibility Initiativehttp://www.w3.org/wai/pf World Wide Web Consortium (W3C) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Procmail's stopped processing
Janina Sajka writes: > I can't be the only one who's run into this? > > > My procmail setup has not changed fundamentally in well over a decade. I > use INCLUDERC directives in my ~/.procmailrc so that I can keep my > various recipies in separate files. It's worked perfectly well forever > -- until my install of Tuesday's F-16 beta, that is. > > Argh. All my mail is landing in my inbox! > I neglected to say that my /home is a separate partition which was NOT formatted during the F-16 beta install, though my / was a clean install. My /home is btrfs, if that matters, though this problem wasn't around the past weeks whilst I've been running F-16 Alpha (installed via yum). I've filed: https://bugzilla.redhat.com/show_bug.cgi?id=743775 Sorry for the duplicate message. I should be going to bed! > Janina > > > > > -- > > test mailing list > > test@lists.fedoraproject.org > > To unsubscribe: > > https://admin.fedoraproject.org/mailman/listinfo/test > > -- > > Janina Sajka, Phone: +1.443.300.2200 > sip:jan...@asterisk.rednote.net > > Chair, Open Accessibility jan...@a11y.org > Linux Foundation http://a11y.org > > Chair, Protocols & Formats > Web Accessibility Initiative http://www.w3.org/wai/pf > World Wide Web Consortium (W3C) > > -- > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test > -- > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Chair, Open Accessibility jan...@a11y.org Linux Foundationhttp://a11y.org Chair, Protocols & Formats Web Accessibility Initiativehttp://www.w3.org/wai/pf World Wide Web Consortium (W3C) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Procmail's stopped processing
I can't be the only one who's run into this? My procmail setup has not changed fundamentally in well over a decade. I use INCLUDERC directives in my ~/.procmailrc so that I can keep my various recipies in separate files. It's worked perfectly well forever -- until my install of Tuesday's F-16 beta, that is. Argh. All my mail is landing in my inbox! Janina > > -- > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Chair, Open Accessibility jan...@a11y.org Linux Foundationhttp://a11y.org Chair, Protocols & Formats Web Accessibility Initiativehttp://www.w3.org/wai/pf World Wide Web Consortium (W3C) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Can't login via GDM anyomre: Re: Fedora 16 updates-testing report
Matthias Clasen writes: > On Thu, 2011-09-22 at 14:05 -0400, Matthias Clasen wrote: > > On Thu, 2011-09-22 at 09:12 -0400, Chuck Anderson wrote: > > > Beware the gigantic gnome 3.1.92 update. Something in this > > > transaction broke the ability for me to log in at all via GDM. You > > > type your password, and hit enter, nothing happens. Click Sign In > > > button, nothing happens. > > > > You are likely hitting a race in the a11y key event handling at session > > end (the session being the login screen here). I've been seeing that > > myself with .92. We're working on it. > > This should be fixed in at-spi2-atk-2.1.92-2.fc16. I now have at-spi2-atk-2.1.92-2 (from Koji), but no joy--sorry to say. Janina > > -- > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Chair, Open Accessibility jan...@a11y.org Linux Foundationhttp://a11y.org Chair, Protocols & Formats Web Accessibility Initiativehttp://www.w3.org/wai/pf World Wide Web Consortium (W3C) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 14 Beta RC3 Available Now!
James Laska writes: > Andre correctly reminded me that 'ssh' installer support is not intended > as a replacement for a telnet install. Rather, it is a means for > enabling 'ssh' to remotely monitor install progress. Translation, you > can ssh into the installing system and monitor /tmp/*log or do whatever > else you want from a shell. Essentially, it provides the shell you > normally get on tty2, but over the network. > So, what's the new way to install on a remote machine where one has no hands-on access? What do those of us with machines at dataplexes like The Planet, or with virtual machines on services like Virtual Host do? To my mind ssh would be a perfect replacement for telnet for all the obvious security reasons. If, however, the answer is vnc, then I'm compelled to point out that leaves some of us out of the party. Janina > Thanks, > James > -- > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Chair, Open Accessibility jan...@a11y.org Linux Foundationhttp://a11y.org Chair, Protocols & Formats Web Accessibility Initiativehttp://www.w3.org/wai/pf World Wide Web Consortium (W3C) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 14 Beta RC3 Available Now!
Hi, Jon Hermansen writes: > Hi, > > On Sat, Oct 2, 2010 at 11:52 AM, Janina Sajka wrote: > > > Seems telnet installs are again broken. I've filed bug 639629 Submitted > > - Installation over telnet isn't working > > > > James Laska recently mentioned that "the ability to telnet into the > installer and direct the installation from the telnet session has been > removed" -- see this ticket: https://fedorahosted.org/fedora-qa/ticket/129 > Thanks for the pointer. > AFAIK it _was_ on some list of installer test cases, but isn't supported > anymore. It's probably recommended that you use SSH instead. Hmmm, looks much worse than that, from my perspective. Seems ssh isn't replacing telnet's use case at all: http://www.spinics.net/lists/fedora-testing/msg93762.html So, I will go test whether accessibility support is fixed in the Live image. If not, I have no way to install Fedora without assistance from someone. That would not be good at all. Janina > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Chair, Open Accessibility jan...@a11y.org Linux Foundationhttp://a11y.org Chair, Protocols & Formats Web Accessibility Initiativehttp://www.w3.org/wai/pf World Wide Web Consortium (W3C) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 14 Beta RC3 Available Now!
Seems telnet installs are again broken. I've filed bug 639629 Submitted - Installation over telnet isn't working This has happened more than once in the past. It would be REALLY REALLY nice if this functionality could be among the things verified before new distribution releases. Since it does keep coming up, shouldn't telnet install be on some checklist? Janina -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Chair, Open Accessibility jan...@a11y.org Linux Foundationhttp://a11y.org Chair, Protocols & Formats Web Accessibility Initiativehttp://www.w3.org/wai/pf World Wide Web Consortium (W3C) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
