GNOME Bugzilla – Bug 624657
Totem crashes when adjusting volume
Last modified: 2010-07-20 18:52:42 UTC
Sometimes when i try to adjust the volume by hovering over the volume control icon in totem and using the wheel, the player crashes. ive managed to reproduce this many times, but it can tike a while for the error to occur. sometimes the player crashes as soon as you reach the mute-point, sometimes it takes a few tries up and down from max to mute to max volume for the player to crash. this error occurs with every type of media file ive tried; ogg, ogm, mkv, avi, flac and mp3. Here the output from totem --debug nxxs@nxxs-desktop:~$ totem --debug (totem:27934): Totem-DEBUG: Received SaveYourself(SmSaveLocal, !Shutdown, SmInteractStyleNone, !Fast) in state idle (totem:27934): Totem-DEBUG: Setting initial properties (totem:27934): Totem-DEBUG: Sending SaveYourselfDone(True) for initial SaveYourself (totem:27934): Totem-DEBUG: Received SaveComplete message in state save-yourself-done (totem:27934): Totem-DEBUG: Init of Python module (totem:27934): Totem-DEBUG: Registering Python plugin instance: BBCViewer+TotemPythonPlugin (totem:27934): Totem-DEBUG: Creating object of type BBCViewer+TotemPythonPlugin (totem:27934): Totem-DEBUG: Creating Python plugin instance (totem:27934): Totem-DEBUG: totem_playlist_add_one_mrl (): Dunproofin-OnlyMashupsCanBreakYourHeart.mp3 (null) (null) Segmentation fault nxxs@nxxs-desktop:~$
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance! Given that stacktrace, it's hard to tell. If you can reproduce it while running under gdb (see http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details about how to do this), that might help getting a better trace if you've already got debug packages installed.
Created attachment 166110 [details] Stacktrace of the error
Comment on attachment 166110 [details] Stacktrace of the error nxxs@nxxs-desktop:~$ gdb totem GNU gdb (GDB) 7.1-ubuntu Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/totem...Reading symbols from /usr/lib/debug/usr/bin/totem...done. done. (gdb) run Starting program: /usr/bin/totem [Thread debugging using libthread_db enabled] [New Thread 0xb6f7db70 (LWP 26359)] [New Thread 0xb677cb70 (LWP 26360)] [Thread 0xb677cb70 (LWP 26360) exited] [New Thread 0xb677cb70 (LWP 26373)] [New Thread 0xb5db9b70 (LWP 26374)] [New Thread 0xb53ffb70 (LWP 26375)] [New Thread 0xb0bfdb70 (LWP 26377)] [Thread 0xb0bfdb70 (LWP 26377) exited] Program received signal SIGSEGV, Segmentation fault. 0x00000000 in ?? () (gdb)
just found out this problem also exists when adjusting volume by use of the arrow-keys.
Program received signal SIGSEGV, Segmentation fault. 0x00000000 in ?? () (gdb) here you should do 'thread apply all bt' to get traces and make sure you have debuginfo packages installed for totem.
Created attachment 166171 [details] New and complete Stack
(In reply to comment #6) > Created an attachment (id=166171) [details] > New and complete Stack Unfortunately that stack's still missing symbols in important places (notice the large number of "??"s in the backtrace). Could you install all the GStreamer debug packages and produce another backtrace please? Thanks.
Created attachment 166221 [details] stack after installing bug-buddy
Relevant bits:
+ Trace 222942
Thread 1 (Thread 0xb7fd8750 (LWP 13711))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 533427 ***