Don't drop alsaconf
Bug #54262 reported by
Norbert Tretkowski
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
alsa-utils (Baltix) |
Confirmed
|
Undecided
|
Unassigned | ||
alsa-utils (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Sound worked fine yesterday, but when I switched on my computer today, there was no sound. Yes, alsa modules are loaded. To fix this, I wanted to run alsaconf, but unfortunately it's not installed in dapper's alsa-utils package.
Please do _not_ drop alsaconf.
Changed in alsa-utils: | |
status: | Unconfirmed → Confirmed |
Changed in alsa-utils: | |
importance: | Undecided → Wishlist |
status: | Unconfirmed → Confirmed |
To post a comment you must log in.
Since I've already filed this bug before, and had it rejected, I'd like to chime in before it gets rejected again. Alsaconf is a buggy, sorry excuse for a configurator that happens to work. Before dropping it, please see that its functionality is replaced. For Gnome users, I hear that it is. For KDE users, especially KDE users with multiple sound cards, it's not. I assume the situation is similar for users of other desktops.
Last time this came up, I was admonished to file bugs against the failures of existing tools to solve these problems. That's good advice, but until those tools (and there should be a command line, desktop-independent tool among them) are ready to do what alsaconf has done for those of us who have come to appreciate it, please leave it as an option.