Bug 333569

That's weird, because there is probably no difference between the old networkmanagement applet and plasma-nm. Both of them use same DBus calls.

Well I can't connect/disconnect via plasmoid at all.
Clicking Connect on a network produces

in .xsession-errors:

NetworkManagerQt "plasma-desktop" ( 3383 ) QDBusPendingReply<QDBusObjectPath> NetworkManager::NetworkManagerPrivate::activateConnection(const QString&, const QString&, const QString&) : Activating connection "/org/freedesktop/NetworkManager/Settings/23" on interface "/org/freedesktop/NetworkManager/Devices/1" with extra "/org/freedesktop/NetworkManager/AccessPoint/1

in /var/log/messages:

console-kit-daemon[2686]: WARNING: Couldn't read /proc/3380/environ: Failed to open file '/proc/3380/environ': No such file or directory

This doesn't look like a problem in plasma-nm, we just use NetworkManager over DBus. Do you have NetworkManager compiled with consoleKit? I think there is probably such option for that.

Yes I do.

old kde-misc/networkmanagement copes with connections, so if (as You say) plasma-nm uses the same dbus calls, I perceive there is something wrong with 
plasma-nm <--> consolekit glue.

There is no plasma-nm/networkmanagement <--> consoleKit glue, both talk directly to NetworkManager over DBus, so I'm afraid that the problem is not in plasma-nm. Are you sure you have everything installed properly? Also you can't have installed both applets together.

I have networkmanager with consolekit support and tried after removal of networkmanagement - Gentoo didn't let me install plasma-nm while networkmanagement was still installed.

I haven't tried any connection except OpenVPN as the Wifi-Link used for VPN was system-wide and started automatically by networkmanager without user interaction.

Felix, have You tried connecting to any non-system-wide network around (or even disconnecting from already connected)?

I am also on Gentoo;

(In reply to comment #7)
> Felix, have You tried connecting to any non-system-wide network around (or
> even disconnecting from already connected)?

Tried disconnecting VPN - no.
Tried disconnecting underlying Wifi - no.
Tried connecting to previously unseen but open Wifi - no.

All with the same message:
console-kit-daemon[6235]: WARNING: Couldn't read /proc/4933/environ: Failed to open file '/proc/4933/environ': No such file or directory

All I did in this case was replacing networkmanagement with plasma-nm and restarting plasma-desktop. Connecting to the currently running Wifi network worked flawlessly from networkmanagement.
Only thing I've noticed so far is an error about Avahi being unavailable during plasma-desktop restart. And yes, avahi-d* is not (system-)started on this box.

Hi,

I use Gentoo too but I do not have this problem.  Can you send me NetworkManager's log messages? They are in /var/log/daemong.log.

Please send me the version numbers of networkmanager, networkmanager-openvpn and libnm-qt you are using too.

(In reply to comment #8)
> All I did in this case was replacing networkmanagement with plasma-nm and
> restarting plasma-desktop. Connecting to the currently running Wifi network
> worked flawlessly from networkmanagement.

You also need to restart kded4 when switching between plasma-nm and networkmamangent and vice versa. Please check which network module kded4 is currently using in systemsettings -> Startup and Shutdown -> Service Manager. There should be a module called "Plasma Networkmanagement module" with "running" status in the lower section of the window (Startup Services).

I have rebooted every networkmanagement <--> plasma-nm change;

net-misc/networkmanager-0.9.8.8
net-misc/networkmanager-openvpn-0.9.8.4
net-libs/libnm-qt-0.9.8.1

I turned on debug option in consolekit, it says:
console-kit-daemon[2629]: DEBUG: CkManager: get session for unix process: 3280
console-kit-daemon[2629]: DEBUG: uid = 103
console-kit-daemon[2629]: DEBUG: pid = 2537
console-kit-daemon[2629]: WARNING: Couldn't read /proc/3280/environ: Failed to open file '/proc/3280/environ': No such file or directory
console-kit-daemon[2629]: DEBUG: CkManager: unable to lookup session for unix process: 3280

However I can see that it contacts kded4 a few times and it does get session;

Upon click Connect/Disconnect NetworkManager doesn't produce any log entries (--log-level=INFO). Which part of NetworkManager log are You interested in?

Created attachment 86230 [details]
/etc/init.d/NetworkManager restart (--log-level=INFO)

There is no mention of vpn connection attempt in your log. Can you send me the log right after you have tried to activate an openvpn connection?

as I said in the second comment of this bug I can't connect at all;
Moreover comment 8th suggests that this is not VPN related at all.

NM perfectly connects when there is a "connect automatically" network around. Any connect/disconnect action from the new plasmoid has no result.

Btw, do You use systemd?

No, I do not use systemd. You seem to have permission problems with polkit. What's the output of the command below:

emerge --nodeps -pv polkit polkit-qt consolekit

These are the packages that would be merged, in order:

[ebuild   R    ] sys-auth/polkit                                       [0.112-r1]                    USE="-examples -gtk introspection kde nls pam (-selinux) -systemd" 0 kB
[ebuild   R    ] sys-auth/polkit-qt                                    [0.103.0]                     USE="-debug -examples" 0 kB
[ebuild   R    ] sys-auth/consolekit                                   [0.4.6]                       USE="acl -debug -doc pam (policykit) (-selinux) -systemd-units {-test}" 0 kB

You can try to activate it using nmcli, it should show you some error if you don't have sufficient permissions. Unfortunately plasma-nm for kde 4 doesn't show you such information, but we added this at least to Plasma Next version.

>  activate it using nmcli,

how should I do it?

Use "nmcli connection up your_vpn_connection", you can also use tab to invoke autocompletion.

Also you may try this checklist to see you have missed something in your consolekit configuration:

https://forums.gentoo.org/viewtopic-t-858965.html

I can use nmcli to connect and disconnect with no problems

Is this issue still reproducible with the latest plasma-nm version?

Currently I use plasma-nm-5.3.2 and have no problems at all