Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Martyimac

macrumors 68020
Original poster
Aug 19, 2009
2,492
1,730
S. AZ.
On my 2018 mini and my nMP the 10.14.2 update changed my screensaver setting from using my photos library to a generic built in screensaver.
Anybody else see any changes from the update?
 
Found another problem. Printer "not found". Happened on both machines using 10.14.2. I had to remove the printer, rescan and select the printer, then reinstall the printer.
And before anyone asks, yes the printer was up and connected to my home wifi system. The Windows 10 machines did not have this problem.
It just works? Bah humbug.
 
Found another problem. Printer "not found". Happened on both machines using 10.14.2. I had to remove the printer, rescan and select the printer, then reinstall the printer.
And before anyone asks, yes the printer was up and connected to my home wifi system. The Windows 10 machines did not have this problem.
It just works? Bah humbug.

wait... someone's having a problem with their mac? has the world finally ended? or maybe... it's not so serious, it's easily resolved, and is more of a quirk, than a bug/disaster/reason to switch OSes...
 
wait... someone's having a problem with their mac? has the world finally ended? or maybe... it's not so serious, it's easily resolved, and is more of a quirk, than a bug/disaster/reason to switch OSes...
Sure glad I didn't say anything about switching OS's. :p
 
On my 2018 mini and my nMP the 10.14.2 update changed my screensaver setting from using my photos library to a generic built in screensaver.
Anybody else see any changes from the update?
Switch it back. “Problem” solved.
 
Switch it back. “Problem” solved.
I did and yes, problem solved. But the real issue is, there is no published reason for the update to have done this. It's surprising, has never happened before and  should not have done it. Or if there WAS a reason, they should have put that info into the release notes so we wouldn't be caught unaware.
I did file a bug report.
 
I did and yes, problem solved. But the real issue is, there is no published reason for the update to have done this. It's surprising, has never happened before and  should not have done it. Or if there WAS a reason, they should have put that info into the release notes so we wouldn't be caught unaware.
I did file a bug report.

unless, of course, it's not an issue everyone has, but just some quirky behavior you've experienced. not everything is a conspiracy...
 
unless, of course, it's not an issue everyone has, but just some quirky behavior you've experienced. not everything is a conspiracy...
I just updated my '15 rMBP to 10.14.2 and the same thing happened to it. While I don't hold to a conspiracy I do find it quite odd that all 3 of my machines had the same thing happen.
 
I just updated my '15 rMBP to 10.14.2 and the same thing happened to it. While I don't hold to a conspiracy I do find it quite odd that all 3 of my machines had the same thing happen.

i find it quite odd that you mentioned 2 macs originally... and now it's 3. :cool: but seriously. could be something you have in software on both (or all 3?).... either way, it's a: not been commonly reported, and b: easily fixed.
 
i find it quite odd that you mentioned 2 macs originally... and now it's 3. :cool: but seriously. could be something you have in software on both (or all 3?).... either way, it's a: not been commonly reported, and b: easily fixed.

Why find it weird since I clearly posted "I just updated my '15 rMBP to 10.14.2 and the same thing happened to it."
 
Why find it weird since I clearly posted "I just updated my '15 rMBP to 10.14.2 and the same thing happened to it."

was going by your iniitial post, and the 2nd one as well. having it happen to three macs suggests something in your setup (a similar app, perhaps), and, most important of all, it seems both issues were easily resolved. glad you resolved it!
 
  • Like
Reactions: Martyimac
The big change I notice is the Combo update refuses to install with an error message saying the update is only for APFS formatted drives. All through the Beta tests, then 10.14.0 and 10.14.1 there was no problem installing on HFS+ disks.
Interestingly the 10.14.2 full installer will install on an HFS+ disk, but not the Combo or Delta update.
Anyone else experience the same, and if so did you find a way around it, other than converting to APFS.
 
On my 2018 mini and my nMP the 10.14.2 update changed my screensaver setting from using my photos library to a generic built in screensaver.
Anybody else see any changes from the update?
Hmm. Posted this yesterday; a direct response to the question.
Just updated a few days ago. It did not mess with my "screensaver" (using my photos). It found the folder I had been using.
 
Hmm. Posted this yesterday; a direct response to the question.
Just updated a few days ago. It did not mess with my "screensaver" (using my photos). It found the folder I had been using.

I updated today and see the same issue as OP.
It may not have changed the folder, but there is no way anymore to select an album from Aperture/iPhoto/Photos as a screensaver.
 
I updated today and see the same issue as OP.
It may not have changed the folder, but there is no way anymore to select an album from Aperture/iPhoto/Photos as a screensaver.
That's even worse than my issue, I was at least able to go back and re-set up my screen saver using the photoslibrary.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.