Bug 1010650 - abundant error messages with Adobe plugins
abundant error messages with Adobe plugins
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: nspluginwrapper (Show other bugs)
6.4
x86_64 Linux
unspecified Severity medium
: rc
: ---
Assigned To: Martin Stransky
Desktop QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-22 05:26 EDT by o.h.weiergraeber
Modified: 2013-09-23 09:12 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-09-23 09:12:56 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
example .xssession-errors output (9.15 KB, text/plain)
2013-09-22 05:26 EDT, o.h.weiergraeber
no flags Details

  None (edit)
Description o.h.weiergraeber 2013-09-22 05:26:07 EDT
Created attachment 801150 [details]
example .xssession-errors output

Description of problem:
After installation of nspluginwrapper together with acroread-plugin and flash-plugin (supplementary channel), starting firefox leads to my .xsession-errors file being flooded with error messages like:
(npviewer.bin:3080): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks"
Gdk-ERROR **: The program 'npviewer.bin' received an X Window System error
*** NSPlugin Wrapper *** ERROR: NPP_HandleEvent() wait for reply: Connection closed
(npviewer.bin:3719): Gdk-WARNING **: XID collision, trouble ahead

For complete output refer to attachment.

Version-Release number of selected component (if applicable):
1.4.4-1.el6_3.x86_64
1.4.4-1.el6_3.i686

How reproducible:
always

Steps to Reproduce:
1. install nspluginwrapper and Adobe plugins from RH channels
2. start firefox
3. observe messages in ~/.xsession-errors

Actual results:
see attachment

Expected results:
no errors

Additional info:
Comment 2 Martin Stransky 2013-09-23 09:12:56 EDT
There's nothing we can do with it.

Note You need to log in before you can comment on or make changes to this bug.