On Mon, 07 Dec 2015 20:10:57 +0100, Felix Miata wrote:
Richard Brown composed on 2015-12-07 12:04 (UTC+0100):
Felix Miata wrote:
Is this a bug report?
No. It's not a problem that seems reasonably succeptible of a repeatable reproduction scenario required of a useful bug report. I did get some sound eventually, but not across the board.
I do not see a single question mark in the email, so I suspect this is the case
It's more akin to a review, but heavily colored by the frustration of 5+ hours of rebooting, searching, trying this, trying that, and accomplishing little in the context of having reached success in well under an hour on the same machine multiple elsewheres than in TW.
If I had to describe the problem in as few characters as possible, I would have to include the string "broken deps". Success in 4 other distros proves hardware is not a problem.
Process seems to be two problems:
1-YaST2 configuration doesn't stick. YaST2 only plays a test sound immediately after using it to configure the sound device. Once YaST2 sound has been exited, it is incapable of playing a test sound until having deleted the sound device and then adding it back. Last night's was not my first observation of this phenomenon either, as I recall it happening several times dating back too far to remember, probably several years.
Usually you don't need to configure via YaST nowadays. Rather better to avoid it as much as possible.
2-No comprehensive sound configuration utility. Takashi responded "YaST setup is only for the kernel module." Why is that?
Because it's the only thing you can set up commonly in the system level. All the rest depends on your DE and your choice of sound backend setup, including the choice of packages and the choice of plugins.
Overcoming above is complicated by an ostensible help page https://en.opensuse.org/SDB:Audio_troubleshooting on which most recent release in a list of releases to which applicable is the four-year-old, long-out-of-support 12.1.
Right, the documentation should be updated. The generally often seen problem is: people who have used PCs for long time tend to want more detailed controls, and started configuring the system unnecessarily. Then it screws up things easily. In your case, excluding PA, fiddling the system-level sound setup via YaST, then shuffling the sound layer setups...; no surprise that it doesn't always work flawlessly. Look at the graphics setup. Few people fiddle with xorg.conf today. Most of graphics setups are done in a more dynamic way instead. The similar trend is found for sound setup, too. You *shouldn't* change the system setup unless you know what you're doing. This is the way many DEs want / try to go. Instead, the sound setup is done in an upper level, typically in PulseAudio, then covered by more APIs on it like gstreamer, phonon, etc. Yet, there are a few basic DEs that don't cover in such a way and let the system all done. Of course, on such DEs, you'll have to set up everything manually, and old kludges are still useful. An old-school grumpy developer like me still prefers this way, and some in-detail documentation might help. But, this is totally different knowledge from what other people need for a normal sound setup. So, again, the documentation should be updated: but to a direction to minimize the need for any changes. If you start modifying something, it's already out of the scope and it's at your own risk. If you had to change anything to make something working, it's safer to report at first before screwing up. Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org