Yes, there was an update last night. Have you restarted the players? What version of Chromium are you using?
Yes we tried restarting the players and rebooting the machines.
We are using version 37.0.2062.94 on Ubuntu 14.10 (290621) with LXDE for the majority of our displays, I did a apt-get update/upgrade on one display to see if that resolved it but no luck.
Is there a release note for the update anywhere so I can check if anything we have configured might be conflicting?
I am having the same issue with all of my players that are running on Ubuntu 13.04 or 13.10 with the Chrome player version 1.24.36
They are all displaying a white screen and are not connecting to Rise Vision.
1. Make sure the player is not running (press CTRL-W to exit)
2. Launch the chrome browser (not the Rise Player).
3. Enter chrome://flags in the address bar.
4. Search for, and make sure "Enable debugging for packed apps" is enabled.
5. Close chrome.
6. Launch Rise Player.
7. **IMMEDIATELY** right click and select "inspect element".
8. Click on the console "tab".
Unfortunately, this isn't going to be a very satisfactory answer. We only officially support Rise Player on the following platforms: WIndows 8.1, Ubuntu Linux 14.04, OSX Yosemite, and ChromeOS in managed mode. The port/availability of the Player to the Pi platform arose out of a series of community posts and effort and was never an official product. The recent update of our Player inadvertently broke compatibility with the Pi because it runs an much older version of Chromium that does not support a specific API that our player calls. Our devs are in the process of looking at a workaround and will be incorporating a fix to resolve the issue, however, it is quite possible that a situation like this will arise again in the future.
That feature was introduced in release 44 of Chrome. Because Chromium is the open source browser that Chrome is based on, I imagine that the release numbers should be the same.
Is there a way we can install the previous version of the Player, possibly through the "Load unpacked extension" option in the extension settings in Chromium? And avoid future updates.
Definitely update this thread if you find anything. I think quite a few people will appreciate it.
Unfortunately, I don't think there's a way to install an earlier version of a Chrome App, short of taking a snapshot of the cache/config folders before an update occurs and rolling it back that way. Further, unless there's an obscure setting in chrome://flags or an ini file, I don't know of a way to prevent updates outside of managed mode in ChromeOS.
Our devs have made changes to the player that should resolve the incompatibility with the Chromium version on the Raspberry Pi 2 and they should be going out tomorrow morning.
I'll pass the suggestion up the ladder, but because this is an unsupported platform I can't make any promises about implementation.
Can you update the topic when the release goes out? I've had 2 of my PI2's restart today with white screens and I'm afraid of what will happen when the 3rd restarts!
Am I right to assume original PI's are unaffected by this as they all seem to be up ok?
Can I also add that while unsupported breaking the PI solution will put off the many users you have who have implemented your great platform.
We are in the same boat. All our screens are offline with white screens after the update.
I am following along here to see if anybody has a solutions.
Same here work in a small Charity and the PI is the only cost effective solution for us.
Updated: 28 July 2015
I've forced an update of the app (instructions in link below) and the Pi is working perfectly again. The apps will automatically update but it can take a few hours from what I can tell.
Thanks Matthew to you and your team getting this release out so quickly.
I would love to see official support for Pis again, there is obviously demand for them. Like others have said they are one of the most cost effective ways to have digital signage, especially if you have a lot of diplays (we have close to 100 of them!)
It seems some of the screens have come back online on their own, yet others remain offline.
The solution described in the link seems to work but now begins the long process of traveling to all the screens around the country to fix those that are still down.
Hopefully Rise will soon offer support for Pi's again as it seems there is demand for this.
Hmm no Idea I think we will give up with the RPI solution.
I have now the latest extension installed but now it starts up and crashes immediately.
When I try to get into the console it crashes already so I can't see what is happening there.
Is there a possibility to see the log files from a crash somewhere on the disk?
So my issue wasn't involving a Raspberry Pi...so Idk is that this will help anyone, as it sounds like the issue's been somewhat fixed.