Bug 725749 - alsamixer: Program received signal SIGSEGV, Segmentation fault.
Summary: alsamixer: Program received signal SIGSEGV, Segmentation fault.
Keywords:
Status: CLOSED DUPLICATE of bug 731381
Alias: None
Product: Fedora
Classification: Fedora
Component: alsa-utils
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Kysela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-26 12:58 UTC by Martin Kho
Modified: 2011-11-01 18:39 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-11-01 18:39:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Output from "thread apply all bt full" (gdb) (2.89 KB, application/octet-stream)
2011-07-26 18:18 UTC, Martin Kho
no flags Details

Description Martin Kho 2011-07-26 12:58:39 UTC
Description of problem:

Running gdb alsamixer output:

Program received signal SIGSEGV, Segmentation fault.
__list_add (next=0x613000, prev=0x6134c8, _new=0x6134c8) at ../../include/list.h:46
46              prev->next = _new;

Version-Release number of selected component (if applicable):
alsa-utils-1.0.24.1-3.fc15.x86_64

How reproducible:
always

Steps to Reproduce:
1. Open a console
2. Run alsamixer
3. "Segmentation fault"
  
Actual results:
alsamixer outputs " Segmentation fault"

Expected results:
alsamixer starts up

Additional info:

Comment 1 Martin Kho 2011-07-26 18:18:58 UTC
Created attachment 515337 [details]
Output from "thread apply all bt full" (gdb)

Comment 2 dinyar.rabady+spam 2011-10-13 22:31:57 UTC
I can reproduce this bug. (Thinkpad X200s with Fedora 16 isntalled through anaconda upgrade from DVD. x86_64 architecture.)

Comment 3 Erik Bartoš 2011-10-16 18:13:00 UTC
1. Run "alsamixer" in console
3. "Segmentation fault"

Fresh Fedora 16 Beta installation through preupgrade.

Comment 4 Erik Bartoš 2011-10-20 08:53:57 UTC
More comments:

1. I have multi-user installation of Fedora 16 Beta. So booting is into console. In console works sound and also "alsamixer" is running.
2. After logging into X by "startx", the "alsamixer" is not running, showing segmentation fault, also "aplay -l" shows no sound card device.

I think there are some permission problems, but now I cann't  define them.

Comment 5 Erik Bartoš 2011-10-21 17:04:17 UTC
Solved!
I've reinstall ConsoleKit stuff, plus new updates of F16. Sound is working in console and gnome-shell.

Comment 6 Martin Kho 2011-10-21 17:30:05 UTC
Hi,

Tried reinstalling ConsoleKit[-libs,-x11], with no change. For me, alsamixer still segfaults. Btw. I'm running KDE with all latest updates installed and have never had any problems with sound.

@Erik: What new updates made alsamixer stop crashing?

Martin Kho

Comment 7 Martin Kho 2011-10-21 18:43:57 UTC
Hi,

alsamixer runs at the console (ALT+CRL-F[2,3,4,...]) okay, the issue appears only when in graphics mode. In Konsole (KDE, 4.7.2) or Gnome Terminal (3.2.1) alsamixer segfault. My graphics card is a NV4B and I use the nouveau driver.

Hope this helps,

Martin Kho

Comment 8 Erik Bartoš 2011-10-22 13:36:34 UTC
Hard to say which updates, I'm updating daily a lot of packages.

The correct command for alsamixer is "alsamixer -c 0", without the options is "segmentation fault" also in my case. But sound is working...

Btw, I've also found out, that my installation (Fedora 16 beta, Nvidia driver, gnome-shell) is slow in comparison to previous version. I'm trying to find out why.

Comment 9 Martin Kho 2011-10-22 14:43:23 UTC
Hi,

Just saw that this bug is a duplicate of bug #731381. Please close this report.


Thanks,

Martin Kho.

Comment 10 Jaroslav Kysela 2011-11-01 18:39:36 UTC

*** This bug has been marked as a duplicate of bug 731381 ***


Note You need to log in before you can comment on or make changes to this bug.