abrt version: 2.0.0 comment: Pulseaudio didn't set mixer volume right I was editing it in alsamixer -c0 > Master Front on max & Smart 5.1 on package: alsa-utils-1.0.24.1-3.fc15 cmdline: alsamixer -c0 component: alsa-utils executable: /usr/bin/alsamixer crash_function: snd_hctl_handle_event kernel: 2.6.38.2-8.fc15.x86_64 architecture: x86_64 reason: Process /usr/bin/alsamixer was killed by signal 6 (SIGABRT) uid: 500 username: social os_release: Fedora release 15 (Lovelock) time: 1301516282 rating: 4 Text file: event_log, 3917 bytes Text file: maps, 5314 bytes Text file: smaps, 26062 bytes Binary file: coredump, 835584 bytes Text file: dsos, 3726 bytes Text file: backtrace, 6013 bytes
Created attachment 488923 [details] File: event_log
Created attachment 488924 [details] File: maps
Created attachment 488926 [details] File: smaps
Created attachment 488927 [details] File: dsos
Created attachment 488928 [details] File: backtrace
Adding me to CC.
See also https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/715544
I believe that this issue has similar culprit as in bug#731381 . *** This bug has been marked as a duplicate of bug 731381 ***
Hi Jaroslav, Are you sure this bug is a duplicate? Over the last year or two I've had similar reports to this but in different applications. For example check out this backtrace from KMix: https://bugs.mageia.org/show_bug.cgi?id=3391 Could there be something more interesting going on here, especially if it's not just alsamixer code that is affected?
Ping?