Amethyst icon indicating copy to clipboard operation
Amethyst copied to clipboard
verified publisher icon ianyh

App doesn't start on login

Open alloc33 opened this issue 3 years ago • 8 comments

Simply doesn't start on login some reason (Mac mini), but everything works fine on my MBP. Mac mini. Monterey 12.5 (M1 pro). Any suggestions how to fix that? It feels like start on login option is ignored on my Mac mini

alloc33 avatar Aug 08 '22 05:08 alloc33

i have same issue on MacBook Pro M1 Max. Monterey 12.5 When I click on "start Amethyst on Login" it doesn't mark the option.
amethyst version: 0.15.6

azinsharaf avatar Aug 09 '22 04:08 azinsharaf

btw in my case in just crashes on login (everything is fine on my MacBook Pro M1, only Mac mini has this issue)

alloc33 avatar Aug 11 '22 03:08 alloc33

btw in my case in just crashes on login (everything is fine on my MacBook Pro M1, only Mac mini has this issue)

solved by adding delay to app start (executing automator app which runs amethyst with delay, may be there is a better way, but at least it works)

alloc33 avatar Aug 13 '22 10:08 alloc33

encountering the same problem at iMac Monterey 12.5.1 with v0.16 and also had the same from 12.5.0 and 0.15.6

KubiGR avatar Sep 06 '22 10:09 KubiGR

I also have this issue.

I can't be sure, but it seems to be related to the following:

  • App is installed using homebrew
  • App is installed by another user (who is admin)
  • App is launched by current user (who is not admin)

When I check the launchd.log in console, I see the following:

2023-05-08 10:23:06.603653 (gui/504/application.com.amethyst.Amethyst.28378091.28378097) <Notice>: internal event: WILL_SPAWN, code = 0
2023-05-08 10:23:06.603655 (gui/504/application.com.amethyst.Amethyst.28378091.28378097) <Notice>: service state: spawn scheduled
2023-05-08 10:23:06.603656 (gui/504/application.com.amethyst.Amethyst.28378091.28378097) <Notice>: service state: spawning
2023-05-08 10:23:06.603666 <Notice>: Coalition Cache Hit: app<application.com.amethyst.Amethyst.28378091.28378097(504)> [1110]
2023-05-08 10:23:06.603679 (gui/504/application.com.amethyst.Amethyst.28378091.28378097) <Notice>: launching: launch job demand
2023-05-08 10:23:06.605443 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [12409]) <Notice>: xpcproxy spawned with pid 12409
2023-05-08 10:23:06.605451 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [12409]) <Notice>: internal event: SPAWNED, code = 0
2023-05-08 10:23:06.605454 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [12409]) <Notice>: service state: xpcproxy
2023-05-08 10:23:06.605486 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [12409]) <Notice>: internal event: SOURCE_ATTACH, code = 0
2023-05-08 10:23:06.679986 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [12409]) <Notice>: service state: running
2023-05-08 10:23:06.679995 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [12409]) <Notice>: internal event: INIT, code = 0
2023-05-08 10:23:06.679996 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [12409]) <Notice>: job state = running
2023-05-08 10:23:06.680014 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [12409]) <Notice>: Successfully spawned Amethyst[12409] because launch job demand
2023-05-08 10:23:06.700423 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [12409]) <Notice>: exited due to SIGKILL | sent by loginwindow[10860]
2023-05-08 10:23:06.700430 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [12409]) <Notice>: service state: exited
2023-05-08 10:23:06.700433 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [12409]) <Notice>: internal event: EXITED, code = 0
2023-05-08 10:23:06.700435 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [12409]) <Notice>: job state = exited
2023-05-08 10:23:06.700450 (gui/504 [100273]) <Notice>: service inactive: application.com.amethyst.Amethyst.28378091.28378097
2023-05-08 10:23:06.700451 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [12409]) <Notice>: service state: not running
2023-05-08 10:23:06.738387 (gui/504/application.com.amethyst.Amethyst.28378091.28378097) <Notice>: removing job: caller = runningboardd
2023-05-08 10:23:06.738401 (gui/504 [100273]) <Notice>: removing service: application.com.amethyst.Amethyst.28378091.28378097
2023-05-08 10:23:06.738411 (gui/504/application.com.amethyst.Amethyst.28378091.28378097) <Notice>: internal event: PETRIFIED, code = 0
2023-05-08 10:23:06.738414 (gui/504/application.com.amethyst.Amethyst.28378091.28378097) <Notice>: job state = removed

For some reason loginwindow is killing amethyst.

I also have this for some other apps installed by homebrew, but not all.

lougreenwood avatar May 08 '23 09:05 lougreenwood

It also seems that reinstalling with brew reinstall --cask amethyst --no-quarantine fixes the issue (verified just now)

