Opened 4 years ago

Last modified 4 years ago

#13040 new bug

Launch scripts in ~/config/data/user_launch don't work

Reported by: humdinger Owned by: axeld
Priority: normal Milestone: Unscheduled
Component: Servers/launch_daemon Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All


This is hrev50627.

I have a package that installs this launch script in $data/user_launch:

target desktop {
	service x-vnd.Clipdinger {
		if setting ~/config/settings/Clipdinger/Clipdinger_settings autostart

When the package is installed in the system hierarchy, Clipdinger is started on boot. If it's installed in the home hierarchy, it's not. As the launch_daemon is supposed to launch via app signature, it shouldn't matter in which hierarchy the binary ended up in, right? Am I missing something?

Attachments (1)

clipdinger-0.5.5-1-x86_gcc2.hpkg (130.2 KB ) - added by humdinger 4 years ago.
clipdinger package

Download all attachments as: .zip

Change History (2)

by humdinger, 4 years ago

clipdinger package

comment:1 by humdinger, 4 years ago

After installing, make sure to run the app and check the auto-start option.

Note: See TracTickets for help on using tickets.