Media source error a front end graph streaming error occurred try again or contact cyber-link customer support - CyberLink POWERDIRECTOR 7 VLICDELUXE for question.
Just got this error and I have no idea where to go with this. I'm currently on Snow Leopard webkitserver86769:903 Error loading /Library/Internet Plug-Ins/SharePointBrowserPlugin.plugin/Contents/MacOS/SharePointBrowserPlugin: dlopen(/Library/Internet Plug-Ins/SharePointBrowserPlugin.plugin/Contents/MacOS/SharePointBrowserPlugin, 262): no suitable image found. Did find: /Library/Internet Plug-Ins/SharePointBrowserPlugin.plugin/Contents/MacOS/SharePointBrowserPlugin: mach-o, but wrong architecture webkitserver86769:903 Error loading /Library/Internet Plug-Ins/QuickTime Plugin.plugin/Contents/MacOS/QuickTime Plugin: dlopen(/Library/Internet Plug-Ins/QuickTime Plugin.plugin/Contents/MacOS/QuickTime Plugin, 265): no suitable image found. Did find: /Library/Internet Plug-Ins/QuickTime Plugin.plugin/Contents/MacOS/QuickTime Plugin: no matching architecture in universal wrapper webkitserver86769:903 Error loading /Library/Internet Plug-Ins/Flash Player.plugin/Contents/MacOS/Flash Player: dlopen(/Library/Internet Plug-Ins/Flash Player.plugin/Contents/MacOS/Flash Player, 262): no suitable image found. Did find: /Library/Internet Plug-Ins/Flash Player.plugin/Contents/MacOS/Flash Player: no matching architecture in universal wrapper I did find this: posted on the QT web forum. So I guess this is not a capybara-webkit issue? Any pointers would be appreciated.
A not-so-real solution for a not-so-real problem: This is not a real problem for capybara-webkit. QT will fail to load all those plugins of different architecture, and this is not affecting by any means capybara. I tried to disable plugins via QWebSettings::PluginsEnabled, but it didn't worked. So, in order to keep rspec's output as clean as possible, I just hide all error messages while loading webkit-server. I guess this is not a really good approach, because that way any other loading errors that it might appear, would be hidden as well. But it will bring us some temporary sanity at least:). Alright so I've dug a little deeper and I found a fix for my issue.
It might break other people's system if they don't know what they're doing but in my case it works great. As with any problem like this one there are a lot of actors and it's hard to figure out who needs to do the appropriate fix. I think they all stem from one fact.
There are plugins residing in your system that are too old for the system you currently use. This can happen if you upgrade your OS and system without doing a cleanup of some key folders. To do this cleanup you need to go in two folders: /Library/Internet Plug-Ins/. Thanks a lot for looking into that and reporting here. I will check it out when I have a moment and write back.
On Oct 25, 2012, at 5:28 PM, Gary Haran wrote: Alright so I've dug a little deeper and I found a fix for my issue. It might break other people's system if they don't know what they're doing but in my case it works great. As with any problem like this one there are a lot of actors and it's hard to figure out who needs to do the appropriate fix.
I think they all stem from one fact. There are plugins residing in your system that are too old for the system you currently use. This can happen if you upgrade your OS and system without doing a cleanup of some key folders. To do this cleanup you need to go in two folders: /Library/Internet Plug-Ins/. The suggested fix does remove the error from the test output, however, it also removes the plugins from your browser.
On Mavericks I get the plugin architecture error for QuickTime (using the brew install qt -head method of installing Qt). When I move the QuickTime Plugin.plugin out of the /Library/Internet Plugin-Ins folder there is no error message in my test output, however, QuickTime videos no longer play in Chrome. A warning to others: be sure to just move the QuickTime Plugin.plugin file, don't delete it. Apple doesn't seem to allow you to easily download the QuickTime plugin for OSX. As far as I know, you have to copy it off another Mac, find it somewhere in the Mavericks install download, or reinstall OSX to get it back.
I just ran across this issue and though I would post here for anyone else. Capybara:: Webkit.configure do config config.blockunknownurls #.
Version: M53 OS: Windows, MAC What steps will reproduce the problem? (1) Open (2) Open a game What is the expected output?
I should be able to play flash videos What do you see instead? Error message 'Could not load plugin' Some affected URLs, bbc.co.uk, Washington Post, Daily Telegraph, AOL/Huffington Post, etc We can try to connect with users on forum to get logs / debug info if required. Few examples 1. Could not watch videos on news sites 2. Unable to play facebook games due to could not load plugin Trends analysis.
Processing Cc: [email protected][email protected] Rechecked this issue on chrome stable version 53.0.2785.143 on Windows 10 and MAC OS 10.11.6. Below are the observations for the same: Flash Version# 23.0.0.166 Launched the below Web Sites: 1) - Played some videos 2) 3) 4) 5) On Corp machines in a Google network, it is observed that the sites when loads, immediately it plays the videos. But when the same web sites are tried on a Non corp machine with a Google guest network, it takes time (approximately 10 Minutes) for each site to play the videos. Also the below website never played (Same worked fine on a corp network). Url: Could this be some thing related to network behavior.
Processing Some more user feedback 1. I can't play any games on my hp laptop because i can't load plugin 2. Same thing and it was working fine until yesterday. Just what is going on? Nothing I did seem to work for me and I'm really getting pissed since there are sites that I need to do my work on that rely on Flash and the plugin not being loaded despite me having everything updated does not help. This issue still impacts people and no workaround seems to work. Is there anything else that we can suggest impacted users?
Processing 99% of my 200+ staff users are on MacOS 10.10.5 network home folders with up to date Chrome 54.0.2840.59 and Flash 23.0.0.185 and we've had to switch to Safari to get Flash sites to play with the NAPPI 23.0.0.185 player, we don't install Adobe's PAPPI plugin we rely on Chrome's built in pepper flash. Flash 23.0.0.162 works until Chrome auto updates it to 23.0.0.185. And it makes no difference if it's Chrome 53 or 54. I've tried deleting/replacing affected users' Pepper Flash in /Library/Application Support/Google/Chrome/ with my PepperFlash folder that is working for me and while it's not generating the invalid code signature on my system it's not working at all for my users and still giving the 'Couldn't load plugin' error. I deleted their flash and then copied my PepperFlash directory via CLI on our server and reset the ownership permissions after the copy too in addition to outright deleting the PepperFlash folder and letting Chrome rebuild it on launch.
Backing up user bookmarks and starting with an all new profile works until Chrome updates Flash from 23.0.0.162 to 23.0.0.185. Here is a log entry from an affected user (I obfuscated server and user name) after the Flash 185 update. This appears when I go to Adobe's about flash page on their site which gives me the 'cannot load plugin' error. 10/18/16 1:17:46.168 PM Google Chrome Helper1272: Error loading /Network/Servers/server.org/users/username/Library/Application Support/Google/Chrome/PepperFlash/23.0.0.185/PepperFlashPlayer.plugin/Contents/MacOS/PepperFlashPlayer: dlopen(/Network/Servers/staff.skaggscatholiccenter.org/users/sharonphelps/Library/Application Support/Google/Chrome/PepperFlash/23.0.0.185/PepperFlashPlayer.plugin/Contents/MacOS/PepperFlashPlayer, 262): no suitable image found. Did find: /Network/Servers/server.org/users/username/Library/Application Support/Google/Chrome/PepperFlash/23.0.0.185/PepperFlashPlayer.plugin/Contents/MacOS/PepperFlashPlayer: code signature invalid for '/Network/Servers/staff.skaggscatholiccenter.org/users/sharonphelps/Library/Application Support/Google/Chrome/PepperFlash/23.0.0.185/PepperFlashPlayer.plugin/Contents/MacOS/PepperFlashPlayer' You can see it's still complaining about 'PepperFlashPlayer: code signature invalid'. Processing Hi. I've also run into this annoying issue.
I'm forced to use Firefox since chrome won't play anything flash based (in some sites says 'can't load plugin' and others like radio players, it just won't load anything). Tried to uninstall, tried renaming pepflashplayer.dll, tried disabling firewall, tried uninstalling flash from windows, tried also the youtube link provided by jainabhi. Sad to say nothing works. Chrome is updated and using 23.0.0.185 player. Hope you can figure out a solution, I prefer chrome over Firefox. Processing If you are having trouble w/ Flash Player, here are the main recommendations: 1.) Clear the Adobe Flash Player component, from your user data directory, and trigger a component update (in chrome://components).
vuppala18 did a nice job enumerating the directory locations, so I'm just repeating Windows 7, 8.1, and 10: C: Users AppData Local Google Chrome User Data Default Mac OS X El Capitan: Users//Library/Application Support/Google/Chrome/Default Linux: /home//.config/google-chrome/default 2.) If that doesn't work, or you can't find the directory Install the PPAPI Flash Player from Adobe -. Processing @tsrwebgl - What are the contents, in the versioned Flash Player directories (under those user data dirs)?
For example here's what I see: C: Users laforge AppData Local Google Chrome User Data PepperFlash 23.0.0.195dir 02:35 PM 66 manifest.fingerprint 11:16 AM 2,220 manifest.json 11:16 AM 31,064,768 pepflashplayer.dll 3 File(s) 31,067,054 bytes 2 Dir(s) 589,074,391,040 bytes free C: Users laforge AppData Local Google Chrome User Data PepperFlash 23.0.0.195 Are you (or your users) running any specific AV applications? Processing My company is also having this problem!! Really making IT department look bad for pushing users to Chrome due to better security and built in flash updates! Why are all the support people in the forums and you guys here asking users to run around in circles trying all kind of crazy stuff!?! Uninstall Chrome, delete all of your settings then try installing it yourself! There is something really wrong with the Pepper flash plugin and it should not take a Mensa asking people to update drivers and see it works in a closet with the lights off, did you try with the lights on? Look at the support.
It's really sad for such a large and easily reproducible issue. You want logs, remote connection what? Heck give me your email and I'll provide you with my Logmein Rescue user/pass so you can see my machines. Processing I have a computer with this problem. Completely uninstalled Chrome and Chrome user data. After re-installing Chrome from scratch there is no Adobe Flash component present.
This directory exists but is completely empty: C: Users username AppData Local Google Chrome User Data PepperFlash In chrome://components/ Adobe Flash Player - Version: 0.0.0.0 Manually triggering a 'Check for update' results in this: 1: Status - component downloading 2: Update ready 3: Status - Component not updated The component simply won't install no matter what. Even after completely removing any trace of Chrome from the computer's filesystem and registry and re-installing Chrome.
Processing @Comment 35 Updated Flash at Run As Administrator, Check for update in chrome://components. (other things (previous suggestions here) didn't work anymore, they worked in past, as I already had Flash issue with Chrome and learned how to deal with it, by deleting PepperFlash). After this update as Administrator, at site now it's written 'Adobe Flash Player is out of date'.
It's not possible to update it as a User (after clicking button 'Check for update' in chrome://components: Adobe Flash Player - Version: 23.0.0.205 Status - Component not updated) Before it was written 'Couldn't load plugin'. I'm on Win8.1. Processing Status: Available (was: Untriaged) Many users encountering 'Could not load plugin' are using a user-data-directory on a network drive.
The security concerns with network file systems are great enough that the current thinking of the team is that users (on any OS) using a user-data-dir in a network location will have to install Flash on the local disk by using one of the Adobe-published installers. Unfortunately, this is broken for many users in M54, due to a detail about how Chrome breaks ties between multiple sources of Flash binaries. There is a CL landed in M55 that is expected to fix any cases where an up-to-date Flash has been installed on the system (i.e.
By an Adobe installer, not just by Chrome). There is mixed support for merging that change into M54 (stable). Processing Why was the pepperflash location changed out of the 'program files' install folder and into each user's profile folder?
We had Chrome happily working in a terminal services environment for 2000 users, and as of Chrome 54, Flash is completely broken. We store profiles on network shares, and Flash has long been known to choke on network shares. This change is a breaking change for anyone who uses Chrome in an enterprise terminal services environment. If you're trying to increase user adoption of Internet Explorer or Firefix, you're on the right track. Processing FIX: To resolve this I did the following: 1. Exit Chrome by clicking the three dots in the upper right, and clicking exit 2.
Go to%localappdata% Google Chrome User Data, in Windows File Explorer 3. Rename folder 'PepperFlash' to 'PepperFlash.old' 4. Shift+Right Click Chrome icon, and select 'Run as Administrator' 5. In Chrome's address bar go to chrome://components 6. Find 'Adobe Flash' It should say you are on version 0.0.0.0. Click 'Check for Update' and wait for it to update.
In Chrome's address bar go to chrome://restart 9. Test it somewhere you previously had issues This worked for me on 3 different machines, but, as always, YMMV.
Processing I tried a few variations of fixes found on diff sites for this. I didn't try the run as admin fixes(like comment 57 above), bc I fixed a diff way. Its more complicated, but worked for me so wanted to share. I uninstalled chrome, deleted the pepperflash folder in appdata, reinstalled chrome. The following steps from above did not work for me, since the peperflash folder remained empty no matter what I did: 5.
In Chrome's address bar go to chrome://components 6. Find 'Adobe Flash' It should say you are on version 0.0.0.0. Click 'Check for Update' and wait for it to update. So instead, I went to and it loaded the newest flash automatically! Processing We have been having this issue in our 22k user enterprise environment.
User profiles are stored locally, not on the network. We are hoping to avoid using the Adobe.msi files as that becomes an additional piece of software that we must patch on a regular basis. All of the fixes offered above have not worked in our environment.
However uninstalling Symantec Endpoint Protection resolved the issue in 100% of cases. Reinstalling SEP re-introduced the issue. We have opened a case with Symantec. Processing Symantec has confirmed that this is a known issue. Below is their response to our case.
After reviewing this case and the available data (primarily the provided WPP logs) I have found that this is a known-issue with the SEP 12.1 and SEP 14 products. SEP is attempting to obtain a hash of the Adobe Flash Player file 'pepflashplayer.dll'; however, during the hash operation, Chrome is attempting to move the file from a temporary folder (where SEP is performing the hash) to Chrome's plugin folder; since SEP has a lock on the file, Chrome's move operation fails and the plugin update process aborts. Symantec has identified a fix for this issue and is planning on including a resolution in the next release of SEP 12.1 and SEP 14, both due out early next year.
It is possible to work around this issue by disabling deferred scanning for AutoProtect; however, this is not generally recommended in production unless absolutely needed, as it disables scan throttling based on I/O activity. For more information on disabling deferred scanning, please see the following KB document: How to disable deferred scanning in Auto-Protect for Symantec Endpoint Protection It is also possible to work around the issue by temporarily disabling SEP; however, this is a potential security issue, as you will be temporarily disabling the product from being able to scan files. Processing I was able to somewhat manually update this by taking a copy of the PepperFlash folder from my home system running Chrome 55 in the users profile and copying it to a work system with the following steps.
YMMV, but hopefully this helps someone. Close Chrome. Go to c: users AppData LocalGoogle Chrome User Data and find and delete the PepperFlash folder.
Copy the PepperFlash folder from a working updated system in the same source folder and place it into the User Data director where you just deleted the old one. Start Chrome 5. In the address bar, type chrome://components 6. Find the Adobe Flash Player, it will say Version: 0.0.0.0, Status New.
Hit the Check for update button. The status will change a couple of times and end up with Status – Component updated and the version will be at 24.0.0.186.
Processing Here is the latest update from SEP: 'I'm still monitoring our internal defect tracking system for updates. After discussion with our engineering release team, it has been determined that Symantec Endpoint Protection 12.1 will not contain a fix for this issue. The fix will only be available in SEP 14.0 MP1, which will be released later this month (February, 2017).
It will be a full build and will follow the normal migration process for SEP (unchanged on the client side in 14.0 compared to 12.1). The fix cannot be delivered via LiveUpdate. I'm continuing to watch for updates as they become available from development and will let you know once SEP 14.0 MP1 is available.'