After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 164521 - Crash when doing stuff with sound in background
Crash when doing stuff with sound in background
Status: RESOLVED DUPLICATE of bug 156921
Product: gnome-media
Classification: Deprecated
Component: gnome-volume-control
unspecified
Other other
: Normal normal
: ---
Assigned To: gnome media maintainers
gnome media maintainers
Depends on:
Blocks:
 
 
Reported: 2005-01-18 20:51 UTC by John Spray
Modified: 2005-01-18 21:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description John Spray 2005-01-18 20:51:56 UTC
Distribution: Debian testing/unstable
Package: gnome-media
Severity: normal
Version: GNOME2.9.4 unspecified
Gnome-Distributor: GNOME.Org
Synopsis: Crash when doing stuff with sound in background
Bugzilla-Product: gnome-media
Bugzilla-Component: gnome-volume-control [was: gmix]
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.9.1)
Description:
Description of the crash:
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?)



Debugging Information:

Backtrace was generated from '/opt/gnome2/bin/gnome-volume-control'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1089687232 (LWP 13276)]
0xffffe410 in __kernel_vsyscall ()
  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 741
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 ??
    from /lib/tls/i686/cmov/libc.so.6
  • #7 ??
  • #8 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 ??
  • #31 ??
  • #32 ??
  • #33 ??
  • #34 ??
  • #35 ??
  • #36 ??
  • #37 ??
  • #38 ??
  • #39 ??
  • #40 ??
  • #41 ??
  • #42 ??
  • #43 _IO_file_write
    from /lib/tls/i686/cmov/libc.so.6
  • #44 _IO_do_write
    from /lib/tls/i686/cmov/libc.so.6
  • #45 _IO_file_xsputn
    from /lib/tls/i686/cmov/libc.so.6
  • #46 ??
    from /lib/tls/i686/cmov/libc.so.6
  • #47 __after_morecore_hook
    from /lib/tls/i686/cmov/libc.so.6
  • #48 ??
  • #49 stdout
    from /lib/tls/i686/cmov/libc.so.6
  • #50 free
    from /lib/tls/i686/cmov/libc.so.6
  • #51 __after_morecore_hook
    from /lib/tls/i686/cmov/libc.so.6
  • #52 ??
  • #53 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #54 _IO_2_1_stdout_
    from /lib/tls/i686/cmov/libc.so.6
  • #55 __assert_fail
    from /lib/tls/i686/cmov/libc.so.6
  • #56 ??
    from /usr/lib/libasound.so.2
  • #57 ??
  • #58 ??
    from /usr/lib/libasound.so.2
  • #59 in6addr_loopback
    from /lib/tls/i686/cmov/libc.so.6
  • #60 ??
    from /usr/lib/libasound.so.2
  • #61 ??
  • #62 ??
    from /usr/lib/libasound.so.2
  • #63 ??
  • #64 ??
  • #65 ??
  • #66 snd_mixer_selem_get_playback_volume
    from /usr/lib/libasound.so.2




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-18 15:51 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-media".
   Setting to default milestone for this product, '---'
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.

Comment 1 Elijah Newren 2005-01-18 21:17:43 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in
determining the cause of the crash. This bug has been reported, but we really
need a stack trace with debugging symbols to look further.  If you can produce
one (see http://bugzilla.gnome.org/getting-traces.cgi for more information),
please add it to bug 156921.

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