Arch Linux

RickDeckard

Member

From: Acworth, Georgia, USA

Registered: 2016-02-19

Posts: 59

x86_64 NetworkManager woes again, update from 1.8.4.1 to 1.8.5dev+22g5

Hi again, this is kind of a continuation of the old topic located here: https://bbs.archlinux.org/viewtopic.php?id=231218 and I'm experiencing the exact same stuff I did then, right down to a root 'loginctl show-session' made after a re-login displaying "Failed to get properties: No such file or directory."

This time libnm and the networkmanager dev- packages are standing out to me as possibly more likely culprits than lightdm - which I didn't upgrade today:

libnm (1.8.4.1 -> 1.8.5dev+22+g5f2855fad-1)
libnm-glib (1.8.4.1 -> 1.8.5dev+22+g5f2855fad-1)
networkmanager (1.8.4.1 -> 1.8.5dev+22+g5f2855fad-1)
network-manager-applet (1.8.4.2 -> 1.8.7dev+3+g3d7c0a89-1)
nm-connection-editor (1.8.4.2 -> 1.8.7dev+3+g3d7c0a89-1)

Nov 11 18:44:50 acidstar-two NetworkManager[22035]: <info> [1510443890.7984] audit : op="connection-activate" uuid="e8a7eb93-2958-41e5-97b0-acee7762309c" name="My Wireless Network" pid=21918 uid=1000 result="fail" reason="Not authorized to control networking."

Can I ask why packages that are marked as development (i.e.: not stable) are being pushed out to Arch users before they're ready?  Should I just downgrade all five packages this time and hope for the best?

Last edited by RickDeckard (2017-11-12 00:20:05)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,435

Re: x86_64 NetworkManager woes again, update from 1.8.4.1 to 1.8.5dev+22g5

Your session  is  broken, and the networkmanager updates have nothing to do with that, that message is a side effect of a much deeper problem on your system (even IF it were the networkmanager packages which are buggy, there's no way they can have a relation to your session issues, which are the real problem here), figure out the source of that, instead of blaming packagers/packages. Thousands of people are using the updated networkmanager without issue, me included. Dev branches get pushed out if they contain needed fixes and are pushed out after extensive testing.

To pick up where your thread left of, make sure that you do not have any instances of dbus-launch in any of the x startup files. post your lightdm configuration and the complete output of a

journalctl -b

Oh and something else, remove your user from network and polkitd, systemd's logind should properly provide you with that functionality, without those groups

Not a network issue, moving to NC...

RickDeckard

Member

From: Acworth, Georgia, USA

Registered: 2016-02-19

Posts: 59

Re: x86_64 NetworkManager woes again, update from 1.8.4.1 to 1.8.5dev+22g5

Your session  is  broken, and the networkmanager updates have nothing to do with that, that message is a side effect of a much deeper problem on your system (even IF it were the networkmanager packages which are buggy, there's no way they can have a relation to your session issues, which are the real problem here), figure out the source of that, instead of blaming packagers/packages. Thousands of people are using the updated networkmanager without issue, me included. Dev branches get pushed out if they contain needed fixes and are pushed out after extensive testing.

To pick up where your thread left of, make sure that you do not have any instances of dbus-launch in any of the x startup files. post your lightdm configuration and the complete output of a

journalctl -b

Oh and something else, remove your user from network and polkitd, systemd's logind should properly provide you with that functionality, without those groups

Not a network issue, moving to NC...

I am not blaming anyone and I don't understand why you're so defensive.  If I were blaming someone, I would state that the developers of x package are coding things badly or doing something else wrong, which I did not.  I only asked why packages marked as development are pushed out even with the possibility of breakage.  If you choose to take offense to that, that isn't something I can help. 

Just as you don't appreciate the implication that system development is going along anything less than smoothly, which is obvious according to your choosing to bold certain words, I don't appreciate the implication that I'm some idiot that just fell off the turnip truck. 

All I did was say that this issue is in fact continuing, which it is.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,435

Re: x86_64 NetworkManager woes again, update from 1.8.4.1 to 1.8.5dev+22g5

Blaming might have been a poor choice of words there, sorry about that. The fact remains, your current issues are not related to the networkmanager update. Your session isn't properly set up (NetworkManager could be the buggiest software out there, it shouldn't be able to prevent your logind session from initializing), a side effect of that is that NetworkManager doesn't get the permission it needs. I did bold out certain terms to drive home that there are certain peculiarities on your setup, that down grading will - at best - mask over for a short period of time, before inevitably coming up again. We will want to find the root cause of that.

To do that we need some more information on your setup.

Last edited by V1del (2017-11-12 02:25:58)