Mac Studio: Window location, mouse settings, etc..

[asykes]

Hi Mac users,

After many happy years with a MacPro 5,1 I had to upgrade to a current system for compatibility reasons. My current machine is a mid level Mac Studio. Since I got this machine, I've had a few issues. One of the most annoying, is a problem with the app windows staying in their last used position. Upon sleeping the machine, the windows will always consolidate to the primary monitor (dual monitor setup). Oddly, if I go to open a new window instance the new window will pop up where the last usage before sleeping happened, regardless of the current window position.

I know it's not that big of a deal, but anything that interrupts work flow is a time consuming nuisance.

I'm not sure if it might be related, but this machine also has an issue with walking itself up from sleep randomly. I've tried to investigate, but no real luck. I have a fresh and current install of Ventura running as the machine was wiped when the ethernet card failed a few weeks ago. I figured the fresh install would sort it. Alas, no such luck.

I've also just realized that my mouse setting keep reverting. I have the center button set up for Mission Control and it keeps going back to unassigned.

 

[wdhpgx]

I've run into two things:

• Sometimes when I awaken it from sleep the next morning, the iTerm windows and Finder windows have relocated themselves from the secondary monitor to the primary monitor.
  • And other times, both sets of windows stay where they were on the secondary monitor
  • I'm still trying to discern what causes it to happen vs not happening
  • One variable is my secondary monitor is on an hdmi port on a multi-port usb hub thing, and I've observed some issues with a down-stream usb hub possibly back-feeding power and causing the monitor to not be present to the OS at boot time; I've since unplugged the power on that down-stream usb hub, but it seems like I still observed the issue with sleep after doing that. But, it hasn't done it for the past few days, so I'm ultimately unsure.
• When Activity Monitor re-opens its windows (eg after logout/login), it never restores them to their prior location on the secondary monitors, and always places them at the corresponding position on the primary monitor.
  • I believe this was also true on Big Sur on an m1 mini, before I bought the studio, so it's not a new thing
  • I don't recall if this happened at sleep/wake or not; I was mostly noticing the iTerm and Finder windows

My mac studio max replaced a macpro 3,1; both monitors are older DVI, one connected to on-board hdmi, and the other on the hub's hdmi. I'm running Monterey.

My mac studio was largely silent the past year and only recently started its "whine", so I'm now sleeping it at night. With the recent OS versions and the m1 processor, it looks like getting a mac to reliably stay asleep is a lot more complicated than it used to be. I'm using Sleep Aid and that seems to help. Even so, I have to manually disable Time Machine every night, else it spends all night alternately backing up, or banging on the backup drive to update Spotlight.

 

[Bigwaff]

Since upgrading to Ventura, I’ve noticed similar windowing behavior. Considering turning off Stage Manager to see if the window positioning and movement behavior stops.

 

[ColdCase]

The sometimes random relocation of finder windows have been going on for years, perhaps since High Serra time frame. I keep upgrading OS in the hope it will be corrected, but Apple doesn't seem to care.

I use a display port monitor with the iMacPro. With the Studio I have a studio display and a display port monitor.

Don't have the issue with the 5,1.

The insomnia and crash on shutdown has also been around for years. For me its usually caused by the interaction with a TB drive enclosure. The 5,1 didn't have the issue, but the iMacPro, 2013 Macbook pro, and the studio all do that more often than not. I resorted to just leaving the studio on 24/7 and shutting down the iMacPro. The 5,1 sleeps soundly, but then its not running a current OS.

Just saying its not only a studio issue, probably an OS issue.