public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Alexander Epaneshnikov <aarnaarn2@gmail.com>
To: Janina Sajka <janina@rednote.net>
Cc: Didier Spaier <didier@slint.fr>, speakup@linux-speakup.org
Subject: Re: Now Fixed: Archlinux Speakup problems after alsa package upgrade
Date: Wed, 29 Dec 2021 01:50:25 +0300	[thread overview]
Message-ID: <20211228225025.xdkkmkow6io4kcml@alex-pc> (raw)
In-Reply-To: <YcuSVelJCeOX5Vg0@rednote.net>

On Tue, Dec 28, 2021 at 05:40:21PM -0500, Janina Sajka wrote:
> Yes, I seem to have a full compliment of pw on the older machine, and
> the same set of pw on the newer machine.

strange. I think espeakup will not work if pw is inuse.

> Interestingly, the files in /etc/alsa/conf.d/ are different. The new
> machine shows only two files there:
>
> 50-pipewire.conf
> 99-pipewire-default.conf
>
> On the older machine, earlier today, I tried renumber my alsa devices
> via /etc/modprobe.d/alsa.conf. I ended up putting things back the way
> they were, because the builtin Intel HDA device doesn't work as card 0
> for some reason--very strange, but I adjusted some time ago to start
> numbering my three devices as 1, 2 and 3.  So, after I put things back,
> a see much more pw in that directory:
>
> 10-samplerate.conf
> 10-speexrate.conf
> 50-arcam-av-ctl.conf
> 50-jack.conf
> 50-oss.conf
> 50-pipewire.conf
> 50-pulseaudio.conf
> 60-speex.conf
> 60-upmix.conf
> 60-vdownmix.conf
> 98-usb-stream.conf
> 99-pipewire-default.conf
>
>
> This suggests to me that the conversion to pw is still a work in
> progress!
>
> I've no idea why the above is the situation, though, or what packages
> handle what aspect.

you can use pacman -Qo /path/to/file to check which package owns this file.

> Best,
>
> Janina

--
Sincerely, Alexander

  reply	other threads:[~ UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Kelly Prescott
     [not found] ` <20210609072927.3igbp7jvopq3c6f7@begin>
   ` Kelly Prescott
     ` Janina Sajka
     [not found]     ` <20210609110828.kpo76f2zmbixjran@begin>
       ` Kelly Prescott
         ` Janina Sajka
           ` Alexander Epaneshnikov
     [not found]             ` <YNMr0Pathc/mqx1L@rednote.net>
     [not found]               ` <20210819205617.l76b7fxume3lrf67@begin>
                 ` Alexander Epaneshnikov
                   ` Janina Sajka
     [not found]                   ` <20210820155212.rlj4addvh726cgbb@begin>
                     ` Janina Sajka
     [not found]                       ` <20210821121814.vbyw4vxysowqf7as@begin>
                         ` Janina Sajka
                           ` Didier Spaier
                             ` Janina Sajka
                               ` Didier Spaier
                                 ` Janina Sajka
     [not found]                           ` <20210821125234.onaxd4ccrrh5oiyq@begin>
                             ` Janina Sajka
               ` Now Fixed: " Janina Sajka
                 ` Jason White
                   ` Janina Sajka
                     ` Janina Sajka
                     ` Didier Spaier
                       ` Janina Sajka
                         ` Didier Spaier
                           ` Didier Spaier
                           ` Alexander Epaneshnikov
                             ` Janina Sajka
                               ` Alexander Epaneshnikov [this message]
                                 ` Janina Sajka
           ` captcha revisited, just a little Karen Lewellen
 ` Archlinux Speakup problems after alsa package upgrade Chris Brannon
   ` Kelly Prescott
     ` Jude DaShiell
       ` Jude DaShiell
     ` Chris Brannon

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=20211228225025.xdkkmkow6io4kcml@alex-pc \
    --to=aarnaarn2@gmail.com \
    --cc=didier@slint.fr \
    --cc=janina@rednote.net \
    --cc=speakup@linux-speakup.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).