Hi all, Sorry for the spam. Using `shepherd -s shepherd-socket` and can start shepherd and communicate via `herd -s shepherd-socket`. I see nothing in ~/xcape.log yet, however. It does spawn many xcape processes and it seems like it found $DISPLAY, however. Any pointers on how to fix the original service definition?
Thanks, John On Fri, Feb 1, 2019 at 4:11 PM John Soo <js...@asu.edu> wrote: > Hello, > > I tracked down the shepherd file for the service and put most of the > contents in ~/.config/shepherd/init.scm: https://paste.debian.net/1064476/ > When starting shepherd with `shepherd` I get the following: > > 250:24 2 (main . _) Fri 08:09:37 AM 48:6 1 (open-server-socket _) In > unknown file: 0 (bind # #(1 "/run/user/1000…") #) > ERROR: In procedure bind: In procedure bind: Address already in use > > What should I do from here? Seems like I need to specify a separate > socket for the user instance of shepherd. > > Thanks! > > John > > On Wed, Jan 23, 2019 at 4:04 PM John Soo <js...@asu.edu> wrote: > >> Oh wait I’m not sure I’m doing it right. I don’t know how to start a user >> instance. I’ll go look that up. >> >> > On Jan 23, 2019, at 5:08 AM, Ricardo Wurmus <rek...@elephly.net> wrote: >> > >> > >> > Hi John, >> > >> >> I've been trying to define a service to keep xcape alive: >> >> >> >> https://paste.debian.net/1061770/ >> >> >> >> Which works nicely when spawning the service except /var/log/xcape.log >> has >> >> the following error: >> >> >> >> Unable to connect to X11 display. Is $DISPLAY set? >> > >> > Does the service work when you run it after starting a graphical >> > session? (e.g. with a user instance of the Shepherd.) >> > >> > -- >> > Ricardo >> > >> >
