From: LinArcX <LinArcX@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] `alsactl kill rescan` not working.
Date: Sat, 11 Mar 2023 09:20:31 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42698@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
New issue by LinArcX on void-packages repository
https://github.com/void-linux/void-packages/issues/42698
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.15_1 x86_64 GenuineIntel uptodate hold rFF
### Package(s) Affected
alsa-utils
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
I am using Alsa for sound/audio management on my void machine and i have two monitors:
1. one from my laptop
2. one is external
I can switch between them by changing the device number in `~/.asoundrc` like this:
```
defaults.ctl.card 0;
defaults.pcm.card 0;
defaults.pcm.device 0;
#defaults.pcm.device 3;
```
And every time i came here and uncomment the last line and comment the third line, if i want to use external speaker.
For affecting the change, there is a command:
`alsactl kill rescan`
But it doesn't work for me. any idea?
### Actual behaviour
when I run this command:
`alsactl kill rescan`
It should read `~/.asoundrc` file and affect the changes.
### Steps to reproduce
1. Just install `alsa-utils`
next reply other threads:[~2023-03-11 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 8:20 LinArcX [this message]
2023-03-11 9:04 ` LinArcX
2023-03-11 9:04 ` [ISSUE] [CLOSED] " LinArcX
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42698@inbox.vuxu.org \
--to=linarcx@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).