I isolated the problem to be a package called "squeezelite". There are
actually 3 such packages: "squeezelite, squeezelite-pa, and
squeezelite-pulseaudio". Squeezelite is a local client for the
Logitechmediaserver (LMS, formally slimserver) which I have installed on
my machine for music media files. The solution was to remove and ignore
the debian-specific package, and go install the latest and greatest from
the developers. This is because I also use the latest and greatest
LMS. Once this was done, no more sound issues. Actually, I don't have
any issues at all right now (fingers crossed).
On 8/25/21 3:04 PM, James D Freels wrote:
I was able to correct my problem. Not sure exactly what I did to
correct it. I was following the steps from here:
https://www.linuxquestions.org/questions/slackware-14/alsa-1-2-5-upgrade-errors-4175695921/page3.html
which was a similar problem to mine. Anyways, finally got there.
On 8/24/21 4:27 PM, James D Freels wrote:
Hello,
I am a long-time debian and TDE user, and just recently upgraded my
buster amd64 machine to bullseye. As part of this upgrade, I also
switch from stable builds to the preliminary stable builds of TDE.
For example, tdm-trinity is versioned to read this:
4:14.0.11~pre26-0debian11.0.0+7 . Essentially everything works as
expected so far. However, one very nagging problem I currently have
is that my sound does not work unless I am rooted. For example, if I
issue the command
aplay bark.au
where bark.au is a snippet sound file of a dog barking, it fails.
However, if I issue the command
sudo aplay bark.au
it works fine. Similar sound playing occurs with any sound-playing
app. For example mpg123, vlc, etc., all require a sudo or be logged
in as root to work.
I have looked all around the WWW to try to find a solution to this
problem. The most common solution is to make sure that user ids are
in the audio group in the /etc/group configuration file. Of course, I
have that, and have confirmed it. This is not a brand new
installation after all, but an upgrade.
Other common remedies I have tried are to fiddle with the pavucontrol
and alsamixer settings. My sound card does not show up in the
pavucontrol (pulse doesn't find my sound card), but DOES show up in
the alsamixer.
I have also looked at the debian sound wiki, and other sources to try
to fix this problem.
Then, I remembered that I often used this form to learn about debian
way back in the days when I first started using debian about 1994 or
so. Perhaps I can get some expert help. Maybe a source I can go
down a list of troubleshoot to nail this one down. It is obviously a
permissions issue (I also looked at device permissions, etc.).
I am not sure if this is a debian/11/bullseye problem of a TDE
problem, so I have cross-posted this help request to the debian-user
mailing list as well (without the TDE information since it is not
supported there).
Just a bit puzzled and frustrated.
P.S.
BTW, my sound card is a C-Media, Xonor DG with chip set CMI8788 and
uses the oxygen HD audio driver.
lspci -v output corresponding:
05:02.0 Multimedia audio controller: C-Media Electronics Inc CMI8788
[Oxygen HD Audio]
Subsystem: ASUSTeK Computer Inc. CMI8786 (Xonar DG)
Flags: bus master, medium devsel, latency 64, IRQ 22, NUMA
node 0
I/O ports at e800 [size=256]
Capabilities: [c0] Power Management version 2
Kernel driver in use: snd_oxygen
Kernel modules: snd_oxygen
Nothing has changed with the hardware, and I know the setup works.
This seems to be a permissions/software issue.
--
Father, if you are willing, please take this cup of suffering away
from me. Yet I want your will to be done, not mine.
Luke 22:42 NLT
James D. Freels, Ph.D., P.E.
freelsjd@xxxxxxxxx
865-457-6742 (landline)
865-919-0320 (cell)
____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
