197695 - Real Player 8 Plugin no longer recognized

Status: RESOLVED DUPLICATE of bug 198562

(Core Graveyard :: Plug-ins, defect)

Description

[Marc Williams]

User-Agent:       Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.3) Gecko/20030313
Build Identifier: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.3) Gecko/20030313

After upgrading to Mozilla 1.3, my Realplayer (8) plugin is no longer recognized
by Mozilla when running about:plugins

Reproducible: Always

Steps to Reproduce:
1.Install the Real plugins in the normal fashion
2.Perform about:plugins
3.

Actual Results:  
The Real plugin is not displayed

Expected Results:  
Recognize the plugin the same as it recognizes all my other plugins

I *think* it was working ok with Moz 1.3b but not positive.
I am using Realplayer 8 instead of RealOne (9) which I could never get working
on *any* version of Moz.

Comment 1

[Matthias Versen [:Matti]]

Which compiler do you used to compile your build ?

Comment 2

[Marc Williams]

Whatever comes with Red Hat 8.0.  It's a pretty stock installation.

Come to think of it, it's probably GCC 3.x since my Sun Java didn't work either
and had to install Blackdown in order to get that working.

Funny that all this would break between 1.3b and 1.3.

Comment 3

[Marc Williams]

Oh, and I didn't compile anything either but rather used the RH8.0 GTK2 RPMs
recently made available from Mozilla.

Comment 4

[Boris Zbarsky [:bzbarsky]]

Yeah, those RPMs are built with gcc 3.2.  Chances are, no stock C++ plugin
binaries will work with them...

Comment 5

[Matthias Versen [:Matti]]

based on bug 197387 i confirm this one.
It seems that the fix in bug 154206 doesn't work with Realplayer 8

Comment 6

[Dan Mosedale (:dmosedale, :dmose)]

Actually, the RealPlayer 8.0 plugin works fine with gcc 3.2 builds.  I bet this
is a GTK1 / GTK2 incompatibility issue.

Comment 7

[Matthias Versen [:Matti]]

*** Bug 199028 has been marked as a duplicate of this bug. ***

Comment 8

[Marc Williams]

I don't know if it's a gtk1/gtk2 issue or not.  All I know is that merely
changing from Moz 1.3b to 1.3 caused this problem.  Nothing else changed on my
system.  I would think that if it was a gtk1/gtk2 issue, Moz 1.3b would have had
the same problem.  But maybe not.

Comment 9

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

*** This bug has been marked as a duplicate of 198562 ***