264538 - Firefox can't load RealPlayer plugin

Status: RESOLVED INCOMPLETE

(Plugins Graveyard :: RealPlayer (Real), defect)

Description

[Boris Zbarsky [:bzbarsky]]

BUILD: 0.10.1 or 2004-10-14-21 branch Firefox nightly on Linux.

STEPS TO REPRODUCE:
1)  Make sure you have no firefox profile
2)  Make sure you have rpnp.so in your $MOZ_PLUGIN_PATH
3)  Start firefox

ACTUAL RESULTS:  Firefox outputs:

LoadPlugin: failed to initialize shared library /home/bzbarsky/plugins/rpnp.so
[/home/bzbarsky/plugins/rpnp.so: undefined symbol: __pure_virtual]

and RealPlayer does not appear in about:plugins

EXPECTED RESULTS:  Load and use the RealPlayer plugin

NOTE: This works fine in a GTK1 build of SeaMonkey on the same system.

Comment 1

[/\/\arcio Galli]

Yes. Here is my experience. Using linux * Firefox PR1. The broken plugin icon
links to the installer popup which gives me a couple steps and the success
installation message. THen the page is reloaded and nothing happens. 

Comment 2

[Boris Zbarsky [:bzbarsky]]

Nominating.  This is one of the most popular plug-ins out there...

Comment 3

[Asa Dotzler [:asa]]

Johnny, can you look at this?

Comment 4

[Asa Dotzler [:asa]]

We need a new plug-in from Real. ->rafael.

Comment 5

[Alexander Opitz]

This seems only for RealPlayer 8 ... RealPlayer 10 uses the helix code and have
a nphelix.so and nphelix.xpt file included.

Comment 6

[Alexander Opitz]

Hmmm, is this a problem on the build system?

the __pure_virtual is defined from the "old ABI wrapper" code in nsAppRunner.
This code is normaly included in ff and can be disabled by a configuration option.

The disable configuration option isn't used, but some builds in firefox/latest
do not have the symbol defined. (2004-10-29-09-0.11 works with rpnp.so but
2004-10-06-09-0.11 don't work). So there is a firefox since the report where it
worked.

Comment 7

[Alexander Opitz]

Bad, bad ... the problem is now inside firefox1.0

Comment 8

[Christian :Biesinger (don't email me, ping me on IRC)]

note bug 178805

Comment 9

[Tracey]

Not done this before - have never had a problem with Firefox before!  Anyway,
just to say that I also have this problem but I'm using Windows XP Home Edition
- not Linux as this bug mentions.  I don't know whether I ought to have reported
this as a separate bug?  Can you advise if necessary and I'll submit it as a new
bug.

Comment 10

[Boris Zbarsky [:bzbarsky]]

> I don't know whether I ought to have reported this as a separate bug?

You should have, yeah.  This bug is Linux-specific.

Could we possibly get this fixed for 1.1?  I'd really like to have my plugins
working with Firefox...

Comment 11

[Asa Dotzler [:asa]]

Not a blocker. Users should get the new version. We can release note this.

Comment 12

[Wayne Mery (:wsmwk)]

bug 178805 comment 27 indicates bug 178805 may be gone.
so is this still a problem?

Comment 13

[Boris Zbarsky [:bzbarsky]]

It's a problem with the build at <http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2006-11-18-04-trunk/firefox-3.0a1.en-US.linux-i686.tar.bz2>, yes.

Comment 14

[Reed Loden [:reed]]

--> addons.mozilla.org :: Plugins

Comment 15

[Boris Zbarsky [:bzbarsky]]

Uh... what does this have to do with addons?  This is a core widget issue, no?

Comment 16

[Reed Loden [:reed]]

(In reply to comment #15)
> Uh... what does this have to do with addons?  This is a core widget issue, no?

I read the bug incorrectly (see ping on IRC).

--> Core :: Plug-ins

Comment 17

[Boris Zbarsky [:bzbarsky]]

Look.  Just stop messing with the bug.  And _especially_ stop nuking flags.

Comment 18

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Is this only a problem with old versions of the plugin?

If it does affect latest version as well then this should probably be marked [wanted-1.9]

Comment 19

[Boris Zbarsky [:bzbarsky]]

The newer versions of the plug-in flat-out refuse to run over here.  The one that we broke is the latest one I've found that actually works (or used to work).

Given that it's basically never worked with Firefox, I guess I should just stop caring... except that now that Seamonkey is also using GTK2 it has the same issues.

Comment 20

[Benjamin Smedberg]

Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/

If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.