[Pkg-utopia-maintainers] Bug#758557: Bug#758557: network-manager: not authorized to control networking

OmegaPhil OmegaPhil00 at startmail.com
Sat Aug 30 10:57:52 UTC 2014


On 30/08/14 11:06, Tyler wrote:

> Next I did some research on systemd, and found the following page which
> explains how to determine which init is active on boot-up:
> (http://www.reddit.com/r/debian/comments/29ydkj/jessie_am_i_running_systemd/). 
> 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:
> (http://forums.debian.net/viewtopic.php?f=17&t=116810).  (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.
> 
> 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.** **


For reference I won't be switching over to systemd, so a normal SysV
init here. Debian is committed to supporting alternative init systems,
so having something only work under systemd is unacceptable.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-utopia-maintainers/attachments/20140830/37eca583/attachment.sig>


More information about the Pkg-utopia-maintainers mailing list