public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speech-dispatcher now working, sort of
Date: Fri, 2 May 2008 14:34:33 -0700	[thread overview]
Message-ID: <20080502213432.GA16705@localhost.localdomain> (raw)
In-Reply-To: <20080502211418.GA8726@cq.ftml.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chuck,

I remember the issue was with the alsa libs, libasound2 to be exact I
think. On my debian testing system, the info for libasound2 shows:

Package: libasound2
State: installed
Automatically installed: no
Version: 1.0.16-2

This is the version that apt-get dist-upgrade installed for me after I
took the hold off libasound2, once I read your post that things with
alsa were back to normal on debian unstable. So, are you saying that
libasound2 1.0.16-2 is in reality libasound2 1.0.15?

Greg


On Fri, May 02, 2008 at 05:14:18PM -0400, Chuck Hallenbeck wrote:
> Zach,
> 
> Actually, the fix Greg mentioned was to revert to alsa 1.0.15, so it
> wasn't a fix in the usual sense, but a rolling back to a version
> without the 1.0.16 problem. 
> 
> Chuck
> 
> 

- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIG4jo7s9z/XlyUyARAhXhAKDgQTyi50SwJGzHu6Q96Q4TnaRUagCffNoX
PqQkwO8Vih04HtC7OSQ3RiY=
=vlnB
-----END PGP SIGNATURE-----


  reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Zachary Kline
 ` Gregory Nowak
   ` Gregory Nowak
     ` Zachary Kline
       ` Chuck Hallenbeck
         ` Gregory Nowak [this message]
           ` Chuck Hallenbeck
       ` Gaijin

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=20080502213432.GA16705@localhost.localdomain \
    --to=greg@romuald.net.eu.org \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).