After replacing kde-misc/networkmanagement with kde-misc/plasma-nm I can't start my OpenVPN connection any longer as consolekit tries to read an already-finished task's environ from /proc. I already filed a bugreport upstream at https://bugs.kde.org/show_bug.cgi?id=333569. Meanwhile I ask for networkmanagement to be unmasked and not removed until plasma-nm can start OpenVPN connections when using consolekit. Reproducible: Always
There is no activity in upstream since some time. Does it work in the meantime (for example with 0.9.3.4 or 0.9.3.5)?
(In reply to Johannes Huber from comment #1) > There is no activity in upstream since some time. Does it work in the > meantime (for example with 0.9.3.4 or 0.9.3.5)? Unfortunately not. Aside from the fact it depends on net-libs/libnm-qt-0.9.8.3 which conflicts with kde-frameworks/networkmanager-qt from kde-frameworks-5.* it does plain not work for me. All WiFi APs are listed as "connected" though there's only one AP the client is connected to. Restarting the WiFi-connection does not change this. Disconnecting does not work (unless I use the hardware RF-switch), reconnecting recreates the connection but again lists all APs in range as "connected". And my VPN-connection is not even listed at all. And no, entering the connection management window to start the VPN connection I do not regard as an option. So, I'll stick to kde-misc/networkmanagement as long as possible before and while switching to KDE-5.
Meanwhile there's consolekit-1.0.0 unmasked in tree, and upstream bug was 'resolved fixed' - did you give it another try?
(In reply to Andreas Sturmlechner from comment #3) > Meanwhile there's consolekit-1.0.0 unmasked in tree, and upstream bug was > 'resolved fixed' - did you give it another try? Response time out. I assume this is fixed upstream.
