FS#76745 - [emacs-nativecomp] 28.2-1 emacsclient doesn't start
Attached to Project:
Arch Linux
Opened by Martin Brodbeck (beedaddy) - Monday, 05 December 2022, 08:48 GMT
Last edited by Toolybird (Toolybird) - Sunday, 11 December 2022, 04:53 GMT
Opened by Martin Brodbeck (beedaddy) - Monday, 05 December 2022, 08:48 GMT
Last edited by Toolybird (Toolybird) - Sunday, 11 December 2022, 04:53 GMT
|
Details
Description:
I use emacsclient and therefore have the (user-) systemd daemon emacs.service enabled. But after system startup and logging into my desktop environment (GNOME, Wayland) I can't start emacs (client): --- snip --- emacsclient.desktop[5312]: Waiting for Emacs...*ERROR*: Display :0 can’t be opened systemd[1261]: app-gnome-emacsclient-5312.scope: Couldn't move process 5312 to requested cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-emacsclient-5312.scope': No such process dleyna-renderer-service[5242]: dLeyna: Exit systemd[1261]: app-gnome-emacsclient-5312.scope: Failed to add PIDs to scope's control group: No such process systemd[1261]: app-gnome-emacsclient-5312.scope: Failed with result 'resources'. systemd[1261]: Failed to start Application launched by gnome-shell. --- snip --- But after restarting the daemon, it works. So I guess the daemon started perhaps too early? Additional information: * Emacs 28.2-1 * GNOME 43 Steps to reproduce: 1. Enable the Emacs systemd daemon: `systemctl --user enable emacs.service` 2. Reboot the machine 3. Login to desktop environment (GNOME in my case) 4. Try to start "Emacs (Client)". It won't start. Workaround: 1. Restart the daemon with `systemctl --user restart emacs.service` 2. Now, "Emacs (Client)" starts successfully |
This task depends upon
Closed by Toolybird (Toolybird)
Sunday, 11 December 2022, 04:53 GMT
Reason for closing: Upstream
Additional comments about closing: See comments
Sunday, 11 December 2022, 04:53 GMT
Reason for closing: Upstream
Additional comments about closing: See comments
Yes, it appears to be the case. So how would you propose to fix it? i.e. where is the Arch packaging bug?
[1] https://unix.stackexchange.com/questions/397853/how-to-set-a-systemd-unit-to-start-after-loading-the-desktop
[2] https://bbs.archlinux.org/viewtopic.php?id=200094
[3] https://bbs.archlinux.org/viewtopic.php?id=267914
[4] https://superuser.com/questions/759759/writing-a-service-that-depends-on-xorg
[1] https://bbs.archlinux.org/viewtopic.php?id=281813