Quote from Dae on 15.04.2024, 09:49

Have you tried uninstalling and reinstalling it?

3.58 is running fine on my Mac, so it’s not something affecting all Mac users

Quote from Guido on 15.04.2024, 11:25

It also runs fine here on my side. Could you try Dae's suggestion (uninstall and reinstall)? If that doesn't help, please let me know.

 

Quote from justjoheinz on 15.04.2024, 11:54

Unfortunately doing the un-/install cycle did not help. I also tried to turn of a virus checker but also without a change.

Guido, please let me know if there is anything I can provide to help you diagnose the problem.

Regards,

Markus

 

Quote from Guido on 15.04.2024, 12:01

Hi Markus,

It's possible that some information still stays on your Mac after deleting. Could you do following:

• Remove Scenic again
• Then open a finder window, and do <cmd>-<shift>-G. This will open the "Go to Folder" window.
• In that window enter "~/Library/Containers/" and hit ENTER
• Now look for the s c e n i c folder (it should look like below), and delete it.
• Then reinstall Scenic.

Let me know if that still doesn't work.

Cheers,
Guido

Quote from justjoheinz on 15.04.2024, 13:04

Unfortunately this did not change a thing. I was able to follow your instructions, but to no avail,

Regards Markus

 

Quote from DarrenS on 15.04.2024, 14:29

Same issue here. Just went to finish planning my trip and just the bouncing icon.

M1 MacBook Air

App Deleted, Cache Delete, Library Deleted, Reboot, Fresh Install, Bouncy Icon and nothing more

 

Quote from DarrenS on 15.04.2024, 14:35

Guido, if it helps, here is a section of the stack trace log when I attempt to run.

Client com.apple.runningboardd trying to look up container 2:com.pinguido.scenic with ambiguous user identity (client: <MCMUserIdentity: 0x600002f50680; personaType = unspecific>; container: <MCMUserIdentity: 0x600002f583c0; personaType = unspecific>)

Could not read metadata file at [/private/var/root/Library/Containers/com.pinguido.scenic/.com.apple.containermanagerd.metadata.plist]; error = Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory" UserInfo={SourceFileLine=1961, NSLocalizedDescription=<~~~>, FunctionName=<~~~>}

Failed to read container metadata [<private>]: (127|1|2|[/private/var/root/Library/Containers/com.pinguido.scenic/.com.apple.containermanagerd.metadata.plist])

[app<com.pinguido.scenic(501)>:59596] Memorystatus failed with unexpected error: Invalid argument (22)

memorystatus: Ignore assertion driven idle priority. Process not previously controlled Scenic:59596

 

Quote from Guido on 15.04.2024, 15:44

I wonder if it's M1 Macs? I'll give it a try on my wife's M1 Macbook Air later today.
What MacOS version are you all running?

 

Quote from justjoheinz on 15.04.2024, 17:09

I am on 14.4.1 .

 

Quote from DarrenS on 15.04.2024, 18:57

14.4.1

Quote from Guido on 17.04.2024, 09:49

Hi Guys,

Scenic is running fine on my M3 MacBook Pro, and also on my wife's M1 MacBook Air, updated to Sonomo 14.4.1.

I looked at @darrens stacktrace. Apparently there is a process, called "com.apple.runningboardd", looking for a file that doesn't exist. That process is not running on my Macs.

You can see if this process is running on your Macs through Activity Monitor (to open Activity Monitor do <cmd>-space and type in Activity Monitor).

I did some googeling as I'm unfamiliar with this process. To be honest, I didn't get much wisser from that. I'm not sure what this process does, and what starts it. I did find this link: https://discussions.apple.com/thread/253439567?sortBy=best that shows a solution on how to disable this process. It also mentions (in the last post) that it could somehow be related to a VPN. The post is a bit vague so not sure. If you are running a VPN, try turning it off to see if that works.

@darrens, since you sent me the stacktrace I assume you are quite technically inclined 🙂. Could you check your system and see if temporarily disabling the runningboardd process (through activity monitor) solves it?

Cheers,
Guido

 

Quote from DarrenS on 17.04.2024, 10:38

Hi Guido,

Runningboardd was introduced as a process in MacOS Catalina and one of its functions on apple silicon Macs is management of iOS / iPad apps. So I am surprised you did not seeing it running on your Macs.

RunningBoard engages early in the launch of iOS/iPadOS apps, and declares in the log that the process will be managed, noting its HOME and TMPDIR paths. It then tracks the app process, acquiring assertions, just as it does for Catalyst apps. Initially, RunningBoard sets its Jetsam priority to 0, its Darwin role to Background, GPU priority to ‘deny’, and CPU limits to defaults.

The above taken from https://eclecticlight.co/2021/04/21/how-macos-manages-ios-apps-runningboard-comes-of-age/

This process can be terminated but will immediately launch itself again (in fact the relaunch is so quick that in Activity Monitor the only way you knew it quit and reloaded is the change in pid).

As you know, I have uninstalled the app, cleared the library cache and rebooted and the problem persisted.

What I had NOT done, was manually kill the runningboardd process.

Doing this made no difference, the app still failed to load.

So I killed it again and the before touching anything did a full reboot (by reboot I mean actually turn off the Mac then power on).

Scenic Launched

As a reboot on it's own did not resolve the issue, and neither did killing the runningboardd process, the only thing I can maybe think is that runningboardd keeps a cache on disk that is reloaded on boot, and it was only when the process is force quit (in effect made to crash) and then rebooted that the cache is cleared. So maybe possible a path or something in scenic has changed/removed within the compiled package and my runningboardd had that cached and until that was force cleared could not load?

Pure speculation, but the combination of remove, delete library, install, kill runningboardd, immediately do a full power cycle (rather than restart) fixed the issue (at least for me)

 

Quote from Guido on 17.04.2024, 10:53

OK. Thanks for this info Darren. Very helpfull.

I wonder if killing runningboardd was necessary. Perhaps simply turning off the Mac and turning it on again works too? As I didn't receive any other feedback so far, this sounds plausible to me.

So, @justjoheinz / Markus, could you give following a try:

First simply try turning off your Mac and then turning it on again (don't reboot, but really turn it OFF, wait 30 seconds to a minute, and turn it back on again).

If that doesn't work,

Try following Darren's steps above.

Let me know how it goes?

 

Sidenote:

@darrens, I now see runningboardd in Activity Monitor too. After restarting Activity Monitor it took around 30 seconds to show up. Need to be more patient 🙂

 

Quote from Guido on 17.04.2024, 10:58

Ah...sorry.. I see that you already tried a Reboot only, and it didn't work.

Your assumption about the cached location sounds plausible. Although I did not change any paths, 3.58 was compiled with a newer XCode version, which perhaps changed a patch during compilation.

Quote from justjoheinz on 17.04.2024, 11:17

Hi *,

 

good news first - scenic is starting again.

find runningboardd

ps -ax | grep runningboardd
sudo kill -9 "PID of process"

start scenic - no change, no start
Restart Mac afterwards (power down /power up)
Scenic starts. Yeah!
Thanks Darren and Guido,
Markus

 

Quote from Guido on 17.04.2024, 11:28

Awesome. Thanks for your patience and help guys!