GNOME Bugzilla – Bug 582067
Player crashes on resume/suspend if playing visual effects
Last modified: 2009-05-13 05:54:26 UTC
Steps to reproduce: 1. play an mp3 file or stream 2. suspend the computer, with one of several visualizations on (see below) 3. resume; 1-2 seconds of audio can be heard (buffered?) Stack trace: $ gdb totem GNU gdb 6.8-debian Copyright (C) 2008 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"... (gdb) run Starting program: /usr/bin/totem [Thread debugging using libthread_db enabled] [New Thread 0xb680fa60 (LWP 28039)] [New Thread 0xb636eb90 (LWP 28043)] [New Thread 0xb5adcb90 (LWP 28044)] [Thread 0xb5adcb90 (LWP 28044) exited] /var/lib/python-support/python2.6/gdata/tlslite/utils/cryptomath.py:9: DeprecationWarning: the sha module is deprecated; use the hashlib module instead import sha [New Thread 0xb5adcb90 (LWP 28051)] [New Thread 0xb4580b90 (LWP 28052)] [New Thread 0xafd41b90 (LWP 28053)] [New Thread 0xaf540b90 (LWP 28054)] [New Thread 0xaed3fb90 (LWP 28055)] [New Thread 0xae0ffb90 (LWP 28056)] [New Thread 0xad8feb90 (LWP 28057)] [Thread 0xad8feb90 (LWP 28057) exited] The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 1394 error_code 11 request_code 133 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program exited with code 01. Other information: Affected (built-in) plugins: libvisual jess plugin plugin v.0.1 libvisual infinite plugin plugin v.0.1 libvisual libvisual corona plugin plugin v.0.1 libvisual Bumpscope plugin plugin v.0.0.1 GOOM: What a GOOM! GOOM: What a GOOM! 2k1 edition (by the way, something's odd with the names)
Please gather a backtrace as mentioned in the error message.
(I'm running "$ gdb --args totem --sync") Setting a breakpoint on gdk_x_error always produces: (gdb) b gdk_x_error Function "gdk_x_error" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (gdk_x_error) pending. And the breakpoint is never reached. I try to set the breakpoint both before and during execution ('run', Ctrl-C, 'b gdk_x_error'). If I set the breakpoint on 'exit', this is the trace I get:
+ Trace 215294
What should I do now?
(In reply to comment #2) > What should I do now? Install debug symbols for GTK+ and try again. It's failing to find the gdk_x_error symbol because it doesn't have the symbol list for GDK.
Breakpoint 1, gdk_x_error (display=0xa08c3a8, error=0xaf443688) at /build/buildd/gtk+2.0-2.16.1/gdk/x11/gdkmain-x11.c:614 614 /build/buildd/gtk+2.0-2.16.1/gdk/x11/gdkmain-x11.c: No such file or directory. in /build/buildd/gtk+2.0-2.16.1/gdk/x11/gdkmain-x11.c (gdb) bt
+ Trace 215297
Can you also install the GStreamer and gst-plugins-* debug symbols please?
Created attachment 134490 [details] backtrace with gstreamer dbg symbols
Thanks for that. This looks like a duplicate of bug #351784, but there are still questions to be answered there. Could you get a debug log with the following command, and attach it to bug #351784 please? GST_DEBUG_NO_COLOR=1 GST_DEBUG=*:5 totem &> totem.log The log will probably be quite big, and will need compressing. Thanks. *** This bug has been marked as a duplicate of 351784 ***
> GST_DEBUG_NO_COLOR=1 GST_DEBUG=*:5 totem &> totem.log > > The log will probably be quite big, and will need compressing. Thanks. -rw-r--r-- 1 ariel ariel 2875052 2009-05-12 21:00 totem.log.bz2 Bugzilla says "The file you are trying to attach is 2808 kilobytes (KB) in size. Non-patch attachments cannot be more than1000 KB" I recall having seen a link to a site commonly used to upload large log files. What was it?
You could try rapidshare.com. Please post the link in bug #351784. Thanks.