Re: NetworkManager doesn't "Connect automatically"

Thomas Haller <thaller redhat com> writes:

On Wed, 2016-12-14 at 01:38 -0800, Chris Marusich wrote:
Hi Thomas,

Thank you for the quick response!

Thomas Haller <thaller redhat com> writes:

Did you build NetworkManager yourself? Is session-tracking properly
enabled to use systemd-logind or consolekit.

Yes, I'm building it from source [1].  It looks like we might need to
adjust the way we build it to enable session-tracking, like you've
suggested.  Am I correct in understanding that I should only need to
pass the option "--with-systemd-logind=yes" to the configure script
enable session tracking via systemd-logind?  Is anything else


No, that should be enough.

Possibly it was already enabled before, detected automatically?


OK.  Thank you for confirming my understanding.

In GuixSD, we actually use elogind [1] instead of systemd for session
tracking.  This requires us to patch the NetworkManager source to use
elogind instead of systemd libraries.  For example, we do this sort of
patching successfully when packaging polkit [2].

I tried the same thing with NetworkManager [3], but it didn't quite work
out.  There are a lot of references to systemd in NetworkManager, and I
think I'm just not familiar enough with NetworkManager, systemd, or
elogind to know for sure what needs to be patched to trick
NetworkManager into using elogind instead of systemd for session
management.  For now, we've committed the package definition as-is, but
until somebody figures out exactly how to patch it to work with elogind,
users must use the previously mentioned work-around (make the connection
available to all users) if they want to enable automatic connection.

Thank you again for your help.  Hopefully soon we'll figure out how to
get NetworkManager working with elogind in GuixSD!



Attachment: signature.asc
Description: PGP signature

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]