Emacs

2496 readers

1 users here now

Our infinitely powerful editor.

founded 5 years ago

MODERATORS

Berserkware@lemmy.ml

Zippoh@lemmy.ml

Issues with daemon as systemd user unit (lemmy.ml)

submitted 1 year ago* (last edited 1 year ago) by highduc@lemmy.ml to c/emacs@lemmy.ml

4 comments fedilink hide all child comments

Hi!

I'm trying to run the emacs daemon as a systemd user unit, and I'm seeing this error when trying to launch the GUI client:

Authorization required, but no authorization protocol specified

From what I've seen online it might be due to it trying to start before I'm logged in or something like that.
It does work after restarting the unit but I don't want to do that every time.

Anyone else see this before? Any ideas for a fix? Is there a better way of starting the emacs daemon?

top 4 comments

sorted by: hot top controversial new old

[–] Shareni@programming.dev 2 points 1 year ago

Is there a better way of starting the emacs daemon?

I just use the DE/WM autostart functionality

[–] nmtake@lemm.ee 1 points 1 year ago

"emacsclient --alternate-editor=''" may work. If you need to solve the systemd issue, please post "systemctl --user cat emacs"(assuming the unit is "emacs") here.

[–] eldavi@lemmy.ml 1 points 1 year ago

Have you set the multiuser target as a prerequisite already?

[–] flux@lemmy.ml 1 points 1 year ago

I haven't done it, but you could try socket activation.