Bug 731381
Summary: | [abrt] alsa-utils-1.0.24.1-3.fc15: __list_add: Process /usr/bin/alsamixer was killed by signal 11 (SIGSEGV) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jurgen Kramer <gtmkramer> |
Component: | alsa-utils | Assignee: | Jaroslav Kysela <jkysela> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 16 | CC: | andreas.tunek, axellira, bugs.michael, gandr, glennjohnson57, igor.redhat, jamescape777, jkysela, lkundrak, lpoetter, l.vivier89, martin_sjostrand, mhlavink, nomad71st, oscar.bacho, pahan, rcrodgers622, redhat, rh-bugzilla, rmarko, shigorin, shnurapet, social, stefan.friesel, sven, thenavi, vmedrea |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | abrt_hash:2811a8ad2e8d287aa693aeb85fb31668d2b79c2d | ||
Fixed In Version: | alsa-utils-1.0.24.1-5.fc15 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-11-05 01:23:39 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jurgen Kramer
2011-08-17 13:16:56 UTC
same bug as my bug #731277. This still happens with F16 alpha and also happens on a different machine in a VM. reinstalling pulseaudio 'fixes' the problem. I will keep this bug open to see if this is fixed in beta. Package: alsa-utils-1.0.24.1-3.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Ran alsamixer out of curiosity during a period of audio output gone lost and the gnome-shell based tools not having helped either. After a reboot, reproducibly: $ alsamixer Segmentation fault (core dumped) Package: alsa-utils-1.0.24.1-3.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- This seems to happen every time I run alsamixer. Package: alsa-utils-1.0.24.1-3.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- happens when running alsamixer with no params (alsamixer -c 0 works fine) Package: alsa-utils-1.0.24.1-3.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I ran it into the console and got segmentation fault Package: alsa-utils-1.0.24.1-3.fc15 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- alsamixer issues Package: alsa-utils-1.0.24.1-3.fc15 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- when try to open alsamixer Package: alsa-utils-1.0.24.1-3.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Simply opened a terminal and typed "alsamixer". Crashed with core dump. Package: alsa-utils-1.0.24.1-3.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Open alsamixer from the terminal Package: alsa-utils-1.0.24.1-3.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Ran alsamixer from the command line with no arguments. It's a clean install of Fedora 16 beta. Package: alsa-utils-1.0.24.1-3.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Running alsamixer Package: alsa-utils-1.0.24.1-3.fc15 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- ran alsamixer as normal user Package: alsa-utils-1.0.24.1-3.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Just launch alsamixer in console (root or user) Hi, For me, when running alsamixer in a text console (Ctrl+Alt-F[2,3,4,5, ...]) the program doesn't segfault. It does when run in Konsole (KDE) or Gnome Terminal. Eric Bartoš [1] found that alsamixer -c <card number> also didn't crash. Martin Kho [1] Bug 725749, comment #8. Package: alsa-utils-1.0.24.1-3.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Alsamixer segfaults upon running. The sound card is working fine, it's an ATI SBx00 Azalia onboard a Biostar A770E3 motherboard; amizer works fine, too. Package: alsa-utils-1.0.24.1-3.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I tried to ejecute the program alsamixer Package: alsa-utils-1.0.24.1-3.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Just start. Package: alsa-utils-1.0.24.1-3.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I ran alsamixer in a terminal. I am wondering why this has not been picked up? We're at RC3 now and it is still broken. *** Bug 725749 has been marked as a duplicate of this bug. *** *** Bug 739030 has been marked as a duplicate of this bug. *** It appears like a memory corruption somewhere in the PulseAudio layer (in combination with X). According gdb, the mixer structure in alsalib - snd_mixer_attach() - gets broken after the snd_hctl_open() call with the "default" device name (this devices is redirected to the alsa pulse audio plugin by default). Hardware watchpoint on the mixer structure shows: #0 _int_free (av=0x3a885ae700, p=0x612ff0, have_lock=0) at malloc.c:4008 #1 0x0000003a89647e7a in snd_mixer_close (mixer=0x613000) at mixer.c:622 #2 0x000000000040967a in ?? () #3 0x0000003a8ca087e6 in xcb_disconnect (c=0x62d1b0) at xcb_conn.c:257 #4 0x0000003aa0c3200c in pa_client_conf_from_x11 (c=0x62cdc0, dname=<optimized out>) at pulse/client-conf-x11.c:114 #5 0x0000003aa0c0d849 in pa_context_new_with_proplist (mainloop=0x62b9e8, name=<optimized out>, p=<optimized out>) at pulse/context.c:182 #6 0x00007ffff19bf79c in pulse_new () at pulse.c:151 #7 0x00007ffff19bef80 in _snd_ctl_pulse_open (handlep=0x7fffffffe0a8, name=0x40ad3c "default", root=<optimized out>, conf=<optimized out>, mode=0) at ctl_pulse.c:698 #8 0x0000003a8963db68 in snd_ctl_open_conf (mode=0, ctl_conf=0x622d10, ctl_root=0x6131e0, name=0x40ad3c "default", ctlp=0x7fffffffe0a8) at control.c:858 #9 snd_ctl_open_noupdate (ctlp=0x7fffffffe0a8, root=0x6131e0, name=0x40ad3c "default", mode=0) at control.c:885 #10 0x0000003a8963c42b in snd_hctl_open (hctlp=0x7fffffffe0d8, name=<optimized out>, mode=<optimized out>) at hcontrol.c:75 #11 0x0000003a896476fd in snd_mixer_attach (mixer=0x613000, name=<optimized out>) at mixer.c:203 It appears that PA tries to do something with X in a terminal mode session causing that the mixer device is closed in the initialization. Reassigning to PA to get better clue.. Debugging further: It seems that there is some linking clash between shutdown() function from <sys/socket.h> and shutdown() function in the alsamixer code. The shutdown() function for socked is called from xcb_disconnect(). Reassigning back to me. Here is the patch which solves this issue with comments. It works in my environment. I will prepare new alsa-utils package for F15 and F16. http://git.alsa-project.org/?p=alsa-utils.git;a=commitdiff;h=4c09aaa5c13c2260fea57a89c47f88252da8a692 *** Bug 743268 has been marked as a duplicate of this bug. *** *** Bug 692278 has been marked as a duplicate of this bug. *** *** Bug 719712 has been marked as a duplicate of this bug. *** *** Bug 748084 has been marked as a duplicate of this bug. *** alsa-utils-1.0.24.1-5.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/alsa-utils-1.0.24.1-5.fc16 alsa-utils-1.0.24.1-5.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/alsa-utils-1.0.24.1-5.fc15 Please test and increase karma!! Hi, 24.1-5.fc16 works for me. Thanks, Martin Kho Forks for me too. Thank you. Package: alsa-utils-1.0.24.1-3.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Yep, alsa-utils-1.0.24.1-5 fixes the segfault problem (tested on F16 x86_64). Thanks. Package: alsa-utils-1.0.24.1-3.fc15 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- ran alsamixer from command line Package alsa-utils-1.0.24.1-5.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing alsa-utils-1.0.24.1-5.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-15390 then log in and leave karma (feedback). alsa-utils-1.0.24.1-5.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. alsa-utils-1.0.24.1-5.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. Under the released version of Fedora 16 on the Asus Sabertooth 990FX motherboard, I get no sound at all. The Sound settings panel shows no hardware. It's a fresh install, alsamixer doesn't crash when running from terminal, but yields: ALSA lib pulse.c:229:(pulse_connect) PulseAudio: Unable to connect: Connection refused cannot open mixer: Connection refused I've reinstalled pulseaudio but sound still isn't working. (In reply to comment #43) > Under the released version of Fedora 16 on the Asus Sabertooth 990FX > motherboard, I get no sound at all. Please don't just add new issues to unrelated bugs. This bug is about alsamixer crashing on startup. Please consult: http://fedoraproject.org/wiki/How_to_debug_sound_problems and file a new bug if necessary. Thanks. (In reply to comment #27) > Here is the patch which solves this issue with comments. It works ...for me too, applied to alsa-utils-1.0.24.2-alt2 (ALT Linux), thank you. |