From: "Nick Gawronski" <nick@nickgawronski.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: hal on debian testing fails configuration
Date: Wed, 24 Dec 2008 13:51:22 -0600 [thread overview]
Message-ID: <FF703941019A4908B69CB74FB888063A@chihuahuad1> (raw)
In-Reply-To: <49520F04.7050901@baechler.net>
Hi, Well I did try unloading the speakup module from running at boot and the
program still fails with gnome can't communicate with hal or something like
that. Does hal have any log files that I could look at when I am using
speakup and I could find the errors in them?
----- Original Message -----
From: "Tony Baechler" <tony@baechler.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, December 24, 2008 4:29 AM
Subject: Re: hal on debian testing fails configuration
> First, this is probably not on topic for Speakup. Second, a bit more
> detail would be helpful, like what error message you're getting. Have you
> ran "aptitude -q update" "aptitude -q upgrade" to make sure you have the
> latest packages? Have you looked to see if bugs have been filed that
> relate to your problem? Really there is nothing we can do without a bit
> more to go on.
>
> Nick Gawronski wrote:
>> Hi, I am running debian testing and was having problems with
>> configuration of the hardware abstraction layer. It tries to configure
>> itself but fails. I am using a dectalk express external synthisizer
>> connected to the first and only serial port in my system. Has anyone
>> else had this problem and is there a fix for it?
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Nick Gawronski
` Tony Baechler
` Nick Gawronski [this message]
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=FF703941019A4908B69CB74FB888063A@chihuahuad1 \
--to=nick@nickgawronski.com \
--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).