Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

10.11.3 not supported. #202

Closed
TheWojtek opened this issue Jan 24, 2016 · 14 comments
Closed

10.11.3 not supported. #202

TheWojtek opened this issue Jan 24, 2016 · 14 comments

Comments

@TheWojtek
Copy link

The screensaver reports it's not compatible with 10.11.3 update.

@alistairmcmillan
Copy link
Collaborator

Working for me on 10.11.3 here. Could you try again please?

@Royedc4
Copy link

Royedc4 commented Jan 28, 2016

What version are you using alistairmcmillan?
I'm using a thunderbolt display as only screen. i've:

  1. Downloaded all videos and put them in /Library/Caches/Aerial/
  2. installed 1.2 latest beta = getting just black screen.
  3. installed 1.1 latest release = getting just black screen also...

@alistairmcmillan
Copy link
Collaborator

/Library/Caches/Aerial is the wrong location. The cache location is that folder but within your own account, for example /Users/royedc4/Library/Caches/Aerial.

Try putting them in that folder and installing 1.2b5.

@Royedc4
Copy link

Royedc4 commented Jan 28, 2016

Working now(in both versions actually), thanks @alistairmcmillan

BTW i see some outgoing connection to: akamai.net, can i block it?
It will not try to download the videos anymore right? Because i notice some delay at the beginning of the screensaver.

@alistairmcmillan
Copy link
Collaborator

Apple could update the JSON file to include new videos. If they do, John designed the screensaver to download the new videos.

Personally I'd leave that outgoing connection unblocked.

@TheWojtek
Copy link
Author

Unfortunately - still no: (
screen shot 2016-01-30 at 1 20 10 pm

@alistairmcmillan
Copy link
Collaborator

Have you tried the latest release?

https://github.com/JohnCoates/Aerial/releases/tag/v1.2beta5

@TheWojtek
Copy link
Author

Yes, I am using this. However, I've found a solution:

  • if the screensaver reports "please contact the vendor", leave the screesaver selected and close System Preferences,
  • reboot,
  • check back to Desktop & Screesaver to see if Aerial works. In my case it took 3 reboots.
    (note: same "false alarms" happen for iOS Screensaver, for example)

@alistairmcmillan
Copy link
Collaborator

That is very weird. I've seen that message randomly before when switching between screensavers but never worked out why. If you leave Aerial selected, close System Preferences and let the screensaver start naturally after the 5 minute delay does it just show the same error full screen?

Is there any chance you have two copies installed? One in /Library/Screen Savers and another in /Users/YOURUSERNAME/Library/Screen Savers?

@TheWojtek
Copy link
Author

No, just a single copy for sure.
If I used a hot corner, the effect was just as expected - error message across the screen. Same thing after timeout. However, both methods are working now after reboots.

@alistairmcmillan
Copy link
Collaborator

That is so weird. I could understand why it might need one reboot. There does seem to be a bug in OS X where it holds on to old versions of plugins (which OS X screensavers basically are) but that should have been solved by one reboot.

Is it all working for you now though? Are you happy to close this issue?

@msheaver
Copy link

The latest iteration of Mac OS X (10.11 El Capitan) sets different permissions on applications based upon whether they are signed my a valid developer and the user has the opportunity to override those permissions in System Preferences -> Security & Privacy -> General -> Allow apps downloaded from. I wonder if something inside of that may be causing the erratic behavior being discussed here;

Just a random thought.

@TheWojtek
Copy link
Author

Is it all working for you now though? Are you happy to close this issue?

Yepp, feel free to close it. It's great!

@alistairmcmillan
Copy link
Collaborator

@msheaver That can cause issues but if it was a Gatekeeper permission blocking it from running I don't think rebooting would have solved the issue that TheWojtek was having.

@TheWojtek Anyway glad to hear it's working now. Closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants