Re: Screensaver running only on one display with a multiple display setup
> By logging when init and viewDidMoveToWindow methods, you can see when the > latter fails to be called. That's what i did > It's a bug Apple needs to fix. Oh, it's a well-known bug? Good to know. > They broke it some time ago, then didn't fix it when the partially fixed > legacy screensavers in 13.4. Just continue to report their bugs. Will do. > > I?m seeing it failing on MacOS 10.5.5 on a 3 monitor system and in 13.2.1 on > a 2 monitor system when compiled from source. And by ?fail?, I mean that it > only runs on one display. Thanks a lot! Would be interesting to see how it performs on 13.4 ... Best regards, Gabriel smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Screensaver running only on one display with a multiple display setup
I’m seeing it failing on MacOS 10.5.5 on a 3 monitor system and in 13.2.1 on a 2 monitor system when compiled from source. And by “fail”, I mean that it only runs on one display. Alex Zavatone > On Jun 12, 2023, at 7:23 AM, Steven Mills via Cocoa-dev > wrote: > > On Jun 10, 2023, at 12:45, Gabriel Zachmann via Cocoa-dev > wrote: >> >> Two of the instances never reach method -viewDidMoveToWindow. >> >> Is there a way to instrument the source code or the executable, such that I >> can receive a line-by-line trace of the execution of the three screensaver >> instances from that user? >> >> I am wondering if two of the instances are crashing. >> But I don't know how to retrieve more info about it (if any). > > By logging when init and viewDidMoveToWindow methods, you can see when the > latter fails to be called. It's a bug Apple needs to fix. They broke it some > time ago, then didn't fix it when the partially fixed legacy screensavers in > 13.4. Just continue to report their bugs. > > -- > Steve Mills > Drummer, Mac geek > > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com > > This email sent to z...@mac.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Screensaver running only on one display with a multiple display setup
On Jun 10, 2023, at 12:45, Gabriel Zachmann via Cocoa-dev wrote: > > Two of the instances never reach method -viewDidMoveToWindow. > > Is there a way to instrument the source code or the executable, such that I > can receive a line-by-line trace of the execution of the three screensaver > instances from that user? > > I am wondering if two of the instances are crashing. > But I don't know how to retrieve more info about it (if any). By logging when init and viewDidMoveToWindow methods, you can see when the latter fails to be called. It's a bug Apple needs to fix. They broke it some time ago, then didn't fix it when the partially fixed legacy screensavers in 13.4. Just continue to report their bugs. -- Steve Mills Drummer, Mac geek ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Screensaver running only on one display with a multiple display setup
> > I have one user, who has three displays connected to the Mac, but only the > main display (center) gets a screensaver. > This is on macOS Ventura 13.4. > (I should also say that with other users, who also have multiple displays, > everything seems fine.) > > According to the log file, legacyScreenSaver does launch three instances of > my screen saver, but then only one continues to run. Two of the instances never reach method -viewDidMoveToWindow. Is there a way to instrument the source code or the executable, such that I can receive a line-by-line trace of the execution of the three screensaver instances from that user? I am wondering if two of the instances are crashing. But I don't know how to retrieve more info about it (if any). Best regards, Gabriel smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Screensaver running only on one display with a multiple display setup
I have a screensaver that is supposed to run on all displays simultaneously. MacOS launches several instances, if there are multiple displays. I have one user, who has three displays connected to the Mac, but only the main display (center) gets a screensaver. This is on macOS Ventura 13.4. (I should also say that with other users, who also have multiple displays, everything seems fine.) According to the log file, legacyScreenSaver does launch three instances of my screen saver, but then only one continues to run. There are no error message or other hints - as far as I can see - as to why the other two instance do not continue to run; I believe they are killed. Does anyone have an idea? Or an idea how I could track down the problem? I know all three instances are launched because I can see their individual info messages in the log file. But then, only one of them continues to output info message in the log file. Thanks a lot in advance. Best regards, Gabriel smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
