public inbox for gentoo-accessibility@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-accessibility@lists.gentoo.org
Subject: Re: [gentoo-accessibility] setting up orca on gnome on gentoo
Date: Mon, 29 Mar 2010 11:13:56 -0500	[thread overview]
Message-ID: <20100329161356.GA13380@linux1> (raw)
In-Reply-To: <78e0dabc1003290758q4f1e7ccclfe7941bbf0653feb@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3816 bytes --]

Hi Dave,

there is a much better way to capture messages from packages.  Take a
look at the PORTAGE_ELOG_SYSTEM and PORTAGE_ELOG_MAILURI settings in
make.conf.

It is possible to have this information saved to a file or emailed to
you.

Thanks,

William

On Mon, Mar 29, 2010 at 10:58:34AM -0400, David Mehler wrote:
> Hi,
> Thanks. I'll do that and report back, I don't expect it'll be a quick process.
> One thing how do i determine results of these updates? I know the
> packages sometimes put messages to the screen, only the last of which
> i can get at, if a package way up puts one onscreen i miss it. I've
> tried a script command to try to capture but the output is
> compilations.
> Thanks.
> Dave.
> 
> 
> On 3/29/10, James Homuth <james@the-jdh.com> wrote:
> > Try adding the accessibility use flag, then emerge --update --deep --newuse
> > world.
> >
> > -----Original Message-----
> > From: David Mehler [mailto:dave.mehler@gmail.com]
> > Sent: March 29, 2010 10:25 AM
> > To: gentoo-accessibility@lists.gentoo.org
> > Subject: Re: [gentoo-accessibility] setting up orca on gnome on gentoo
> >
> > Hello,
> > Thanks for your reply. Here are my USE flags.
> >
> > USE="acpi alsa dbus hal X gtk gnome -kde -ipv6 -qt -qt3 -qt4 -arts sockets
> > threads perl consolekit cairo java nsplugin jce"
> >
> >  My complete /etc/make.conf file is below.
> > Thanks.
> > Dave.
> >
> > /etc/make.conf:
> > # These settings were set by the catalyst build script that automatically #
> > built this stage.
> > # Please consult /usr/share/portage/config/make.conf.example for a more #
> > detailed example.
> > # VMware emulates an Intel Core 2 Duo
> > CFLAGS="-O2 -march=i686 -pipe"
> > CXXFLAGS="-O2 -march=i686 -pipe"
> > # WARNING: Changing your CHOST is not something that should be done lightly.
> > # Please consult http://www.gentoo.org/doc/en/change-chost.xml before
> > changing.
> > CHOST="i686-pc-linux-gnu"
> >
> > MAKEOPTS="-j2"
> >
> > ALSA_CARDS="ens1371"
> >
> > VIDEO_CARDS="vmware vesa vga"
> >
> > INPUT_DEVICES="evdev keyboard mouse vmmouse"
> >
> > LINGUAS="en en_US"
> >
> > USE="acpi alsa dbus hal X gtk gnome -kde -ipv6 -qt -qt3 -qt4 -arts sockets
> > threads perl consolekit cairo java nsplugin jce"
> >
> >
> > On 3/29/10, James Homuth <james@the-jdh.com> wrote:
> >> What are your use flags? You're probably missing someething.
> >>
> >> -----Original Message-----
> >> From: David Mehler [mailto:dave.mehler@gmail.com]
> >> Sent: March 28, 2010 10:52 AM
> >> To: gentoo-accessibility@lists.gentoo.org
> >> Subject: [gentoo-accessibility] setting up orca on gnome on gentoo
> >>
> >> Hello,
> >> I'm trying to get orca going on gentoo. The gnome version used is
> >> 2.26. I've tried googling and asking on the orca mailing list, without
> > success.
> >> I installed gentoo following the handbook except used a serial
> >> terminal, this is in a virtual machine as i unfortunately only have
> >> one machine. Later i proceeded to install gnome, which failed. Before
> >> the install would complete successfully libxml2 needed to be
> >> installed. I next installed orca and started up gnome. I had to make
> >> some changes to custom.conf so i could log in and loaded the
> >> accessibility modules per instructions on the orca site. When i tried
> >> to start orca via either the alt+f2, orca or in a terminal with orca
> >> --text-setup i get to the second screen where i'm prompted for the
> >> speech server always i choose gnome speech and then i hear no more
> >> speech. I've also installed the java-access-bridge, but am assuming
> > there's a configuration step i'm missing.
> >> Any suggestions appreciated.
> >> Thanks.
> >> Dave.
> >>
> >>
> >>
> >>
> >
> >
> >
> >
> 

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-03-29 16:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-28 14:52 [gentoo-accessibility] setting up orca on gnome on gentoo David Mehler
2010-03-29  4:10 ` James Homuth
2010-03-29 14:24   ` David Mehler
2010-03-29 14:45     ` James Homuth
2010-03-29 14:58       ` David Mehler
2010-03-29 16:13         ` William Hubbs [this message]
2010-03-29 16:56           ` David Mehler
2010-03-29 20:59             ` David Mehler
2010-03-29 23:12               ` James Homuth
2010-03-30  1:58                 ` David Mehler
2010-03-30  2:36                   ` David Mehler
2010-03-31  1:57                     ` David Mehler
2010-04-13  3:57                       ` Derek Roberts
2010-04-13  5:58                         ` David Mehler
2010-04-13  6:22                           ` Derek Roberts
2010-04-13 13:19                             ` David Mehler
2010-04-14  1:32                             ` James Homuth
2010-04-14  1:46                           ` James Homuth
2010-04-14  2:15                             ` Derek Roberts

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=20100329161356.GA13380@linux1 \
    --to=williamh@gentoo.org \
    --cc=gentoo-accessibility@lists.gentoo.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