Bonnie,
Thanks again. As I mentioned yesterday, removing 'nspluginwrapper'
fixed the problem. Interesting, however, is that with my x86_64 SL 5.5
only the i386 flash-plugin is installed and available via YUM. In the
spirit of 'if it ain't broke, don't fix it', I think I will leave it
that way.
Tom R.
On Fri, 2012-11-02 at 08:46 -0500, Bonnie King wrote:
> Thanks Tom,
>
> I've tested and I'm able to reproduce the crash on x86_64 with:
>
> * firefox.x86_64 0:10.0.10-1.el5_8
> * flash-plugin-11.2.202.243-release.i386 or
> flash-plugin-11.2.202.243-release.x86_64,
> * nspluginwrapper installed
>
> No segfault with flash-plugin-11.2.202.243-release.x86_64 without
> nspluginwrapper, or with previous Firefox (10.0.8).
>
> On 11/01/2012 11:14 AM, Tom Rosmond wrote:
> > Thanks for the advice. Removing 'nspluginwrapper' looks like it fixed
> > the problem. The seqfaults seemed to be unique to the Google website,
> > and now Google is working. I assume SL installs the proper plugins as
> > part of Yum updates, so hopefully I have everything I need.
> >
> > T. Rosmond
> >
> >
> >
> > On Thu, 2012-11-01 at 08:52 -0500, Bonnie King wrote:
> >> Hello,
> >>
> >>>
> >>> *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown
> >>> variable>) in NPN_GetValue()
> >>>
> >>> [1] Segmentation fault firefox
> >>> [2007]cedar /home/rosmond:
> >>
> >> I don't know what's causing the segfault (some plugin seems likely), but
> >> the NSPlugin Viewer WARNING is seen with nspluginwrapper, which enables
> >> you to use the 32-bit Flash plugin on 64-bit systems (necessary before
> >> there was a 64-bit plugin).
> >>
> >> If you use the flash plugin for your architecture and uninstall
> >> nspluginwrapper, you won't see the warning. I'm not sure it's related
> >> to your crash, since I see the message anywhere nspluginwrapper is
> >> installed and it seems to be harmless.
> >>
> >> In any case, there should be no need for nspluginwrapper if you have the
> >> appropriate flash plugin installed.
> >>
> >>>
> >>> ********************************************************
> >>>
> >>> I'm not a browser expert, so would appreciate any advice to correct the
> >>> problem. I could try to revert to the previous version, but would
> >>> prefer not to.
> >>>
> >>> T. Rosmond
> >>
> >
>
|