I've also found this to fix other homebrew apps with this login problem.

Here's the output of the launchd.log file when launching after doing the --no-quarantine thing:

2023-05-08 10:58:31.281420 (gui/504/application.com.amethyst.Amethyst.28378091.28378097) <Notice>: internal event: WILL_SPAWN, code = 0
2023-05-08 10:58:31.281424 (gui/504/application.com.amethyst.Amethyst.28378091.28378097) <Notice>: service state: spawn scheduled
2023-05-08 10:58:31.281424 (gui/504/application.com.amethyst.Amethyst.28378091.28378097) <Notice>: service state: spawning
2023-05-08 10:58:31.281432 <Notice>: Coalition Cache Hit: app<application.com.amethyst.Amethyst.28378091.28378097(504)> [1110]
2023-05-08 10:58:31.281585 (gui/504/application.com.amethyst.Amethyst.28378091.28378097) <Notice>: launching: launch job demand
2023-05-08 10:58:31.282428 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [17667]) <Notice>: xpcproxy spawned with pid 17667
2023-05-08 10:58:31.282436 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [17667]) <Notice>: internal event: SPAWNED, code = 0
2023-05-08 10:58:31.282437 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [17667]) <Notice>: service state: xpcproxy
2023-05-08 10:58:31.282468 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [17667]) <Notice>: internal event: SOURCE_ATTACH, code = 0
2023-05-08 10:58:31.341998 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [17667]) <Notice>: service state: running
2023-05-08 10:58:31.342000 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [17667]) <Notice>: internal event: INIT, code = 0
2023-05-08 10:58:31.342001 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [17667]) <Notice>: job state = running
2023-05-08 10:58:31.342016 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [17667]) <Notice>: Successfully spawned Amethyst[17667] because launch job demand
2023-05-08 10:58:31.955885 (pid/17667 [Amethyst]) <Notice>: uncorking exec source upfront
2023-05-08 10:58:31.955890 (pid/17667 [Amethyst]) <Notice>: created

lougreenwood avatar May 08 '23 10:05 lougreenwood

It also seems that reinstalling with brew reinstall --cask amethyst --no-quarantine fixes the issue (verified just now)

I've also found this to fix other homebrew apps with this login problem.

Here's the output of the launchd.log file when launching after doing the --no-quarantine thing:

2023-05-08 10:58:31.281420 (gui/504/application.com.amethyst.Amethyst.28378091.28378097) <Notice>: internal event: WILL_SPAWN, code = 0
2023-05-08 10:58:31.281424 (gui/504/application.com.amethyst.Amethyst.28378091.28378097) <Notice>: service state: spawn scheduled
2023-05-08 10:58:31.281424 (gui/504/application.com.amethyst.Amethyst.28378091.28378097) <Notice>: service state: spawning
2023-05-08 10:58:31.281432 <Notice>: Coalition Cache Hit: app<application.com.amethyst.Amethyst.28378091.28378097(504)> [1110]
2023-05-08 10:58:31.281585 (gui/504/application.com.amethyst.Amethyst.28378091.28378097) <Notice>: launching: launch job demand
2023-05-08 10:58:31.282428 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [17667]) <Notice>: xpcproxy spawned with pid 17667
2023-05-08 10:58:31.282436 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [17667]) <Notice>: internal event: SPAWNED, code = 0
2023-05-08 10:58:31.282437 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [17667]) <Notice>: service state: xpcproxy
2023-05-08 10:58:31.282468 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [17667]) <Notice>: internal event: SOURCE_ATTACH, code = 0
2023-05-08 10:58:31.341998 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [17667]) <Notice>: service state: running
2023-05-08 10:58:31.342000 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [17667]) <Notice>: internal event: INIT, code = 0
2023-05-08 10:58:31.342001 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [17667]) <Notice>: job state = running
2023-05-08 10:58:31.342016 (gui/504/application.com.amethyst.Amethyst.28378091.28378097 [17667]) <Notice>: Successfully spawned Amethyst[17667] because launch job demand
2023-05-08 10:58:31.955885 (pid/17667 [Amethyst]) <Notice>: uncorking exec source upfront
2023-05-08 10:58:31.955890 (pid/17667 [Amethyst]) <Notice>: created

Sadly this doesn't work for Ventura 13.5.2, M2. Even after reinstalling using the suggested method the option still doesn't mark. Will look into delay automator app.

cyril-schroeder-ox avatar Sep 14 '23 19:09 cyril-schroeder-ox

Seems to be working well in MacOS Sonoma, seems that all of the quarantined apps installed by Home Brew which didn't autostart on previous versions of MacOS are happy now and start at login 🎉

lougreenwood avatar Oct 04 '23 10:10 lougreenwood