GNOME Bugzilla – Bug 169493
gnome-volume-control crashes on pauze / unpauze totem
Last modified: 2005-03-08 17:25:57 UTC
Distribution: Debian 3.1 Package: gnome-media Severity: critical Version: GNOME2.10.0 2.9.x Gnome-Distributor: Ubuntu Synopsis: gnome-volume-control crashes on pauze / unpauze totem Bugzilla-Product: gnome-media Bugzilla-Component: gnome-volume-control [was: gmix] Bugzilla-Version: 2.9.x BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: gnome-volume-control crashes every time you pauze / unpauze a song in totem-xine. Steps to reproduce the crash: 1. open gnome-volume-control 2. open totem 3. play song with totem 4. pauze song 5. woops: gnome-volume-control crashes Expected Results: No crash. How often does this happen? Every time. Additional Information: console output: htimon@timondell:~$ gnome-volume-control gnome-volume-control: simple.c:1472: snd_mixer_selem_get_playback_volume: Assertion `elem->type == SND_MIXER_ELEM_SIMPLE' failed. htimon@timondell:~$ 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) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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 -1222760288 (LWP 13771)] (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 56539
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-07 11:12 ------- 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.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces.
*** This bug has been marked as a duplicate of 166892 ***