Crash when seeking/playing .mpg file + seeking

Thanks for your bug. Do you use totem-gstreamer or totem-xine? Could you run it from a command line an note any message when it exit? If it's crashing, could you run it with gdb to get a backtrace?
- gdb totem
(gdb) run
... get the crash
(gdb) thread apply all bt

I don't know if I'm using totem-gstreamer or totem-xine, how can I check it ?

This is what I have on the shell (ALL my shell hostory copy/pasted) :

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1293063248 (LWP 7202)]
---Type <return> to continue, or q <return> to quit---
0xb3922e46 in mpeg2_init_fbuf () from /usr/lib/libmpeg2.so.0
(gdb) thread apply all bt

Thread 30 (Thread -1374917712 (LWP 7227)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb752eeec in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb753a5dc in ?? () from /usr/lib/libgthread-2.0.so.0
#3 0x08444830 in ?? ()
#4 0x080b6920 in ?? ()
#5 0xae0c6384 in ?? ()
#6 0xb759208a in gst_object_unref () from /usr/lib/libgstreamer-0.10.so.0
#7 0xb7306d8c in g_async_queue_push_sorted () from /usr/lib/libglib-2.0.so.0
#8 0xb733a4ce in g_thread_pool_free () from /usr/lib/libglib-2.0.so.0
#9 0xb73385a2 in g_static_private_free () from /usr/lib/libglib-2.0.so.0
#10 0xb752c341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#11 0xb71ac4ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 29 (Thread -1366525008 (LWP 7226)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb752eeec in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb753a5dc in ?? () from /usr/lib/libgthread-2.0.so.0
#3 0x08444830 in ?? ()
#4 0x080b6920 in ?? ()
---Type <return> to continue, or q <return> to quit---
#5 0xae8c7384 in ?? ()
#6 0xb759208a in gst_object_unref () from /usr/lib/libgstreamer-0.10.so.0
#7 0xb7306d8c in g_async_queue_push_sorted () from /usr/lib/libglib-2.0.so.0
#8 0xb733a4ce in g_thread_pool_free () from /usr/lib/libglib-2.0.so.0
#9 0xb73385a2 in g_static_private_free () from /usr/lib/libglib-2.0.so.0
#10 0xb752c341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#11 0xb71ac4ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 28 (Thread -1341035600 (LWP 7225)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb752eeec in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb753a5dc in ?? () from /usr/lib/libgthread-2.0.so.0
#3 0x08444830 in ?? ()
#4 0x080b6920 in ?? ()
#5 0xb0116384 in ?? ()
#6 0xb759208a in gst_object_unref () from /usr/lib/libgstreamer-0.10.so.0
#7 0xb7306d8c in g_async_queue_push_sorted () from /usr/lib/libglib-2.0.so.0
#8 0xb733a4ce in g_thread_pool_free () from /usr/lib/libglib-2.0.so.0
#9 0xb73385a2 in g_static_private_free () from /usr/lib/libglib-2.0.so.0
#10 0xb752c341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#11 0xb71ac4ee in clone () from /lib/tls/i686/cmov/libc.so.6

---Type <return> to continue, or q <return> to quit---
Thread 27 (Thread -1358132304 (LWP 7224)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb752eeec in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb753a5dc in ?? () from /usr/lib/libgthread-2.0.so.0
#3 0x08444830 in ?? ()
#4 0x080b6920 in ?? ()
#5 0xaf0c8384 in ?? ()
#6 0xb759208a in gst_object_unref () from /usr/lib/libgstreamer-0.10.so.0
#7 0xb7306d8c in g_async_queue_push_sorted () from /usr/lib/libglib-2.0...

It looks like you are using totem-gstreamer. one way to check is to run "apt-cache policy totem-gstreamer" if its installed you are using it if its not installed please try with totem-xine. only one can be on your system at a time (they conflict)

I have totem-gstreamer.

  Installed: 1.4.3-0ubuntu1
  Candidate: 1.4.3-0ubuntu1

totem-xine isn't installed.

according to the backtrace the crash happens to /usr/lib/libmpeg2.so.0, reassigning

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

Looks like you guys fixed the issue. I can't reproduce it anymore. Thanks! :)

Thanks for the feedback.