Description of problem: Pipelight is a special browser plugin which allows one to use windows only plugins inside Linux browsers. We are currently focusing on Silverlight and its features like watching DRM protected videos. The project needs a patched version of Wine to execute the Silverlight DLL. https://launchpad.net/pipelight Version-Release number of selected component (if applicable): Not released yet! How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Summary: Pipelight Browser Plugin for mageia => Pipelight Browser Plugin for mageia for using Silverlight in Linux browsers
This is the best solution to get signing services like Netflix on CPU only with Linux ...
CC: (none) => frateraec
And Moonlight isn't officially developed anymore so there is no other working option. I'm trying to get a broadcast on viaplay.se working, but mono isn't doing the trick.
CC: (none) => kristoffer.grundstrom1983
Created attachment 4548 [details] Here's the spec I have started to edit from opensuse srpm
(In reply to Kristoffer Grundström from comment #3) > Created attachment 4548 [details] > Here's the spec I have started to edit from opensuse srpm It's not even remotely like a Mageia RPM spec yet - probably better not update it fully before uploading it here, especially as we'll need to update to wine 1.7.7 first and we're in version freeze right now in cauldron for mga4, so this would target Mageia 5 at the earliest.
CC: (none) => mageia
Version: 3 => CauldronTarget Milestone: --- => Mageia 5
Hi, I'm one of the developers of Pipelight and have packaged everything required to run Pipelight on Mageia 4. This includes: * wine-compholio (the patched version of wine, which can be coinstalled to a regular wine version) * msttcore-fonts-installer (as Silverlight requires the M$ fonts to be installed) * and of course pipelight itself To find out more about Pipelight (in general) you can visit for example: * https://launchpad.net/pipelight * http://fds-team.de/cms/pipelight-installation.html * http://fds-team.de/cms/articles/2013-08/pipelight-using-silverlight-in-linux-browsers.html IMPORTANT: ---------- The packages are still beta, there were just a few testers so far. If something doesn't work, please ask in #pipelight on Freenode (webchat: http://webchat.freenode.net/?channels=%23pipelight ) for help and we'll help you to fix the issue or push an updated package for more critical errors. If you have some other ideas for improvement, feel free to share them! PACKAGES: --------- We've set up a separate build server machine to compile the builds for Mageia 4 and some other distros. The published stable packages are located here: http://repos.fds-team.de/stable/mageia/ So far there are no daily packages for Mageia yet, but we've planned this step for the future (at least for Pipelight itself, not sure if it makes sense for Wine ;-) ). INSTRUCTIONS (ALL AS ROOT): --------------------------- # IMPORTANT: You always need the 32-bit repo!!! urpmi.addmedia "Pipelight 32-bit" http://repos.fds-team.de/stable/mageia/4/i586/ # [Only if you're using a 64-bit version of Mageia] urpmi.addmedia "Pipelight 64-bit" http://repos.fds-team.de/stable/mageia/4/x86_64/ # Import the public key to verify the package signatures wget http://repos.fds-team.de/Release.key rpm --import Release.key # Install Pipelight + all dependencies # There is no need to uninstall your regular wine version! wine-compholio is installed to /opt/wine-compholio (as on Debian/Ubuntu) # You can choose between "wine-compholio" (32-bit only) and "wine-compholio64" (includes 32+64bit support) urpmi pipelight # Recommended if you want to use Unity3D/Shockwave where the plugin database is often outdated pipelight-plugin --update # Afterwards enable the plugins you like, in this example Silverlight and Unity3D pipelight-plugin --enable silverlight --enable unity3d # IMPORTANT: Most plugins require a user agent switcher, otherwise they are not loaded at all or don't work as expected. # Take a look here for installation instructions: https://answers.launchpad.net/pipelight/+faq/2351 TROUBLESHOOTING: ---------------- * Don't hesitate to ask in #pipelight on IRC freenode!! ;-) * To verify that your user agent switcher works and for some other types of errors you can use the following diagnostic page: http://fds-team.de/pipelight/ * The easiest way to invalidate the Firefox plugin cache (to force loading the plugin again) is to run: sudo pipelight-plugin --create-mozilla-plugins * For more difficult problems it is often useful to take a look at the terminal output of your browser. Close all browser windows, then just open the browser from a terminal (and optionally capture the stdout & stderr to a file). For example: firefox &> pipelight.log This log often contains useful information for troubleshooting problems. Regards, Sebastian
CC: (none) => sebastian
CC: (none) => remi
It's good of you to do this Sebastian, it would be good to include this in cauldron for testing and possibly backport to mga4 when stable. Colin/Rémi any ideas who would be likely to run with this?
CC: (none) => eeeemail
I agree that it would be definitely nice to have this package included officially, but based on my previous experience with other big distros I think this won't happen so soon. Pipelight itself is relatively easy to package, and I don't see any critical problems there. For most other distros the main problem is that they don't want to package/maintain multiple versions of Wine. Please note that we really need the patched version, not even the newest version is new enough! Getting patches upstream to Wine is a really difficult job - often very delayed responses or no answer at all, although we have the help of several experienced Wine developers in our team. Some of the patches are really fundamental changes (not just bug fixes!), but these are necessary especially for Silverlight DRM. If the Mageia packaging rules allow to provide a separate "Wine-compholio" package the chances would be much better ;-) Addition to my previous post: The spec files are also available of course. See: http://repos.fds-team.de/stable/mageia/CHANGELOG.html Please note that while repackaging Wine I changed the structure a bit, since the original Mageia Wine packaging has a critical bug: The wine32 package doesn't depend on the 32bit libs, which means that with wine64 + wine32 you end up with a non-functional Wine version.
CC: (none) => doktor5000
I found one issue it's ms core fonts,firefox and other browser fonts goes really ugly because of those old buggy ms fonts.
CC: (none) => ozkyster
Hi Otto, unfortunately I don't have a direct solution for this issue. These fonts are required for Silverlight, see the following link: https://answers.launchpad.net/pipelight/+faq/2441 Without them you'll just get an empty rectangle where the plugin should be. We'll think about if there is some alternative way to get around this restriction or maybe some font replacements, but so far the easiest way is just to install them. Sebastian
Yes i have one way to do it winetricks and install them to wineprefix/pipelight wine folder.It's very easy to use winetricks,i do it all the time when i install windows programs what needs those core fonts. Here is example how do it from commandline:WINEPREFIX=~/.PlayOnLinux/wineprefix/pipelight sh winetricks corefonts
Hi, thanks for your feedback. Winetricks itself also isn't a perfect solution, because it has some additional dependencies that are not really required by Pipelight itself. Moreover its huge, and we would just use one function... But we'll think about some alternative ways, and discuss this internally, so that we can hopefully drop this dependency in the future (maybe just copying the functionality of this specific winetricks command into Pipelight?). In the meantime you could use the following Pipelight packages, where I've just commented this dependency: http://cache.fds-team.de/testing/mageia4-i686/20140225-2237/ http://cache.fds-team.de/testing/mageia4-x86_64/20140225-2236/ After the wine prefix was created you can install the core fonts like: WINEPREFIX=~/.wine-pipelight WINE=/opt/wine-compholio/bin/wine sh winetricks Sebastian
It's working and no any font issues anymore.
Yes you are right that winetricks is not best solution to those msfonts so i have changed back to normal pipelight.
The mcc has a weird behaviour. If I run it from a console, I've got this : " LOG **: NP_Initialize succeeded at /usr/lib/libDrakX/mygtk2.pm line 589. [PIPELIGHT:LIN:unknown] attached to process. [PIPELIGHT:LIN:unknown] checking environment variable PIPELIGHT_SILVERLIGHT5_1_CONFIG. [PIPELIGHT:LIN:unknown] searching for config file pipelight-silverlight5.1. [PIPELIGHT:LIN:unknown] trying to load config file from '/root/.config/pipelight-silverlight5.1'. " wine seem to be launched , and some options are missing, ie: in the system services configuration : the description button of the items is missing... how to avoid this side effect ? ---- How to reproduce : 1. Install pipelight packages from the repos of fds-team.de 2. activate silverlight plugin 3. launch mcc from the console
CC: (none) => jeanyves.le-goff
PS: this was with mageia4 x86_64 up to date.
Hi, this is definitely something where you should open a bug-report for MCC. As you can see in the debug output it seems to load arbitrary browser plugins with root rights (/root/.config/...) in the background, which is usually not a good idea for security reasons. I assume that they use some kind of browser widget for displaying information, but usually developers should pay attention and disable loading plugins, unless they're really required. Please note that this also affects all other system-wide browser plugins, not only Pipelight: Flash, Java, Moonlight, ... - but most of them just don't write any output to stderr. In theory all applications should work as expected, even if Pipelight is loaded into the process. Can you probably provide a more detailed log? To workaround this problem I would recommend to enable Pipelight for each user individually instead of system-wide: sudo pipelight-plugin --disable-all pipelight-plugin --enable silverlight5.1 This should solve the issue. Regards, Sebastian
This is amazing!! Thank You! I just used alien to convert wine-browser-installer to rpm with out scripts option and install it on mageia 4.. I just had to modify the wine-browser script a little bit and I was able to use netflix flawlessly.. ;-) Thank you again Sebastian Lackner. ;-)
Well with Mageia 5 on the horizon and pipelight has not been put in the repos, guess Mageia 5 will be out of the game until Mageia 5 has a version.
CC: (none) => dancingmadrb3
> Well with Mageia 5 on the horizon and pipelight has not been put in the repos, guess Mageia 5 will be out of the game until Mageia 5 has a version. Well obviously no packager is interested in Pipelight currently, and since upstream does a great job at providing a Mageia repo and instructions on how to use Pipelight, the matter is not particularly urgent. If you really want to see Pipelight in the official repos, you are free to join the packaging team and make it happen.
Target Milestone: Mageia 5 => ---
(In reply to Rémi Verschelde from comment #19) > > Well with Mageia 5 on the horizon and pipelight has not been put in the repos, guess Mageia 5 will be out of the game until Mageia 5 has a version. > > Well obviously no packager is interested in Pipelight currently, and since > upstream does a great job at providing a Mageia repo and instructions on how > to use Pipelight, the matter is not particularly urgent. > > If you really want to see Pipelight in the official repos, you are free to > join the packaging team and make it happen. Yes but I dont compile any software, I dont know how to make rpms. No sorry Mageia 5 is a disappointment now, gonna use Ubuntu as at least it has ppa's
So, Rémi is telling you you can install it from the repository that pipelight upstream has made (which is the equivalent to a PPA) and you're telling us you are going to Ubuntu because they have PPAs. I don't see any sense in that :) I can only suppose you haven't understood what Rémi said.
(In reply to Samuel VERSCHELDE from comment #21) > So, Rémi is telling you you can install it from the repository that > pipelight upstream has made (which is the equivalent to a PPA) and you're > telling us you are going to Ubuntu because they have PPAs. > > I don't see any sense in that :) > > I can only suppose you haven't understood what Rémi said. Well it would help to tell people what upstream repo are you talking about, is it compiled or source code?
3 click starting from the first url in this bug, and I get http://pipelight.net/cms/install/installation-mageia.html which speak about urpmi.addmedia So yes rpm are available in a third repo, like ppa, as Samual said
(In reply to Manuel Hiebel from comment #23) > 3 click starting from the first url in this bug, and I get > http://pipelight.net/cms/install/installation-mageia.html which speak about > urpmi.addmedia > So yes rpm are available in a third repo, like ppa, as Samual said no those packages don't work I've already tried that they are incompatible with Mageia 5 release candidate it would have to be rebuilt
Well, I guess they'll do it if you ask them (or if they see our comments here since they're following the bug report)
I just wanted to inform you guys that we're now also providing Wine Staging and Pipelight packages for Mageia 5. * Instructions for installing Pipelight are available on the following website (wasn't updated yet, but just replacing mageia/4 -> mageia/5 should be sufficient): http://pipelight.net/cms/install/installation-mageia.html * For those who are only interested in Wine Staging, a special Wine build including various improvements compared to vanilla wine, please take a look here: https://github.com/wine-compholio/wine-staging/wiki/Installation#-mageia-45 If there are any problems with the packages, please report it to us (for example in #pipelight or #wine-staging on freenode or directly to me via mail). Also, if there is any Mageia dev actually interested in officially integrating Wine Staging and/or Pipelight into official repos, please contact me. Although our build scripts are fully automated, we would of course prefer if distros provide their own packages for user convenience.
(In reply to Sebastian Lackner from comment #26) > I just wanted to inform you guys that we're now also providing Wine Staging > and Pipelight packages for Mageia 5. Seems you read the minds and queries of some early adopters :) Anyway, thanks for sharing! For the installation instructions, no real need to distinguish, you can use placeholder variables which will automatically expand depending if they are run on Mageia 4 or 5 (or any other release) - hence the following is sufficient for a x86_64 system, no matter if Mageia 4 or 5: sudo rpm --import http://repos.fds-team.de/Release.key sudo urpmi.addmedia "Wine Staging 32-bit" 'http://cdn.fds-team.de/stable/mageia/$RELEASE/i586/' sudo urpmi.addmedia "Wine Staging 64-bit" 'http://cdn.fds-team.de/stable/mageia/$RELEASE/x86_64/'
(In reply to Florian Hubold from comment #27) > (In reply to Sebastian Lackner from comment #26) > sudo rpm --import http://repos.fds-team.de/Release.key > sudo urpmi.addmedia "Wine Staging 32-bit" > 'http://cdn.fds-team.de/stable/mageia/$RELEASE/i586/' > sudo urpmi.addmedia "Wine Staging 64-bit" > 'http://cdn.fds-team.de/stable/mageia/$RELEASE/x86_64/' Although currently this doesn't work yet, so better keep what you have on the wiki page, as it's obviously working.
FYI on Mageia 5 it's not possible to install pipelight on a x86_64 system: [root@localhost ~]# urpmi lib64netapi-devel Pour satisfaire les dépendances, les paquetages suivants vont être installés : Paquetage Version Révision Arch (média « Core Release (mga1) ») lib64ldap2.4_2-devel 2.4.40 3.mga5 x86_64 lib64netapi-devel 3.6.25 1.mga5 x86_64 un espace additionnel de 1.7Mo sera utilisé. 315Ko de paquets seront récupérés. Procéder à l'installation des 2 paquetages ? (O/n) http://mirrors.kernel.org/mageia/distrib/5/x86_64/media/core/release/lib64ldap2.4_2-devel-2.4.40-3.mga5.x86_64.rpm http://mirrors.kernel.org/mageia/distrib/5/x86_64/media/core/release/lib64netapi-devel-3.6.25-1.mga5.x86_64.rpm installation de lib64netapi-devel-3.6.25-1.mga5.x86_64.rpm lib64ldap2.4_2-devel-2.4.40-3.mga5.x86_64.rpm depuis /var/cache/urpmi/rpms Préparation... ####################################################################################################################### L'installation a échoué : le fichier /usr/include/openldap/include/ldap_config.h de l'installation de lib64ldap2.4_2-devel-2.4.40-3.mga5.x86_64 entre en conflit avec le fichier du paquet libldap2.4_2-devel-2.4.40-3.mga5.i586 le fichier /usr/include/openldap/include/portable.h de l'installation de lib64ldap2.4_2-devel-2.4.40-3.mga5.x86_64 entre en conflit avec le fichier du paquet libldap2.4_2-devel-2.4.40-3.mga5.i586 I had to force install one of the 2 versions (i586 or x86_64) as there is a conflict on the ldap dependency between them.
CC: (none) => bruno
That is normal for devel packages IINM Bruno
(In reply to Bruno Cornec from comment #29) > FYI on Mageia 5 it's not possible to install pipelight on a x86_64 system: > lib64ldap2.4_2-devel 2.4.40 3.mga5 x86_64 > lib64netapi-devel 3.6.25 1.mga5 x86_64 How does a manual installation of netapi-devel relate to pipelight? pipelight installed fine here on mga5 x86_64, only pulling wine-staging64 and wine-common, apart from pipelight itself. Neither netapi nor ldap are dependencies of pipelight. Wrong bugreport?
Interesting. I made again an install on another machine and had indeed no dependecy issue. I wonder what happened on the first one (laptop used for work) except that pipelight was previously installed with mga4 so maybe a side effect of the upgrade to mga5 (as the lib64netapi-devel was then a dep of pipelight x86_64 for that machine) ?
Assigning this package request to all packagers collectively. On a voluntary basis, one of them might want to integrate it to the distribution and maintain it for bug and security fixes. You might also want to join the packager team to maintain this piece of software: see https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
Assignee: bugsquad => pkg-bugs
Sorry, bugs@ml and pkg-bugs@ml members, for the avalanche. 72 bugs with the "New RPM package request" component, had a severity of "normal" or more, which can lead to losing precious time when searching Bugzilla for bugs that urgently need to get fixed Now mass-changing that to "enhancement", as it should be for package requests. https://wiki.mageia.org/en/How_to_report_a_bug_properly#How_to_file_a_package_request @ the reporter of this package request Please check in http://madb.mageia.org/ whether this software did already get packaged, and close this bug report if it did. Please do also close it if you find a package with the same purpose, that meets your needs.
Severity: normal => enhancement
Sadly Michael Müller (pipelight developer) drop the support. in Mexico we need to use silverlight for our taxes portal, pipelight did help us with that, mageia uses esr version of firefox that still support the deprecated npapi plugins, but we could not continue using silverlight because there is no more pipelight, make more difficult the "spread the word" task. The user that already install pipelight will have to still in mageia 5, and no further user that need to use the taxes portal could arrive.
CC: (none) => j.alberto.vc
(In reply to katnatek from comment #35) > Sadly Michael Müller (pipelight developer) drop the support. > in Mexico we need to use silverlight for our taxes portal, pipelight did > help us with that, mageia uses esr version of firefox that still support the > deprecated npapi plugins, but we could not continue using silverlight > because there is no more pipelight, make more difficult the "spread the > word" task. > > The user that already install pipelight will have to still in mageia 5, and > no further user that need to use the taxes portal could arrive. Yes, Müller uses a non-free browser with non-free DRM code and expects everyone else do the same. Still, the Git repository is still available. I'd be perfectly willing to write the RPM spec files to get Pipelight into Mageia if I could. The problem is that Pipelight requires wine-staging, so I'd either have get Mageia to switch from canonical WINE to WINE Staging, or I'd have to become the maintainer of wine-staging too (and I can't get the latest to compile, so I still use Pipelight with WINE Staging 1.7.23, which works fine for me, but would be a step back from WINE 2+).
CC: (none) => zooplah
(In reply to Keith Bowes from comment #36) I don't know if is necessary a wine-staging, all depends of how much of the pre wine 2 patches of wine staging are in the 2+ version of wine As i understand the scripts of pipelight are the most tediously part to keep update, they need to update each time a new version of each plugin is available. May be pipleight could work with the wine version shipped by Mageia but patching pipleight to use it and still creating an independent wine profile in the home like already does
(In reply to Keith Bowes from comment #36) > Yes, Müller uses a non-free browser with non-free DRM code and expects > everyone else do the same. Still, the Git repository is still available. With Pipelight you are also using non-free DRM code - even worse, in contrast to most browsers it is not even sandboxed and Wine does not provide any additional security. For most websites, there are indeed better alternatives available in the meantime. I can understand that it is a bit disappointing when people still need it, but please keep in mind that open-source projects like Pipelight are entirely driven by volunteers in their spare time. Like any other open-source project, everyone is welcome to fork / continue it, if they still consider it useful. > I'd be perfectly willing to write the RPM spec files to get Pipelight into > Mageia if I could. The problem is that Pipelight requires wine-staging, so > I'd either have get Mageia to switch from canonical WINE to WINE Staging, or > I'd have to become the maintainer of wine-staging too (and I can't get the > latest to compile, so I still use Pipelight with WINE Staging 1.7.23, which > works fine for me, but would be a step back from WINE 2+). Wine Staging is only required for certain plugins and features (for example Silverlight DRM). The general functionality should work fine with any version of Wine. Michael is still actively working on Wine/Wine-Staging and planning to bring back Mageia 6+ builds soon (test builds already available): https://bugs.winehq.org/show_bug.cgi?id=43436#c3. Please note that with recent versions of Wine/Wine-Staging, the default Windows version is set to Win7. Silverlight DRM only works when the version is changed back to XP before the installation of the plugin.
(In reply to Sebastian Lackner from comment #38) > (In reply to Keith Bowes from comment #36) > > Yes, Müller uses a non-free browser with non-free DRM code and expects > > everyone else do the same. Still, the Git repository is still available. > > With Pipelight you are also using non-free DRM code Yeah, but at least I can use my browser of choice with it. I'd rather not watch Netflix again than have to use Firefox (or even worse, Chrome).
I think this pluging is no longer needed since Linux already has widevine on both firefox and google chrome to watch DRM video sites like netflix.. Don't you think?.. Should this be mark as resolved?.
No longer needed since there's other addons that will do the job.
Resolution: (none) => WONTFIXStatus: NEW => RESOLVED