public inbox for gentoo-accessibility@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Homuth, James (Gentoo)" <james@the-jdh.com>
To: orca-list@gnome.org
Cc: gentoo-accessibility@lists.gentoo.org
Subject: [gentoo-accessibility] Confirmation: Orca on Gnome 2.24 crashes when sounds are enabled.
Date: Tue, 25 Aug 2009 16:23:49 -0500	[thread overview]
Message-ID: <1251235429.27595.10.camel@laptop.pc-net> (raw)

I've had confirmation now that, upon the enabing of certain sound
notifications in Gnome 2.24 on Gentoo, Orca will crash. Noteably if you
enable the option to play a sound when a button is clicked. The only way
around it that I've been able to find, which unfortunately means I have
to set up Orca again, is to blow away the /home/james/.gconf directory
and start it over. Fortunately that's not what I'd call a huge problem
for me at this stage, and I know what not to enable in future.

I'm curious, though, to know if this is addressed in a later version of
Gnome and/or Orca. If yes, it might be worth the trouble of upgrading,
in spite of the fact Gentoo doesn't list 2.26 as stable yet. As said
earlier, any feedback or additional information on this would be
appreciated. I'm CCing the Gentoo accessibility list as well, in the
event it turns out to be an OS specific problem.




             reply	other threads:[~2009-08-28 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25 21:23 Homuth, James (Gentoo) [this message]
     [not found] ` <4A94517E.7090501@informal.com.br>
     [not found]   ` <1251239379.29576.2.camel@laptop.pc-net>
     [not found]     ` <4A946C79.4050001@informal.com.br>
     [not found]       ` <1251242390.29576.12.camel@laptop.pc-net>
     [not found]         ` <4A9454B7.9090208@sun.com>
2009-08-26 18:46           ` [gentoo-accessibility] RE: [orca-list] Confirmation: Orca on Gnome 2.24 crashes when sounds are enabled James Homuth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1251235429.27595.10.camel@laptop.pc-net \
    --to=james@the-jdh.com \
    --cc=gentoo-accessibility@lists.gentoo.org \
    --cc=orca-list@gnome.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox