Can't play two movies in a row

Bug #32433 reported by Julien Olivier
10
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

When using totem-xine-firefox-plugin to play embedded movies from http://www.davesdaily.com/mediaclips.htm, I can play a video once, but if I press "back" and then try to play another movie, it crashes.

Revision history for this message
Daniel Holbach (dholbach) wrote :

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 which you find.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Sorry, I remembered having read the comment once, so I replied a bit fast. The other bug was related, but fixed already, this is a different problem. Which version of Ubuntu, Firefox and totem do you use? Which architecture are you on? Can you try to get a backtrace?

Changed in totem:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Julien Olivier (julo) wrote :

I'm using today's Dapper: firefox-1.5.0.1 and totem-1.3.91.

For the backtrace, could you please point me to instructions on how to do that ?

Revision history for this message
Mark (twistedtexan) wrote : Re: [Bug 32433] Can't play two movies in a row

ubuntu 5.10 breezy
Mozilla Firefox 1.0.7
Totem 1.2.0
xine-lib 1.0.1

I did have 1 more problem out of the program but a reboot seemed to
correct it. My computer locked up when I made adjustments to the volume
control on the totem player panel. Remember that this is only after I
first tested Totem with out a restart. I have not had the same problem
again. I would suggest a reboot after installation. I did play 2
different movies but I didn't do that back to back. i.e. I stopped
Totem, installed the second disk, opened Totem and Played the second
movie. Thanks again. I'll keep you informed about any future problems.

On Wed, 2006-02-22 at 10:59 +0000, Daniel Holbach wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/32433
>
> Comment:
> Sorry, I remembered having read the comment once, so I replied a bit
> fast. The other bug was related, but fixed already, this is a different
> problem. Which version of Ubuntu, Firefox and totem do you use? Which
> architecture are you on? Can you try to get a backtrace?

Revision history for this message
Sebastien Bacher (seb128) wrote :

To get a backtrace:
* start firefox
* from a command line:
- gdb -p $(pidof firefox)
(gdb) continue
* back to firefox, get it crash
* to the (gdb) prompt: "thread apply all bt"

and copy the backtrace to a comment

Revision history for this message
Julien Olivier (julo) wrote :
Download full text (3.7 KiB)

OK, here is the trace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 2001741504 (LWP 21569)]
0x7785cee2 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
(gdb) thread apply all bt

Thread 5 (Thread 1999084464 (LWP 21570)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0x7769a904 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0x77e7c086 in PR_Poll () from /usr/lib/libnspr4.so
#3 0x772e6000 in NSGetModule () from /usr/lib/firefox/components/libnecko.so
#4 0x772e6745 in NSGetModule () from /usr/lib/firefox/components/libnecko.so
#5 0x77f08bb9 in nsIThread::IsMainThread ()
   from /usr/lib/firefox/libxpcom_core.so
#6 0x77e7d79d in PR_Select () from /usr/lib/libnspr4.so
#7 0x77e4d341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8 0x776a452e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 4 (Thread 1987062704 (LWP 21571)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0x77e4feec in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0x77e78207 in PR_Lock () from /usr/lib/libnspr4.so
#3 0x77e7855d in PR_WaitCondVar () from /usr/lib/libnspr4.so
#4 0x77f0af44 in NS_NewThread () from /usr/lib/firefox/libxpcom_core.so
#5 0x77f08bb9 in nsIThread::IsMainThread ()
   from /usr/lib/firefox/libxpcom_core.so
#6 0x77e7d79d in PR_Select () from /usr/lib/libnspr4.so
---Type <return> to continue, or q <return> to quit---
#7 0x77e4d341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8 0x776a452e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 3 (Thread 1967942576 (LWP 21572)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0x77e4feec in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0x77e78207 in PR_Lock () from /usr/lib/libnspr4.so
#3 0x77e7855d in PR_WaitCondVar () from /usr/lib/libnspr4.so
#4 0x772c59aa in NSGetModule () from /usr/lib/firefox/components/libnecko.so
#5 0x77e7d79d in PR_Select () from /usr/lib/libnspr4.so
#6 0x77e4d341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7 0x776a452e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 1945926576 (LWP 21578)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0x77e4feec in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0x77e78207 in PR_Lock () from /usr/lib/libnspr4.so
#3 0x77e7855d in PR_WaitCondVar () from /usr/lib/libnspr4.so
#4 0x772f0eed in NSGetModule () from /usr/lib/firefox/components/libnecko.so
#5 0x772f1741 in NSGetModule () from /usr/lib/firefox/components/libnecko.so
#6 0x77e7d79d in PR_Select () from /usr/lib/libnspr4.so
---Type <return> to continue, or q <return> to quit---
#7 0x77e4d341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#8 0x776a452e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 2001741504 (LWP 21569)):
#0 0x7785cee2 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#1 0x7785d56e in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#2 0x7785dc38 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#3 0x77c8e335 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#4 0x7693d90a in ?? () from /usr/lib/firefox/com...

Read more...

Revision history for this message
Sebastien Bacher (seb128) wrote :

What architecture do you use?

Revision history for this message
Julien Olivier (julo) wrote :

It's a pentium M, so i386.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Could you try this with Dapper again (maybe with a LiveCD)?

Revision history for this message
Julien Olivier (julo) wrote :

It seems fixed now. You can close it and I'll re-open it if it re-appears.

Thanks !

Revision history for this message
Sebastien Bacher (seb128) wrote :

Closing as fixed so. Feel free to reopen if you get the issue again

Changed in totem:
status: Needs Info → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.