Aerial: Can't exit screensaver without using force quit.
General troubleshooting tips
Before logging an issue please check that:
- You have the latest version installed (There may be a beta version that fixes your issue), see here for the latest releases and bug fixes: https://github.com/JohnCoates/Aerial/releases
- Your issue isn’t already mentioned in our issues. You may find a workaround there or a similar request already made.
- Your problem isn’t mentioned in the troubleshooting section.
If none of this fixes your issue, tell us about the problem you are experiencing or the feature you’d like to request.
Required information
In order to help us sort your issue, we ask that you provide the following information:
- Mac model: MacBook Pro (13-inch, 2018, Four Thunderbolt 3 Ports)
- macOS version: 10.14.4 (18E226)
- Monitor setup: using internal + external screen (PHL 272B8Q 27-inch (2560 x 1440)). Screensaver is set to only show on external screen.
If appropriate, please enable Debug mode and Log to disk in Advanced tab and replicate your bug, then attach the AerialLog.txt file (You can access this file through the Advanced tab).
Description of issue / Feature request
Seemingly at random the screensaver gets ‘stuck’ and I cannot close it without resorting to force quit (cmd-opt-shift-esc). The screensaver continues to play and when I move the mouse I actually see the mouse move on top of the video. Cmd-tab or similar do not work either.
The issue appears randomly every few days, otherwise it exits normally. I am not sure why it happens those times and have not managed to reproduce it, which is why the log is missing; it just happened again but might as well take a while before I see it again.
It seems similar to the (closed) issue #51, but I do not have the options set like in that ticket.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 89
@penx & @apwelsh thanks for getting back to me on this, and apologies because I was confused reading the macrumors story. I did spend a lot of time yesterday going through user reports from people on macrumors and 9to5 and here’s my best explanation of what is happening for them (and you, incidentally) :
So, again, sorry, disabling fast user switching does seem to stop the first bug (screensaver launching on its own) but not the second. The first bug seems to only happen on Big Sur (and maybe M1) for people with multiple user accounts and fast user switching. So, let’s put that one aside.
Here’s what’s interesting, there are multiple people on macrumors/9to5mac and other sites that have confirmed they hit the second issue infrequently, and with some system screensavers. Most people don’t mention the screensaver they are running but some mentioned for example the default Music screensaver.
So at that point I think the theory that some background app may be able to steal focus from
ScreenSaverEngine.appis probably on the right track. I’ll try to see if I can come up with some way to 100% reproduce the issue here to try and narrow it down.It’s quite possible that not all system screensaver may hit the issue, as Apple ported a few of theirs to their new API, while a lot of others (like Music) run either under the compatibility thing they introduced in Catalina
legacyScreenSaver.appexor some other compatibility thing (something likeiLifeScreensaver.appexpossibly ?).Interestingly the issue started with 10.14.4 where they started to change some things for screensavers, although at this point it’s still not super clear to me what they did back then.
Well, it wasn’t obvious to me. The original issue as pointed by @BorBorBor was linked to the old auto update system for Aerial, which I made a workaround early on, and that I fully removed in 2.0. After removing it, multiple people confirmed it fixed the issue for them, including up here.
Since that release I haven’t had a single report until @penx the other day. I did keep the bug open for a whole 3 month after the last user confirmation that it was fixed too just in case. But I guess whatever I do, that’s never enough…
I don’t mean to thread-jack, but don’t want to open a duplicate bug report. I have been experiencing this with version 1.8.2 on Catalina 10.5.4. So the bug still appears to exist. This is the only Screen Save I have ever had the problem with, and the only 3rd part screen save. Unlike @alecmocatta I do not have this issue with Drift nor Flurry, nor any other Apple screen saver.
btw, THANK YOU for this. I love these Aerials on my Apple TV had am so excited to hame them on my dual monitor setup. I love how I was able to calibrate monitor position to make the video transition smoothly between screens.
Ok please update me if you experience any locking issue but I think it’s good, I haven’t had reports about that yet in 2.0. Thanks !
Sorry, Little Snitch is a 3rd party firewall (https://www.obdev.at/products/littlesnitch/index.html). It’s nice, but it doesn’t play well with screensavers in general.
Yes, just be aware that with the next Big Sur beta, your videos may go missing.
I’m seeing the same issue as OP, but for an Apple screensaver (Flurry). Definitely a macOS bug – I’ve filed it with Feedback Assistant and it can be viewed here.
Hi @jacklawry
1.6.4 is the best version for now, yes. Settings don’t seem to have much impact as far as I know regarding the screensaver not quitting after you authenticated.
This looks to be a macOS bug as far as I understand (the screensaver never quits by itself, macOS starts and stops us at will on as many screens as needed), though I haven’t been able to reproduce it here yet.
There may be a common factor on those who hit the bug (the one you specifically mention, the others upthreads are of a fixed, separate issue) but I haven’t managed to find it yet (you’re the second person to report that particular issue so far).
If you are able, I would highly suggest filing a radar through feedback assistant from your machine, as this may help to get the bug resolved. I can guide you through it if needed.
Edit: Completely forgot, but to easily quit, you can press cmd-opt-shift-esc, this will hopefully make it less of a hassle for you.
Ok, I’ve got it installed. I’ll let you know what happens. I typically don’t use this computer over the weekend, so if it doesn’t happen in the next couple hours, it will probably be Monday at the earliest I can test again. Just wanted to give a heads up.
I had just updated to 1.6.2 after posting! Guess I should have tried some of this first 👍
@BorBorBor
Interesting, glad to hear that disabling updates worked for you. My understanding in your case is that Sparkle which I use for auto updates may make Aerial lose focus on some systems but not all (when another app that may steal focus is involved). Glad to hear that fixed, hopefully I can find a better way to handle auto updates then.
I guess you don’t use Sparkle either ? I’d suggest you look at this post here : https://github.com/JohnCoates/Aerial/issues/768#issuecomment-491163629 , there’s a link to a gist with a script that tells you who has focus. Might be interesting for you to see what is happening when your screensaver loses focus.
Haha, I guess that’s not a very marketable skill 😉 The whole process should probably be less painful that it is now though, and I don’t have high hopes for Catalina…