Hi, I have the same issue. It happens pretty often. I usually go around by closing some programs (firefox, virtual box) sometimes that's enough. Otherwise log off / log in always fixes it. Interestingly, I was able to reproduce this with a mp3! VLC was working with the MP3, whereas with the movie, VLC can read audio but not video. Totem was closing right after opening the movie or the mp3
I'm trying to get some debugging trace but it's not working. Can you help me? I have followed this article http://wiki.debian.org/HowToGetABacktrace I have installed totem with debugging symbols However after building totem, I think this didn't work as expected: dpkg -i totem-dbg_2.32.0-0ubuntu10_amd64.deb (Lecture de la base de données... 231440 fichiers et répertoires déjà installés.) Préparation du remplacement de totem-dbg 2.32.0-0ubuntu10 (en utilisant totem-dbg_2.32.0-0ubuntu10_amd64.deb) ... Dépaquetage de la mise à jour de totem-dbg ... Paramétrage de totem-dbg (2.32.0-0ubuntu10) ... file /usr/bin/totem /usr/bin/totem: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped So I used the totem from the building directory: this one is "not stripped": file ./debian/totem/usr/bin/totem ./debian/totem/usr/bin/totem: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, not stripped So I run gdb gdb ./totem-2.32.0/debian/totem/usr/bin/totem But I cannot break on gdk_x_error: (gdb) break gdk_x_error Function "gdk_x_error" not defined. I have tried answering yes to the next question but it's not helping: Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (gdk_x_error()) pending. (gdb) run 'somemovie.avi' --sync [Thread debugging using libthread_db enabled] [New Thread 0x7fffe8a52700 (LWP 30321)] [New Thread 0x7fffe7c20700 (LWP 30322)] [New Thread 0x7fffde6af700 (LWP 30325)] [New Thread 0x7fffdc875700 (LWP 30326)] [Thread 0x7fffdc875700 (LWP 30326) exited] [New Thread 0x7fffdc875700 (LWP 30327)] [New Thread 0x7fffd6c77700 (LWP 30328)] [New Thread 0x7fffd24d0700 (LWP 30329)] [New Thread 0x7fffd0d3c700 (LWP 30330)] [New Thread 0x7fffd053b700 (LWP 30331)] [New Thread 0x7fffcb709700 (LWP 30332)] The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 107 error_code 2 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.) [Thread 0x7fffcb709700 (LWP 30332) exited] [Thread 0x7fffd053b700 (LWP 30331) exited] [Thread 0x7fffd0d3c700 (LWP 30330) exited] [Thread 0x7fffdc875700 (LWP 30327) exited] [Thread 0x7fffde6af700 (LWP 30325) exited] [Thread 0x7fffe7c20700 (LWP 30322) exited] [Thread 0x7fffe8a52700 (LWP 30321) exited] [Thread 0x7fffd24d0700 (LWP 30329) exited] [Thread 0x7fffd6c77700 (LWP 30328) exited] Program exited with code 01. And I cannot get a stack: (gdb) bt No stack. I tried also this but it's not giving a lot of information $ /home/pascal/totem-2.32.0/debian/totem/usr/bin/totem --debug (totem:30865): Totem-DEBUG: Received SaveYourself(SmSaveLocal, !Shutdown, SmInteractStyleNone, !Fast) in state idle (totem:30865): Totem-DEBUG: Setting initial properties (totem:30865): Totem-DEBUG: Sending SaveYourselfDone(True) for initial SaveYourself (totem:30865): Totem-DEBUG: Received SaveComplete message in state save-yourself-done (totem:30865): Totem-DEBUG: Init of Python module (totem:30865): Totem-DEBUG: Registering Python plugin instance: BBCViewer+TotemPythonPlugin (totem:30865): Totem-DEBUG: Creating object of type BBCViewer+TotemPythonPlugin (totem:30865): Totem-DEBUG: Creating Python plugin instance (totem:30865): Totem-DEBUG: totem_playlist_add_one_mrl (): somemovie.avi (null) (null) The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 95 error_code 2 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.) Any help on how to debug this? I think it might some kind of memory issue since it often resolves by releasing memory. The xorg process takes really a lot of RAM. >From the top command all of my memory seems to be used although I have 8GB and >not much running! Mem: 8191472k total, 8114804k used, 76668k free, 154012k buffers Swap: 3664892k total, 1236k used, 3663656k free, 3788204k cached You'll find some memory usage information attached and the pmap on the xorg process: top cat /proc/sys/kernel/shmmax pmap 16629 smem -w Thanks ** Attachment added: "memory information" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/737261/+attachment/2493607/+files/memory_details.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/737261 Title: Totem fails to play anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/737261/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
