chromium 34 not see NPAPI pipelight plugin

Bug #1307989 reported by Александр
298
This bug affects 58 people
Affects Status Importance Assigned to Milestone
Pipelight
Expired
Undecided
Unassigned
chromium-browser (Ubuntu)
Invalid
High
Unassigned
pipelight (Ubuntu)
Invalid
High
Unassigned

Bug Description

Chromium is not see pipelight ( silverlight in windows) and adobe flash plugin after update from 33 to 34 version.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: chromium-browser 34.0.1847.116-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Apr 15 13:29:14 2014
Desktop-Session:
 DESKTOP_SESSION = gnome
 XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg
 XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = /usr/lib32
InstallationDate: Installed on 2014-04-13 (1 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Daily amd64 (20140413)
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
modified.conffile..etc.default.chromium.browser: [deleted]

Revision history for this message
Александр (sanek7-7) wrote :
description: updated
summary: - chromium 34 not see pipelight plugin
+ chromium 34 not see pipelight and adobe flash plugins
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: chromium 34 not see pipelight and adobe flash plugins

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Revision history for this message
Chad Miller (cmiller) wrote : Re: chromium 34 not see pipelight plugin

Pipelight uses NPAPI, which is being removed in upstream Chrome and Chromium. See this question, which was far too optimistic about the timeline. https://answers.launchpad.net/pipelight/+question/241737

I think the status of this is WontFix for Chromium.

summary: - chromium 34 not see pipelight and adobe flash plugins
+ chromium 34 not see pipelight plugin
summary: - chromium 34 not see pipelight plugin
+ chromium 34 not see NPAPI pipelight plugin
Changed in pipelight:
status: New → Triaged
Revision history for this message
Michael Müller (mqchael) wrote :

Hi,

I wrote two small patches to get Pipelight working again with Chromium. The first patch enables loading of NPAPI plugins when using Aura and second one adds some minimal code to make Chromium think that drawing still works. The second patch does not include the necessary Xembed code which would be necessary to actually show the window inside the browser, but will pass an invalid window handle (0) to the plugin. Pipelight versions >= 0.2.6 will automatically detect the invalid handle and disable embedding so that the plugin will be shown in an extra window. It is not perfect, but should be usable for most plugins like Silverlight.

The patches were written against Chromium 35, but I assume that they should also apply for Chromium 34. If there is interest in using the patches and they do not apply, I can try to fix this problem.

Michael

Revision history for this message
Michael Müller (mqchael) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "0001-Enable-loading-of-NPAPI-plugins-again.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pipelight (Ubuntu):
status: New → Confirmed
tags: added: aura
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

It renders essential functionality of the package (or a dependent one) broken.

Changed in chromium-browser (Ubuntu):
importance: Undecided → High
Changed in pipelight (Ubuntu):
importance: Undecided → High
Revision history for this message
Eric Nemchik (eric-nemchik) wrote :

chrome 35 also breaks support for pipelight (and in general npapi)
what are the chances of making a ppapi plugin to serve the same purpose?

Revision history for this message
Michael Müller (mqchael) wrote :

Hi Eric,

you can find some information about this in our slides from our Talk at the LinuxTag 2014. Take a look at Slide 29 and the following ones: http://www.linuxtag.org/2014/fileadmin/docs/slides/Michael_Mueller___Sebastian_Lackner___Erich_Hoover_-_Pipelight__Windows_Plugins_in_Linux_Browsers.e1342.pdf

There was also some live demo of a PPAPI version during our talk, but as mentioned in the slides, a patched browser is a better solution.

Michael

Revision history for this message
Chris Guiver (guiverc) wrote :

NPAPI is deprecated (see https://www.chromium.org/developers/npapi-deprecation)

As such I'm changing status to invalid. If you believe I'm in error, please leave a comment explaining why and the status can be returned to "Confirmed" though the feature was intentionally starting to be blocked upstream starting in chromium 32.

Changed in chromium-browser (Ubuntu):
status: Confirmed → Invalid
Changed in pipelight (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for reporting this bug to Ubuntu.

Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.

Changed in pipelight:
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Pipelight because there has been no activity for 60 days.]

Changed in pipelight:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.