Ludovic Courtès skriver:
>> Now I no longer use SDDM (or any DM), but I was able to work around it
>> by adding #:pid-file:
>>
>> diff --git a/gnu/services/desktop.scm b/gnu/services/desktop.scm
>> index 265cf9f35f..6b7d832a44 100644
>> --- a/gnu/services/desktop.scm
>> +++
Hi!
Marius Bakke skribis:
> Indeed. It was because I had 'sddm-service-type' configured, which
> attempted to communicate with "org.freedesktop.login1" over D-Bus, which
> in turn autostarted elogind before shepherd had gotten around to it.
Oh.
> Now I no longer use SDDM (or any DM), but I
Marius Bakke writes:
> Ludovic Courtès writes:
>
>> Hi Marius,
>>
>> Marius Bakke skribis:
>>
>>> On a newly-installed i7 system, Shepherd believes that the "elogind"
>>> service is not running. Yet there is an 'elogind-daemon' process,
>>> spawned by PID 1, preventing subsequent "herd start
Ludovic Courtès writes:
> Hi Marius,
>
> Marius Bakke skribis:
>
>> On a newly-installed i7 system, Shepherd believes that the "elogind"
>> service is not running. Yet there is an 'elogind-daemon' process,
>> spawned by PID 1, preventing subsequent "herd start elogind" invocations
>> from
Hi Marius,
Marius Bakke skribis:
> On a newly-installed i7 system, Shepherd believes that the "elogind"
> service is not running. Yet there is an 'elogind-daemon' process,
> spawned by PID 1, preventing subsequent "herd start elogind" invocations
> from succeeding.
Could you show the relevant
Hello,
On a newly-installed i7 system, Shepherd believes that the "elogind"
service is not running. Yet there is an 'elogind-daemon' process,
spawned by PID 1, preventing subsequent "herd start elogind" invocations
from succeeding.
signature.asc
Description: PGP signature
