<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Package: network-manager<br>
Version: 0.9.10.0-1.1<br>
<br>
Status: fixed<br>
<br>
Debian Release: jessie/sid<br>
Linux debian 3.14-2-amd64 #1 SMP Debian 3.14.15-2 (2014-08-09)
x86_64 GNU/Linux<br>
<br>
loginctl show-session $XDG_SESSION_ID<br>
Id=1<br>
Timestamp=Sat 2014-08-30 00:07:34 PDT<br>
TimestampMonotonic=13226634<br>
VTNr=7<br>
Display=:0<br>
Remote=no<br>
Service=kdm<br>
Scope=session-1.scope<br>
Leader=1098<br>
Audit=1<br>
Type=x11<br>
Class=user<br>
Active=yes<br>
State=active<br>
IdleHint=no<br>
IdleSinceHint=0<br>
IdleSinceHintMonotonic=0<br>
Name=<username><br>
<br>
<br>
I had this same problem after a recent system update (of many
packages, not just network-manager) -- when I tried to up a
connection in the KDE network-manager applet, it said "Not
authorized to control networking". After doing some research I
thought it might have been an issue with Polkit permissions, as I
was also unable to mount volumes in Dolphin with udisks, and I was
unable to grant root privileges to Apper to download package lists
and install packages. It also seemed to be related to ConsoleKit
because when I ran ck-list-sessions it had "active = FALSE" in the
output. I then found that "ConsoleKit is currently not actively
maintained. The focus has shifted to the built-in seat/user/session
management of Software/systemd called systemd-logind!".<br>
<br>
<br>
Next I did some research on systemd, and found the following page
which explains how to determine which init is active on boot-up:
(<a class="moz-txt-link-freetext" href="http://www.reddit.com/r/debian/comments/29ydkj/jessie_am_i_running_systemd/">http://www.reddit.com/r/debian/comments/29ydkj/jessie_am_i_running_systemd/</a>).
My system was running sysvinit. I found it a little odd that I had
an active logind session while running sysvinit. So after looking
around some more and not getting anywhere, I decided to try
switching to systemd for a single boot by adding "int=/bin/systemd"
(symlink to /lib/systemd/systemd) to the kernel line in the grub
menu (pressing "e" to edit the line). I was fairly surprised to
find that this fixed all three of the problems, and it didn't seem
to break anything. I was able to enable a connection with
network-manager, and mount volumes in Dolphin, and download lists
and install packages in Apper. Additionally, my default connection
was enabled automatically on boot, and that hadn't happened for
several months (I had also used nmcli to set it to autoconnect so
that may have helped, but at least didn't fix it on its own). I did
find the following thread in which someone recommends installing
task-kde-desktop, so I installed that package:
(<a class="moz-txt-link-freetext" href="http://forums.debian.net/viewtopic.php?f=17&t=116810">http://forums.debian.net/viewtopic.php?f=17&t=116810</a>).
(Someone else recommends not using Apper, especially not with
testing, and I will probably take that advice.) I then went ahead
and installed systemd-sysv to use systemd permanently. I then ran
journalctl to view the systemd journal so I could check for error
messages, and there wasn't anything of concern.<br>
<br>
It sounds like jessie is in the process of switching over to systemd
from sysvinit before it is released as stable, so my guess is that
something was changed in one or more packages which made them
dependent on systemd. At least in my case, the problem wasn't
caused by a bug in network-manager itself.<strong></strong> <strong></strong>
</body>
</html>