Sublime Forum

4143+ builds will not start from finder

#1

I have an annoying issue that has been going on for me since i first updated from Sublime 3 to 4 builds. The issue is that when launching from finder Sublime Text 4 simply shuts down and closes. Sublime 3 works fine on same system. Sublime 4 (4143-4150) all close immediately upon launch.

Interestingly, if I launch Sublime Text 4 form shell (open -a Sublime\ Text) it works normally.

I have cleared all resources from my machine related to sublime and performed a fresh install but it still crashes on this machine. I have another mac for work (same model and os) and it works fine. the only difference is that this machine never had Sublime Text 3 installed. It has to be some weird interaction with another resource and I would really like to get it resolved. Any suggestions would be appreciated.

Apple M1 Max
Ventura 13.4

launchd log is brief:
2023-06-09 10:29:00.126770 (gui/501/application.com.sublimetext.4.27134872.27134878) <Notice>: internal event: WILL_SPAWN, code = 0 2023-06-09 10:29:00.126771 (gui/501/application.com.sublimetext.4.27134872.27134878) <Notice>: service state: spawn scheduled 2023-06-09 10:29:00.126772 (gui/501/application.com.sublimetext.4.27134872.27134878) <Notice>: service state: spawning 2023-06-09 10:29:00.126797 (gui/501/application.com.sublimetext.4.27134872.27134878) <Notice>: launching: launch job demand 2023-06-09 10:29:00.127153 (gui/501/application.com.sublimetext.4.27134872.27134878 [7122]) <Notice>: xpcproxy spawned with pid 7122 2023-06-09 10:29:00.127158 (gui/501/application.com.sublimetext.4.27134872.27134878 [7122]) <Notice>: internal event: SPAWNED, code = 0 2023-06-09 10:29:00.127160 (gui/501/application.com.sublimetext.4.27134872.27134878 [7122]) <Notice>: service state: xpcproxy 2023-06-09 10:29:00.127176 (gui/501/application.com.sublimetext.4.27134872.27134878 [7122]) <Notice>: internal event: SOURCE_ATTACH, code = 0 2023-06-09 10:29:00.154862 (gui/501/application.com.sublimetext.4.27134872.27134878 [7122]) <Notice>: service state: running 2023-06-09 10:29:00.154878 (gui/501/application.com.sublimetext.4.27134872.27134878 [7122]) <Notice>: internal event: INIT, code = 0 2023-06-09 10:29:00.154882 (gui/501/application.com.sublimetext.4.27134872.27134878 [7122]) <Notice>: job state = running 2023-06-09 10:29:00.154917 (gui/501/application.com.sublimetext.4.27134872.27134878 [7122]) <Notice>: Successfully spawned sublime_text[7122] because launch job demand 2023-06-09 10:29:03.456497 (gui/501/application.com.sublimetext.4.27134872.27134878 [7122]) <Notice>: exited due to exit(1) 2023-06-09 10:29:03.456501 (gui/501/application.com.sublimetext.4.27134872.27134878 [7122]) <Notice>: service state: exited 2023-06-09 10:29:03.456509 (gui/501/application.com.sublimetext.4.27134872.27134878 [7122]) <Notice>: internal event: EXITED, code = 0 2023-06-09 10:29:03.456512 (gui/501/application.com.sublimetext.4.27134872.27134878 [7122]) <Notice>: job state = exited 2023-06-09 10:29:03.456592 (gui/501 [100021]) <Notice>: service inactive: application.com.sublimetext.4.27134872.27134878 2023-06-09 10:29:03.456597 (gui/501/application.com.sublimetext.4.27134872.27134878 [7122]) <Notice>: service state: not running 2023-06-09 10:29:03.458968 (gui/501/application.com.sublimetext.4.27134872.27134878) <Notice>: removing job: caller = runningboardd 2023-06-09 10:29:03.458980 (gui/501 [100021]) <Notice>: removing service: application.com.sublimetext.4.27134872.27134878 2023-06-09 10:29:03.458986 (gui/501/application.com.sublimetext.4.27134872.27134878) <Notice>: internal event: PETRIFIED, code = 0 2023-06-09 10:29:03.458988 (gui/501/application.com.sublimetext.4.27134872.27134878) <Notice>: job state = removed

0 Likes

#2

It’s likely something to do with environment variables, as that’s the main difference between launching from the UI and through open.

0 Likes

#3

My shell env is normal but has some customizations to it. I would expect it to be more of a blocker than launching from Finder.

0 Likes