Open jay-motion opened 12 months ago
system.log
with version 0.8 on Ventura 13.6.3 shows
Dec 13 12:10:33 cliff legacyLoader-x86_64[1692]: Error: Error Domain=EnvLib Code=0 "Failed to load/start agent" UserInfo={NSLocalizedDescription=Failed to load/start agent}
Can't reproduce. The pane looks like crap on Ventura but it does work for me.
I'd need more information, most importantly how it was installed and on what type of Mac. There is a reason the issue template asks for these types of things ;-).
Hm .. i can provide those details for me, ie Intel-based, 2020 MacBook Pro.
I had an old install (from about 2021 that at some point stopped working). I dropped it following https://github.com/hschmidt/EnvPane#uninstallation , and then downloaded the new 0.8
removed the quarantine bit with the xattr
call and then installed with double-click on the prefPane file install and leaving "for me" selected, the FAQs make that pretty clear. (ie. traditional install)
My .MacOSX/environment.plist
contains 3 env vars, they are not set in iTerm.
What other information do you need? Build instructions look simple, is there some sort of debug mode, i can build for?
Interestingly, I can't execute the EnvPane
executable in ~/Library/PreferencePanes/EnvPane.prefPane/Contents/MacOS
.
EnvPane.prefPane/Contents/MacOS on ☁️ (eu-central-1)
❯ ls
EnvAgent EnvPane
EnvPane.prefPane/Contents/MacOS on ☁️ (eu-central-1)
❯ ./EnvAgent
2023-12-14 12:27:24.807 EnvAgent[8513:198398] Started agent ./EnvAgent (8513)
2023-12-14 12:27:25.913 EnvAgent[8513:198398] Setting environment
2023-12-14 12:27:25.916 EnvAgent[8513:198398] Setting 'GUROBI_HOME' to '/Library/gurobi902/mac64' using XPC launchd API.
2023-12-14 12:27:25.916 EnvAgent[8513:198398] Setting 'XLWINGS_LICENSE_KEY' to 'noncommercial' using XPC launchd API.
2023-12-14 12:27:25.916 EnvAgent[8513:198398] Setting 'GAMS_HOME' to '/Library/Frameworks/GAMS.framework/Versions/34/Resources' using XPC launchd API.
2023-12-14 12:27:25.916 EnvAgent[8513:198398] Setting 'JULIA_NUM_THREADS' to '8' using XPC launchd API.
2023-12-14 12:27:25.916 EnvAgent[8513:198398] Exiting agent ./EnvAgent (PID 8513)
EnvPane.prefPane/Contents/MacOS on ☁️ (eu-central-1)
❯ ./EnvPane
zsh: exec format error: ./EnvPane
EnvPane.prefPane/Contents/MacOS on ☁️ (eu-central-1)
❯ file EnvPane
EnvPane: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit bundle x86_64] [arm64:Mach-O 64-bit bundle arm64]
EnvPane (for architecture x86_64): Mach-O 64-bit bundle x86_64
EnvPane (for architecture arm64): Mach-O 64-bit bundle arm64
EnvPane.prefPane/Contents/MacOS on ☁️ (eu-central-1)
❯ pwd
/Users/coroa/Library/PreferencePanes/EnvPane.prefPane/Contents/MacOS
Ok, using the one-line installer instead and rebooting, made it work for me. Looks like the EnvPane
executable is not meant to be executed directly, since it still fails as above, but everything is working as expected.
ie. can confirm it works for me now. Sorry, if that is unhelpful.
I am witnessing the same behavior — with blank panel, but without the "Failed to load/start agent"
message in /private/var/log/system.log
¹.
In my case, reinstalling with the one-liner in README.md
didn't help; nor did rebooting.
On the other hand, allowing the agent to run at startup did. DUH! (Apple menu → System Settings → General → Login Items → Allow in the Background → Hannes Schmidt)
Sonoma 14.2.1 (23C71), Intel processor.
My heartfelt thanks for maintaining this critically useful piece of software, of which I have been a user since circa 2014, i.e. pretty much from its inception.
¹ Well I do have one, but it's three hours old as I'm writing this, so it's very likely a red herring from my earlier fumbling with xattr
and the long-form install procedure.