Hi Michael, On Sat, Mar 29, 2014 at 11:00:56AM +0100, Michael Biebl wrote: > Am 29.03.2014 10:34, schrieb Salvatore Bonaccorso: > > Package: network-manager > > Version: 0.9.8.0-5 > > Severity: grave > > > > Hi > > > > Disclaimer: have set the severity to grave as it renders for me an > > non-working network connection (but I'm unable to replicate the > > problem on a second system -- but with a different setup). > > > > After updating network-manager from 0.9.8.0-5 to 0.9.8.8-4 which > > entered unstable network-manger looses the network connection. > > Selecting in the Wifi-Connection the desired connection leads to: > > > > Failed to add/activate connection > > (32) No session found for uid 1000 (unknown) > > > Please send me a full log when this happens. Stop the running > NetworkManager instance and run it in the foreground > > NetworkManager --no-daemon > > > Do you have a proper logind session registered? What's the output of > loginctl list-sessions > loginctl session-status <my_session_id>
I think with your hints I found the culprit. I use slim as login manager. And slim has a regression where it is not build with pam: #742904. Rebuilding again slim with PAM enabled now shows that I have a proper logind session (to answer also your follow-up question: yes, libpam-systemd was enabled). Now also all 4 combinations network-manager 0.9.8.0-5 + sysvinit network-manager 0.9.8.0-5 + systemd network-manager 0.9.8.8-4 + sysvinit network-manager 0.9.8.8-4 + systemd works. Regards, Salvatore (Just open is why with broken slim and previous network-manager, network-manager still worked).
signature.asc
Description: Digital signature
