screensaver | Chrome Extension providing a screensaver with custom photo | Browser Plugin library

Concerning the FFMpeg part, I think a good way to start is to actually use the PHP-FFMpeg library. The Basic Usage section in the documentation contains an example on how to generate a frame for a given video:

applaunchservices appears to be Apple-only:

Simple package for registering an app with apple Launch Services to handle UTI and URL. See Apple documentations for details.

I suspect you don't need that, either. Did you create your requirements.txt from a pip freeze? There's likely a bunch of stuff in there you don't need.

I suggest you review that file and remove anything you aren't directly depending on. pip will find transitive dependencies (dependencies your dependencies depend on) and install them automatically.

Prune that file, commit, and redeploy.

I found how to do so :

• First, I permanently deactivate screen-saver with autostart script and commands :

  @xset s off

  @xset -dpms

• Next, I only "play" with hdmi activation when I need it:

Browsing through the source code on github i have found this comment:

Initializations that potentially take place as a priveleged user: If the executable is setuid root, then these initializations are run as root, before discarding privileges.

The function which this comment addresses:

set_image is a method. The method does not return an image, but it sets the image and rect attributes of the object. Therefore:

player.image = player.set_image('screensaver/blue_car.png',)

Your code runs as expected on macOS Big Sur, which is already Apple Silicon, with native Python 3.9.

It looks like the culprit would be Rosetta or Monterey and not your code, but I did see some weird bugs when working with Swift on Rosetta. Have you considered looking that way ?

I am using the code below to start an installed camera app (not developed by me) from a background service

Launching activities from the background is not supported on modern versions of Android.

Also note that many devices will not have that particular package.

I need to determine if the camera app is done loading and ready to use so I can prompt the camera to take a picture

There is no canonical definition of "done loading and ready to use". And, in general, there is no means for you to monitor the operations of another app, for privacy and security reasons.

Also, outside of accessibility services, in general, you have no means of telling a running app to do anything unless it has a specific API for that purpose. Even with accessibility services, I suspect that it will be difficult to come up with an approach that works no matter what the camera app is.

If, from the foreground, you want a camera app to take a picture, use ACTION_IMAGE_CAPTURE. Or, integrate camera functionality directly in your own app, such as via CameraX or other libraries.

Install "Swift 5 Runtime Support for Command Line Tools" from https://support.apple.com/kb/dl1998?locale=en_US on the macOS 10.13 machine I wanted to run the screensaver on.

Thanks to the comment of @Alexander, where he suggested:

Have you tried poking around Console.app to see if anything intersting was logged?

I was able to figure it out.

In Console.app, in the default view that shows device messages for the computer, I applied a search filter for any occurence of the name of the screensaver and then in System Preferences > Desktop & Screen Saver, I selected my screensaver and clicked "Preview" hoping that this would result in something in the logs. And it did!

Relevant log message:

Error loading /Users/erikn/Library/Screen Savers/vibe.saver/Contents/MacOS/vibe: dlopen(/Users/erikn/Library/Screen Savers/vibe.saver/Contents/MacOS/vibe, 265): Library not loaded: @rpath/libswiftCore.dylib

Referenced from: /Users/erikn/Library/Screen Savers/vibe.saver/Contents/MacOS/vibe

Reason: image not found

With this in hand, I was then able to find a similar root cause and some suggested solutions at dyld: Library not loaded: @rpath/libswiftCore.dylib / Image not found

Which amount to setting "Always Embed Swift Standard Libraries" to YES, and possibly also adding @executable_path/Frameworks to Runpath Search Paths.

This may be one acceptable way of doing it.

However, not knowing the specifics of how this will interact on other systems and in the future I was a bit hesitant.

Fortunately, I then found https://developer.apple.com/forums/thread/687847 which while not directly relevant directed me to look for "Swift 5 Runtime Support for Command Line Tools", as this would provide the missing libswiftCore.dylib for macOS 10.13.

you can try uninstall from control panel

open control panel -> select uninstall a program -> select your application what you want to uninstall -> click uninstall

and iam recommended you to using lightshot