From: Philipp Stephani <p.stephani2@gmail.com>
To: Nicolas Richard <youngfrog@members.fsf.org>
Cc: 42242@debbugs.gnu.org
Subject: bug#42242: 27.0.91; emacs.service now requires emacs to be built with -lsystemd
Date: Sun, 12 Jul 2020 16:12:46 +0200 [thread overview]
Message-ID: <CAArVCkRfLRFa7TsAFksn_ro4w8t5pcirL07JPbEJqOw5jkTK=g@mail.gmail.com> (raw)
In-Reply-To: <87blkrpeyc.fsf@members.fsf.org>
Am Di., 7. Juli 2020 um 16:40 Uhr schrieb Nicolas Richard
<youngfrog@members.fsf.org>:
>
> Using emacs-27 branch
>
> I've been using the unit etc/emacs.service, provided with emacs, for
> quite some time.
>
> With emacs-27, it seemed to still work (i.e. no obvious error and I can
> create a frame with emacsclient) but then systemd decided that the
> operation had timed out and killed emacs :
>
> systemd[2465]: emacs.service: Start operation timed out. Terminating.
> systemd[2465]: emacs.service: Main process exited, code=exited, status=15/n/a
> systemd[2465]: Failed to start Emacs text editor.
> systemd[2465]: emacs.service: Unit entered failed state.
> systemd[2465]: emacs.service: Failed with result 'exit-code'.
>
> As it turns out, emacs now uses Type=notify (commit
> 19f5f7b19b0dcdae87476a3fd51c41f840b2b80f) instead of Type=simple, and
> this requires emacs to be built with -lsystemd. I didn't have
> libsystemd-dev installed, so it didn't work.
I guess what we could do is have Autoconf generate emacs.service,
using Type=notify if and only if Emacs is built against libsystemd.
Not sure whether that's 100% reliable, though.
next prev parent reply other threads:[~2020-07-12 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 14:39 bug#42242: 27.0.91; emacs.service now requires emacs to be built with -lsystemd Nicolas Richard
2020-07-12 14:12 ` Philipp Stephani [this message]
2020-07-13 2:52 ` Richard Stallman
2020-07-31 18:38 ` Bhavin Gandhi
2020-08-14 16:58 ` Lars Ingebrigtsen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAArVCkRfLRFa7TsAFksn_ro4w8t5pcirL07JPbEJqOw5jkTK=g@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=42242@debbugs.gnu.org \
--cc=youngfrog@members.fsf.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).