I understand about confinement and how it is an intrinsic part of the
`snap` functionality.
This means that there are many commonly used programs which should
**never** be converted to `snap`-based architecture, because they are
often used in cases where confinement is not appropriate.
That did it! Thank you!
I am using KDE, and KMix wasn't showing the channels as muted. Once I
installed and ran gnome-alsamixer, I saw that the Front channel was
indeed muted. Un-muting it caused my sound to reappear.
If I boot up under 2.6.20-16-generic, that channel always starts up non-
Thank you.
I believe that this is the same script that I ran and referred to in my
original bug report. If you'll look back into this bug description,
you'll see that I put the original output of this script here:
http://pastebin.ca/750760.
But in any case, I have just now run it a second time,
Thank you for your help with this!
I just now followed your suggestion. After installing linux-backports-
modules and rebooting, the problem persists: still no sound at all
within the 2.6.22-14 kernel.
Oh well ... (sigh) ...
It turns out that linux-backports-modules-2.6.22-14-generic are
Public bug reported:
Binary package hint: linux-image-2.6.22-14-generic
I know that there have been other bugs and fixes concerning sound
problems after a Feisty=Gutsy upgrade, but this one seems different.
First, I'll give a summary of what I know, and then, I'll give lots of
supporting
** Summary changed:
- No sound at all after Gusty upgrade
+ No sound at all after Gutsy upgrade
** Description changed:
Binary package hint: linux-image-2.6.22-14-generic
I know that there have been other bugs and fixes concerning sound
problems after a Feisty=Gutsy upgrade, but this
