[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: NetworkManager doesn't "Connect automatically"
From: |
Chris Marusich |
Subject: |
Re: NetworkManager doesn't "Connect automatically" |
Date: |
Wed, 14 Dec 2016 01:13:05 -0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Hi Ludo,
address@hidden (Ludovic Courtès) writes:
> Hello network managers! :-)
Hopefully soon we will MANAGE to get it working! ;-)
> address@hidden skribis:
>
>> Accordig to what Thomas comments, I have two ideas:
>>
>> * I wil try to compile 'network-manager' with
>> '--with-session-tracking=consolekit'.
>
> On GuixSD we use “elogind”, which is like “systemd-logind”.
>
> However, the build log says:
>
> Platform:
> session tracking: consolekit
> suspend/resume: consolekit
>
> … which is definitely wrong.
>
> We need to tell it to use elogind, but adding it as an input is not
> enough. Ideas?
By running "./configure --help", I found these promising options:
--8<---------------cut here---------------start------------->8---
--with-systemd-logind=yes|no
Support systemd session tracking
--with-consolekit=yes|no
Support consolekit session tracking
--8<---------------cut here---------------end--------------->8---
I tried the attached patch, but when I built network-manager, I got:
--8<---------------cut here---------------start------------->8---
checking for SYSTEMD_200... no
checking for LIBSYSTEMD... no
checking for SYSTEMD_JOURNAL... no
checking for SYSTEMD_JOURNAL... no
checking for SYSTEMD_LOGIN... no
checking for SYSTEMD_LOGIN... no
configure: error: You must have libsystemd installed to build with
systemd-logind support.
phase `configure' failed after 5.3 seconds
builder for
`/gnu/store/2zv14p720wfw594g86sf8wsd6fmkh8s7-network-manager-1.4.2.drv' failed
with exit code 1
@ build-failed
/gnu/store/2zv14p720wfw594g86sf8wsd6fmkh8s7-network-manager-1.4.2.drv - 1
builder for
`/gnu/store/2zv14p720wfw594g86sf8wsd6fmkh8s7-network-manager-1.4.2.drv' failed
with exit code 1
guix build: error: build failed: build of
`/gnu/store/2zv14p720wfw594g86sf8wsd6fmkh8s7-network-manager-1.4.2.drv' failed
--8<---------------cut here---------------end--------------->8---
Did I make a mistake, or does NetworkManager just not recognize elogind?
I'll look into this more, but unless I made a mistake, I suspect that
either elogind or network-manager might require some tweaks to convince
network-manager that elogind is equivalent to systemd in this case.
--
Chris
0001-gnome-Enable-session-tracking-in-network-manager.patch
Description: Text Data
signature.asc
Description: PGP signature
- NetworkManager doesn't "Connect automatically", Chris Marusich, 2016/12/13
- Re: NetworkManager doesn't "Connect automatically", Thomas Haller, 2016/12/13
- Re: NetworkManager doesn't "Connect automatically", rennes, 2016/12/13
- Re: NetworkManager doesn't "Connect automatically", Ludovic Courtès, 2016/12/13
- Re: NetworkManager doesn't "Connect automatically",
Chris Marusich <=
- Re: NetworkManager doesn't "Connect automatically", Andy Wingo, 2016/12/14
- Re: NetworkManager doesn't "Connect automatically", Chris Marusich, 2016/12/14
- Re: NetworkManager doesn't "Connect automatically", Chris Marusich, 2016/12/15
- Re: NetworkManager doesn't "Connect automatically", Chris Marusich, 2016/12/15
- Re: NetworkManager doesn't "Connect automatically", Andy Wingo, 2016/12/15
- Re: NetworkManager doesn't "Connect automatically", Ludovic Courtès, 2016/12/15
- Re: NetworkManager doesn't "Connect automatically", Chris Marusich, 2016/12/17
Re: NetworkManager doesn't "Connect automatically", Chris Marusich, 2016/12/14