Error popup after successful playback in Firefox

Thanks for your bug. I've no such issue on my edgy desktop, do you use totem-xine or totem-gstreamer? Could you try with the new totem 1.5.91 (the mozilla plugin got quite some work for that version) if you still have the issue?

On Sun, Aug 13, 2006 at 02:40:47PM -0000, Sebastien Bacher wrote:
> Thanks for your bug. I've no such issue on my edgy desktop, do you use
> totem-xine or totem-gstreamer? Could you try with the new totem 1.5.91
> (the mozilla plugin got quite some work for that version) if you still
> have the issue?

totem-gstreamer. The plugin has always done this for me in the past.
Perhaps it has something to do with my Firefox cache settings.

In current Edgy, the situation has gotten much worse. The plugin does not
work at all, and instead I get a "Click here to download plugin". Perhaps
this is related to the Firefox 2.0 beta?

Firefox produces no output to provide a clue why the plugin isn't used.

Are you saying that it works for you with the current firefox?

--
 - mdz

firefox doesn't start on my edgy desktop at the moment since I deleted .firefox to make sure the evolution startup issue was not due to some firefox config, it displays a "Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system.". I've not tried to debug it (restart the box makes no difference, any clue on where it's looking for that is welcome) since I use epiphany anyway. Does "about:plugins" list the totem plugin? Does it work with epiphany?

On Sun, Aug 13, 2006 at 07:23:03PM -0000, Sebastien Bacher wrote:
> firefox doesn't start on my edgy desktop at the moment since I deleted
> .firefox to make sure the evolution startup issue was not due to some
> firefox config, it displays a "Firefox is already running, but is not
> responding. To open a new window, you must first close the existing
> Firefox process, or restart your system.". I've not tried to debug it
> (restart the box makes no difference, any clue on where it's looking for
> that is welcome) since I use epiphany anyway. Does "about:plugins" list
> the totem plugin? Does it work with epiphany?

No, about:plugins does not list it.

For your firefox, try rm -f ~/.mozilla/firefox/lock. It may be that a new
process is reusing the same pid.

I tested epiphany, and the plugin is shown in about:plugins, the video is
displayed and there is no error popup, but the video plays much too fast. I
think that's related to the new totem, and not epiphany, as it happens even
when I play the movie using totem standalone.

Once the plugin is working again in Firefox, I can test using a clean
profile and see if that helps.

--
 - mdz

On Sun, Aug 13, 2006 at 12:36:13PM -0700, Matt Zimmerman wrote:
> Once the plugin is working again in Firefox, I can test using a clean
> profile and see if that helps.

OK, symlinking the totem plugin from /usr/lib/mozilla/plugins to
/usr/lib/mozilla-firefox/plugins gets the plugin loaded and visible in
about:plugins again (Ian, why is /usr/lib/mozilla no longer searched?).

However, Firefox crashes when the plugin is activated on the example page I
mentioned:

** Message: NP_Initialize

** Message: totem_plugin_new_instance
totemBasicPlugin ctor [0x8cdb1c0]
mode 1
mime type: video/mpeg
argv[0] src video/carwreck.mpg
/usr/lib/firefox/firefox-bin: symbol lookup error: /usr/lib/totem/libtotem-basic-plugin.so: undefined symbol: NS_CStringContainerInit

ldd -r shows a few other unresolved symbols in the plugin. They all seem to
come from libxpcom.so and libxpcom_core.so.

Are you able to reproduce the problem with the video playing at the wrong speed
even with totem standalone? Should I file a bug about that?

--
 - mdz

right, the issue was due to .mozilla, thank you for the pointer

The plugin should be fixed for firefox too with that update:

" totem (1.5.91-1ubuntu2) edgy; urgency=low
 .
   * debian/totem-mozilla.links:
     - make links for firefox too
   * debian/rules:
     - use "-V 'libtotem-plparser1 (>= 1.5.1)'" for the dh_makeshlibs call
     - use "-L libtotem-plparser1 -l debian/libtotem-plparser1/usr/lib"
       for the dh_shlibdeps call"

the video plays at the wrong speed with totem-gstreamer or "gst-launch playbin uri=", totem-xine or xine works fine, please open a bug on gst-plugins-ugly0.10 about that

could you open an another bug about the plugin not being correctly linked too? I get the same issue after upgrading firefox again

Matt Zimmerman writes ("[Bug 56085] Re: [Bug 56085] Re: Error popup after successful playback in Firefox"):
> OK, symlinking the totem plugin from /usr/lib/mozilla/plugins to
> /usr/lib/mozilla-firefox/plugins gets the plugin loaded and visible in
> about:plugins again (Ian, why is /usr/lib/mozilla no longer searched?).

I don't know; I can't see anything relevant in the changelog but it's
quite possibly an upstream or Debian change.

> However, Firefox crashes when the plugin is activated on the example page I
> mentioned:

This might be related to the problem with evolution. I'll look into
that first.

Ian.

On Sun, Aug 13, 2006 at 08:21:36PM -0000, Sebastien Bacher wrote:
> the video plays at the wrong speed with totem-gstreamer or "gst-launch
> playbin uri=", totem-xine or xine works fine, please open a bug on gst-
> plugins-ugly0.10 about that

Bug #56374 filed.

> could you open an another bug about the plugin not being correctly
> linked too? I get the same issue after upgrading firefox again

Someone else already reported bug #56333 which sounds like the same issue,
so I just added info there and confirmed it.

--
 - mdz

I can only re-test this once bug #56333 is fixed.

The other bug has been fixed, could you try if that one is fixed too now?

Seems to be fixed now. Thanks!