GNOME Bugzilla – Bug 156921
Adjusting Mixer for Soundless Audigy 2
Last modified: 2006-07-04 12:23:32 UTC
Distribution: Debian testing/unstable Package: gnome-media Severity: critical Version: GNOME2.8.1 2.8.x Gnome-Distributor: Ubuntu Synopsis: Adjusting Mixer for Soundless Audigy 2 Bugzilla-Product: gnome-media Bugzilla-Component: CDDBSlave2 Bugzilla-Version: 2.8.x BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: I still have no sound after adjusting mixer. Steps to reproduce the crash: 1. changing controls on alsa mixer 2. 3. Expected Results: To properly configure Audigy 2 for sound. How often does this happen? frequently Additional Information: I have startup music when booting but no sound on either the CD Plyer or Xmms. Debugging Information: Backtrace was generated from '/usr/bin/gnome-volume-control' (no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1088377600 (LWP 5532)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in __kernel_vsyscall ()
+ Trace 51483
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-10-30 14:31 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-media". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was ipagansky@yahoo.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Can you please configure GStreamer and libalsa with debugging symbols (or install debuginfo debian packages) and re-run this?
Looks like this matches the stack trace in bug 156995, which has been marked as a duplicate of 148329. I'm reopening to mark it as such.
*** This bug has been marked as a duplicate of 148329 ***
Elijah, in this case I don't think the stack traces match. I'd still like to see a backtrace with actual debug symbols. Therefore, I'm re-setting it to NEEDINFO. ;).
*** Bug 158315 has been marked as a duplicate of this bug. ***
*** Bug 158317 has been marked as a duplicate of this bug. ***
*** Bug 162435 has been marked as a duplicate of this bug. ***
*** Bug 164521 has been marked as a duplicate of this bug. ***
Extra info from bug 164521: I seem to get this crash when I'm pausing/unpausing, skipping tracks in either rhythmbox (gst) or beep-media-player (non-gst). The device that gst-mixer is looking at is an ALSA device. Got this console output upon crash: gnome-volume-control: simple.c:1471: snd_mixer_selem_get_playback_volume: Assertion `elem->type == SND_MIXER_ELEM_SIMPLE' failed. /opt/gnome2/share/bug-buddy/gdb-cmd:1: Error in sourced command file: Previous frame inner to this frame (corrupt stack?)
To the reporter of #164521: I think that implies a race condition in your sound card driver. The assertion is internal to ALSA. Can you report it at http://www.alsa-project.org/?
Bug reported in ALSA: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=835
*** Bug 164783 has been marked as a duplicate of this bug. ***
this is NOTGNOME. given the fact that we do not see any more duplicates is likeley has been fixed in ALSA.