From: rennes@openmailbox.org
To: guix-devel@gnu.org
Subject: Re: NetworkManager doesn't "Connect automatically"
Date: Tue, 13 Dec 2016 09:26:24 -0600 [thread overview]
Message-ID: <cd2c14faf16e4fc43e1669f60eb9e6c9@openmailbox.org> (raw)
In-Reply-To: <1481639851.2533.4.camel@redhat.com>
Hello,
On 2016-12-13 08:37, Thomas Haller wrote:
> This restricts the connection to a certain user, determined by the
> connection.permissions property (see `nmcli connection show $NAME`
> and `man nm-settings`).
>
> This makes the connection only available, when a session for that user
> exists. Is that user logged-in?
>
> Did you build NetworkManager yourself? Is session-tracking properly
> enabled to use systemd-logind or consolekit.
>
> Starting NetworkManager with --debug is usually not that useful. The
> most interesting thing it does is to turn on debug-logging, which you
> can do otherwise [1].
> [1]
> https://cgit.freedesktop.org/NetworkManager/NetworkManager/plain/contrib/fedora/rpm/NetworkManager.conf?id=c90ec2d8c8a12b44c908bf7f80b23059c29f68fa
Accordig to what Thomas comments, I have two ideas:
* I wil try to compile 'network-manager' with
'--with-session-tracking=consolekit'.
* I remember that we do not have the file 'NetworkManager.conf' under
'/etc/NetworkManager' directory.
I will perform the tests in the afternoon.
Thanks
next prev parent reply other threads:[~2016-12-13 15:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 6:51 NetworkManager doesn't "Connect automatically" Chris Marusich
2016-12-13 14:37 ` Thomas Haller
2016-12-13 15:26 ` rennes [this message]
2016-12-13 22:38 ` Ludovic Courtès
2016-12-14 9:13 ` Chris Marusich
2016-12-14 9:20 ` Andy Wingo
2016-12-14 10:06 ` Chris Marusich
2016-12-15 7:16 ` Chris Marusich
2016-12-15 10:24 ` Chris Marusich
2016-12-15 10:41 ` Andy Wingo
2016-12-15 15:53 ` Ludovic Courtès
2016-12-17 9:33 ` Chris Marusich
2016-12-14 9:38 ` Chris Marusich
2016-12-14 21:08 ` Thomas Haller
2016-12-17 9:51 ` Chris Marusich
2016-12-19 11:45 ` Thomas Haller
2016-12-23 10:09 ` Chris Marusich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cd2c14faf16e4fc43e1669f60eb9e6c9@openmailbox.org \
--to=rennes@openmailbox.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.