Open karstengit opened 8 years ago
This is really hard to diagnose and may be very specific to your particular hardware so I think the best thing you could do is to download this script and run it, which will offer to upload the output to alsa-project.org, and sign up to the alsa-user mailing-list with a description of your problem with error messages and a link to the uploaded info.
I run the script and uploaded the contents. I attach it here additional.
Why i must use the mailing list? It is a better place to handle bug reports here?
Not really as this is not an official ALSA project site, just a legacy documentation site. The developers and most active users will be reachable via either the alsa-user or alsa-devel mailing-lists.
Just a long shot suggestion, make absolutely sure your desktop user belongs to the audio
group. Type "groups" into a terminal app and, if "audio" is not one of the entries, then sudo gpasswd -a YOUR_USER audio
and log back in.
Yes all the users belong to the audio group: karsten,multimedia,timidity,pulse
This should not be the problem.
Shall i report this problem to the user mailing list additional?
Yes, sign up to the alsa-users list and submit your translated errors in the first post above, any other info like what apps you were using at the time, and a link to your alsa-info.sh script output so you don't have to go into the tedious details about your alsa, kernel and hardware versions.
O.K. done Thanks for your help!
Great, good luck. It's the best place to get some ALSA help so it won't be a waste of time now or in the future. Feel free to "Close and comment" this ticket with the (hopefully successful) results of your research into your problem.
I asked for my problems at the ALSA mailing lists - without any answer! :-( Here is no solution too :-(
Found in the syslog
translated: