After updating from Lion to Mavericks, I have found that the User switching feature often leaves app windows resized and unresponsive after switching back to an already active user.
So User A is logged on, opens some apps, some fullscreen, some windowed.
User B switches to logon screen and logs in. also opens various apps
later User A switches back to their logon session and finds the previously opened apps have either minimised, or "rolled-up" like a X-window session allows in Linux, but there is no way to restore them - minimise or maximise commands from the taskbar has no effect.
Newly opened apps work fine, so the work-around is to quit the older apps and re-open. This happens nearly every time the users switch.
This has happened to a 2007 Alu iMac, which was always upgraded from Tiger to Lion, via all the intermediate OSX variants (never a clean install) without any issues, but the Mavericks update has shown this fault.
Then, the new 2013 iMac, which was migrated from that 2007 iMac has reproduced the fault.
Obviously the advice will come to clean install - but I want the migration of 4 users with 1Tb+ of data to 'just work' as a TM restore. How the hell do I find the quirk setting that is causing the fault which is probably an issue from a legacy OSX version with a setting/prefs file?
or - is there an easy way to clean install and get all the users back to a seamless refresh of their accounts and data?
So User A is logged on, opens some apps, some fullscreen, some windowed.
User B switches to logon screen and logs in. also opens various apps
later User A switches back to their logon session and finds the previously opened apps have either minimised, or "rolled-up" like a X-window session allows in Linux, but there is no way to restore them - minimise or maximise commands from the taskbar has no effect.
Newly opened apps work fine, so the work-around is to quit the older apps and re-open. This happens nearly every time the users switch.
This has happened to a 2007 Alu iMac, which was always upgraded from Tiger to Lion, via all the intermediate OSX variants (never a clean install) without any issues, but the Mavericks update has shown this fault.
Then, the new 2013 iMac, which was migrated from that 2007 iMac has reproduced the fault.
Obviously the advice will come to clean install - but I want the migration of 4 users with 1Tb+ of data to 'just work' as a TM restore. How the hell do I find the quirk setting that is causing the fault which is probably an issue from a legacy OSX version with a setting/prefs file?
or - is there an easy way to clean install and get all the users back to a seamless refresh of their accounts and data?