From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id 20AD61EF840; Thu, 31 Dec 2015 12:11:09 -0500 (EST) Received: from p3plsmtpa06-05.prod.phx3.secureserver.net (p3plsmtpa06-05.prod.phx3.secureserver.net [173.201.192.106]) by befuddled.reisers.ca (Postfix) with ESMTPS id 1BABF1EF72E for ; Thu, 31 Dec 2015 12:11:06 -0500 (EST) Received: from village2.fios-router.home ([108.41.193.153]) by p3plsmtpa06-05.prod.phx3.secureserver.net with id 0HB21s0073K2U5001HB326; Thu, 31 Dec 2015 10:11:03 -0700 From: Steve Matzura To: "Speakup is a screen review system for Linux." Subject: Re: Getting speakup to run on debian Date: Thu, 31 Dec 2015 12:11:03 -0500 Message-ID: <47oa8b9orqmqb8a4ijgfq6c1nbhljdgu5p@4ax.com> References: <558A5D8D.20209@gmail.com> <56854603.2010409@barrettpianos.co.uk> <56855FC7.7020000@barrettpianos.co.uk> In-Reply-To: <56855FC7.7020000@barrettpianos.co.uk> User-Agent: ForteAgent/7.20.32.1218 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 X-BeenThere: speakup@linux-speakup.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Dec 2015 17:11:09 -0000 Yes, and I just got beat up (LOLP in two places for not reporting something as a bug, but I'm very conservative on bug reporting until I am absolutely positively sure I'm not the one with the bug. Debuggers' time is more valuable than mine will ever be, so I am wont to waste their time on what's really a user problem, and the computer gods know I've certainly been at the root of more than a few of those. On Thu, 31 Dec 2015 17:03:03 +0000, you wrote: >Glad you got it going. > >Probably would be better if nothing was muted by default so that it=20 >should come up with sound enabelled. > >I got caught with the same issue a few years ago but probably best to=20 >report it as a bug. > > > >On 31/12/15 16:40, Steve Matzura wrote: >> Yes, I absolutely did have *EVERYTHING* muted and didn't know it until >> I learned (a little) how to use amixer. I'm still a little confused >> about one thing: amixer thinks the main sound card's output is a >> headphone jack, so when I set the volume for 'Front' to 100%, I got no >> results, but when I set pvolume to 100% for Headphone, on it came. Now >> that I think about it a little, I've seen something similar to this in >> Windows. These Realtek sound chips have an annoying property where >> they show two devices with the same name, something like "Realtek >> High-Definition Speakers". One is the jack on the back of the machine, >> one is the internal speaker of that machine. However, when you set the >> default device to one of those two high-definition devices and plug a >> headphone into the headphone jack, with the internal speaker setting, >> it doesn't switch over, but with the other one, it does, and the >> default device now changes to "Realtek High-Definition Headphones". so >> I think what's going on in the Linux interpretation of all of this is >> that Linux calls the main output jack "Headphone" because it can be >> switched to a front-panel connection simply by plugging something into >> it. I have tried the other jacks on the back panel, of which there are >> four others (not including the SPDIF/optical connector, which looks >> and feels nothing like an eighth-inch audio jack), and gotten no >> response, so I'm 99% sure I'm plugged in to the right thing and have >> the right control volume set in amixer. >> >> On Thu, 31 Dec 2015 15:13:07 +0000, you wrote: >> >>> Just a thought, >>> >>> Do you have sound working? >>> >>> running "speaker-test" should give you white noise if sound is = working. >>> >>> You may have some of the sound controls muted. >>> >>> >>> >>> On 31/12/15 12:08, Steve Matzura wrote: >>>> I just installed a fresh Jessie yesterday. The install was assisted = by >>>> Speakup, which I started at the install screen main menu by pressing >>>> s. I was quite impressed with the way it all worked, with one >>>> silly exception: There was a screen with 78 choices, one per line, = and >>>> I couldn't figure out how to scroll the screen backward to read the >>>> first and second screens of choices, so I just went with the default >>>> choice, which turned out to be the correct one for me for the = question >>>> being asked. Very impressive. No Orca, no forms, just straight CLI. = I >>>> love CLI. >>>> >>>> Now then, the system is up and running, there's no desktop, I boot >>>> directly to the login prompt, and now I want to get Speakup working = on >>>> the console terminals. Someone named Samuel from Debian = accessibility >>>> told me I should install the espeakup package, but apt-get can't = find >>>> it. What'd I do wrong? And why would I even need to be doing this >>>> since obviously Speakup is included in the install, you'd think, or = at >>>> least I did, that it would already exist on the system and be able = to >>>> be run. >>>> >>>> Thanks in advance for any and all assistance and advice. >>>> _______________________________________________ >>>> Speakup mailing list >>>> Speakup@linux-speakup.org >>>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup >>> _______________________________________________ >>> Speakup mailing list >>> Speakup@linux-speakup.org >>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup >> _______________________________________________ >> Speakup mailing list >> Speakup@linux-speakup.org >> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > >_______________________________________________ >Speakup mailing list >Speakup@linux-speakup.org >http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup