From: John Soo <jsoo1@asu.edu>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: xcape service
Date: Fri, 1 Feb 2019 16:29:23 +0000 [thread overview]
Message-ID: <CAKf5CqU7f6x-NKM0so7pTvgF34EpKKb2c7QaH46hoqoJ6hRuQA@mail.gmail.com> (raw)
In-Reply-To: <CAKf5CqUMO0Uu3k2e5zmzdpBd5_UWAxfa5ROjuR-iuYw4N-vQeQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1774 bytes --]
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 <jsoo1@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 <jsoo1@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 <rekado@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
>> >
>>
>
[-- Attachment #2: Type: text/html, Size: 2888 bytes --]
prev parent reply other threads:[~2019-02-01 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 19:35 xcape service John Soo
2019-01-23 13:08 ` Ricardo Wurmus
2019-01-23 16:01 ` John Soo
2019-01-23 16:04 ` John Soo
2019-02-01 16:11 ` John Soo
2019-02-01 16:29 ` John Soo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKf5CqU7f6x-NKM0so7pTvgF34EpKKb2c7QaH46hoqoJ6hRuQA@mail.gmail.com \
--to=jsoo1@asu.edu \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).