[Pkg-utopia-maintainers] Bug#673136: Bug#673136: network-manager-gnome: nm-connection-editor shows no connections and everything is greyed out (can't edit anything)
biebl at debian.org
Wed May 16 14:22:57 UTC 2012
On 16.05.2012 16:16, Jameson Graef Rollins wrote:
> On Wed, May 16 2012, Michael Biebl <biebl at debian.org> wrote:
>>> In any event, as far as I understand things according to the
>>> documentation included with network-manager, the point of consolekit is
>>> to ensure that the user is a member of netdev. That can either be
>>> managed by consolekit, or the user can be added to that group manually.
>>> As I am already a member of netdev, even without consolekit's help, I
>>> don't see how this is the issue:
>> No, that's not how group netdev and consolekit work.
> If I fail to understand the role of consolekit please do enlighten me.
> From /usr/share/doc/network-manager/README.Debian:
> To allow users to connect to the NetworkManager daemon they have to be in the
> group "netdev". If you want to add a user to group "netdev" use the command
> "adduser username netdev" or one of the graphical user management frontends.
> After that you have to reload D-Bus with the command "service dbus reload".
> Alternatively you can install the "consolekit" package which will grant access
> for all locally logged in users.
> Are you telling me this is incorrect? The implication here is clearly
> that I could unintsall consolekit and still be able to use
> network-manager if I was in the netdev group, which I am.
This information is outdated. And yes, I should remove it.
> network-manager neither Depends or Recommends consolekit. If consolekit
> is required to use network-manager then the network-manager package is
> currently broken.
network-manager has a Recommends on policykit (which will pull consolekit).
>> In any case, as you can see above, your session is marked
>> active = FALSE
>> is-local = FALSE
>> That's why you can't edit/change the NM settings.
> See above. Why do these things mean I can change NM setting? How do
> they need to be different?
>> The easiest way to fix that is to use a login manager as I mentioned
> I am using XDM and am plenty happy with it. Suggesting that I use a
> different login manager is not a solution to this problem. Again, if
> there are unmet dependencies for this package, then the package is
Well, XDM does not have proper ConsoleKit integration.
>> See also
> This is a bug in consolekit. Can you explain why this bug is
> responsible for the problem I'm seeing?
It's a changed behaviour in consolekit, not necessarily a bug.
consolekit requires now that certain properties are set by trusted
entities, that's why the Xsession.d scripts no longer work.
> I very much appreciate your speedy help, Michael, but I have yet to hear
> any actual description of what exactly the problem is that I'm facing.
> If consolekit is required, why? What is it supposed to be doing?
consolekit is required to determine if your user is locally logged in
For this to work properly you need a properly setup stack.
XDM unfortunately doesn't work properly in that regard.
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 900 bytes
Desc: OpenPGP digital signature
More information about the Pkg-utopia-maintainers