-
All replies
-
Helpful answers
-
Dec 3, 2014 9:07 AM in response to kw21by kellyjdrummer,On my late 2012 Macbook Pro 15" I have found that moving the image to the picture folder into a "Wallpaper" folder that I created, then right clicking on the file and choosing "Set Desktop Picture" works. I couldn't get it to stick (this problem was apparent in Mountain lion, I think but was addressed much differently. I tried that method and got no result) by using the "Desktop and Screensaver" console.
I am not sure that a "Wallpaper" folder makes much difference, but I DO believe that NOT using the "Desktop and Screensaver" console actually is the trick.
I hope this works. It did for me.
-
Dec 10, 2014 8:46 AM in response to kw21by kw21,thank you for your reply. Tried your suggestion but still I'm not having any success fixing this very annoying problem. :-(
-
Dec 10, 2014 8:55 AM in response to kw21by iW00,Is this issue also appearing in safe mode: OS X: What is Safe Boot, Safe Mode? - Apple Support
Is this issue also appearing on new user account:
Isolating an issue by using another user account - Apple Support
Mac OS X: How to troubleshoot a software issue - Apple Support
-
Dec 10, 2014 11:19 AM in response to kw21by philliprodo,I have the same problem. What's strange on mine is that it only occurs after I put the iMac to sleep. If I do a reboot, the Desktop Background photo appears just fine (even if I woke it up from Sleep and the image was missing and then rebooted). Stranger yet, this only affects Desktop No. 1; all the other Desktops retain their background images. Very strange...
-
Dec 10, 2014 11:39 AM in response to philliprodoby kw21,Good point. The problem is particularly acute and mostly occurs after log out and entered sleep mode. Hmmm...
-
Dec 10, 2014 11:45 AM in response to kw21by Boyd Porter,Create a test log in id with administrator privileges. Log in to it. If the selected background "sticks" then it is a problem with the current user.
Have a nice day.
-
Sep 22, 2016 6:05 PM in response to Boyd Porterby kw21,I know this is an old problem but I did resolve. The problem originated with a program called Team Viewer. I experienced this again when working with another individual that uses the program.