Tried everything, even from init.d could not run the script.

On Thu, 27 Jun 2019 at 23:17, Max abonnements@revolwear.com wrote:

I'd try to launch it as a script in /etc/init.d/ like described here:

https://tutorials-raspberrypi.com/raspberry-pi-autostart-start-program-autom...

On 27.06.19 22:38, Csaba Láng wrote:

...

Dear list, have to run a pd patch with GUI on raspbian but it won’t run

@reboot puredata -gui -open /path-to-patch

Any clue what is wrong? Tried everything even put into script but no

luck!

...

Best, Popesz

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management ->

https://lists.puredata.info/listinfo/pd-list

...

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list

On Fri, 2019-06-28 at 12:29 +0800, Chris McCormick wrote:

Hi,

On 28/6/19 4:38 am, Csaba Láng wrote:

...

@reboot puredata -gui -open /path-to-patch

Any clue what is wrong? Tried everything even put into script but no luck!

Questions:

• Is this installed in the crontab of the 'pi' user?

• Have you tried that exact command on the command line - e.g.

copying and pasting and ensuring it works?

• On my system at least the binary is called 'pd' rather than

'puredata' - have you verified this is the correct binary?

• By default cron is often missing important environment variables

such as PATH. Try specifying the full path to your puredata binary. You

To complement Chris' list:

• Re: environment variables: Scripts or commands might not be aware

that they are running in a graphical environment. When starting a GUI programm from terminal logged through ssh, specifying the DISPLAY helps (maybe you need that for cron, too): DISPLAY=:0 /usr/bin/puredata -gui -open /abs/path/to/your/patch

• However, this might still not be sufficient, since the the user's

crontab might be executed _before_ the graphical (a.k.a "desktop") environment is ready. You could prepend your command with 'sleep 20; ' but that might not be reliable and is ugly

• My final suggestion is to not use cron at all. Cron is good for

background scripts and daemon, but things get hairy with graphical applications (see above why). Most "desktop" environments provide a way to put programs to "autostart" so that those programs are started when the graphical user session is started. This avoids any race conditions (e.g. cron runs too early) and confusion about which user runs the session and what DISPLAY is used.

I believe the graphical environment of Raspbian is derived from LXDE. So, maybe this helps: https://wiki.lxde.org/en/Autostart

Roman

Thanks a lot for all the hints. Will test it and let you know the solution. Have a nice day! Popesz

On Fri, 28 Jun 2019 at 11:38, IOhannes m zmölnig zmoelnig@iem.at wrote:

On 6/28/19 9:04 AM, Roman Haefeli wrote:

...

• My final suggestion is to not use cron at all

+1 to everything you said, and this in particular.

gfamsdr IOhannes

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list