Bug 357068

Summary: VPN: kwallet dialog when VPN connection shuts down
Product: [Plasma] plasmashell Reporter: arne anka <kde-bugs>
Component: Networks widgetAssignee: Jan Grulich <jgrulich>
Status: RESOLVED WORKSFORME    
Severity: minor CC: jgrulich, lukas
Priority: NOR    
Version First Reported In: master   
Target Milestone: 1.0   
Platform: Debian unstable   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: nmcli connection show
journalctl

Description arne anka 2015-12-22 21:02:26 UTC
i got a configuration that creates a VPN to a FritzBox VPN. due a known bug in AVM's VPN implementation the connection shuts down after about an hour. 

i can connect to that VPN without any password request, but when the VPN shuts down after almost one hour, i get two kwallet dialogs overlapping each other.

as far as i can tell, this is due to NM (either the the networkmanager or the KDE integration) trying to re-establish the connection. but i cannot really understand why all of a sudden now the KWallet gets involved, let alone twice without even waiting for my input (whatever that would be since i didn't even set a password to KWallet).

if indeed this is due to NM trying to reconnect, then this useful feature is broken and made useless by the erroneous KWallet involvement.
Comment 1 Jan Grulich 2015-12-28 13:46:08 UTC
Please provide information as described here: https://techbase.kde.org/Projects/Solid/Plasma-nm#Plasma-nm_doesn.27t_remember_my_password

It's possible that NM assumes that you got disconnected because of missing password and then asks for it through our secret agent so I need to know what's going on.
Comment 2 arne anka 2016-01-17 15:47:53 UTC
Created attachment 96697 [details]
nmcli connection show
Comment 3 arne anka 2016-01-17 15:48:27 UTC
Created attachment 96698 [details]
journalctl
Comment 4 arne anka 2016-01-17 15:48:43 UTC
$ if `qdbus org.kde.kded5 /kded org.kde.kded5.loadedModules | grep networkmanagement > /dev/null`; then echo "running"; else echo "not running"; fi
running

kded5:
plasma-nm: virtual NMVariantMapMap SecretAgent::GetSecrets(const NMVariantMapMap&, const QDBusObjectPath&, const QString&, const QStringList&, uint)
plasma-nm: Path: "/org/freedesktop/NetworkManager/Settings/0"
plasma-nm: Setting name: "vpn"
plasma-nm: Hints: ()
plasma-nm: Flags: 4
Pass a valid window to KWallet::Wallet::openWallet().
plasma-nm: bool SecretAgent::processGetSecrets(SecretsRequest&) const Waiting for the wallet to open
plasma-nm: virtual void SecretAgent::SaveSecrets(const NMVariantMapMap&, const QDBusObjectPath&)
plasma-nm: Path: "/org/freedesktop/NetworkManager/Settings/0"
Pass a valid window to KWallet::Wallet::openWallet().
plasma-nm: bool SecretAgent::processDeleteSecrets(SecretsRequest&) const Waiting for the wallet to open
plasma-nm: virtual NMVariantMapMap SecretAgent::GetSecrets(const NMVariantMapMap&, const QDBusObjectPath&, const QString&, const QStringList&, uint)
plasma-nm: Path: "/org/freedesktop/NetworkManager/Settings/0"
plasma-nm: Setting name: "vpn"
plasma-nm: Hints: ()
plasma-nm: Flags: 4
plasma-nm: virtual void SecretAgent::SaveSecrets(const NMVariantMapMap&, const QDBusObjectPath&)
plasma-nm: Path: "/org/freedesktop/NetworkManager/Settings/0"
Comment 5 Jan Grulich 2016-02-04 08:15:31 UTC
Hi, sorry for late response. According to the output from kded5 it looks that NM requests secrets based on user request (which doesn't make sense) unless this is reported when you were trying to edit this connection, but if it's due to re-activation then there is something wrong apparently. Also, your secrets are marked to be stored in NetworkManager even when there is no password involved/required  so NM shouldn't ask at all. Btw. both windows are requested by our secret probably as I see more requests to manipulate with secrets.

What is your NetworkManager version? I don't see any related info in the NM log, but I think this problem is NM related.
Comment 6 arne anka 2016-02-06 21:54:51 UTC
$ dpkg -s network-manager
Package: network-manager
Status: install ok installed
Priority: optional
Section: net
Installed-Size: 14090
Maintainer: Utopia Maintenance Team <pkg-utopia-maintainers@lists.alioth.debian.org>
Architecture: amd64
Version: 1.1.90-5
Depends: libbluetooth3 (>= 4.91), libc6 (>= 2.17), libglib2.0-0 (>= 2.39.4), libgnutls30 (>= 3.4.0), libgudev-1.0-0 (>= 165), libmm-glib0 (>= 1.0.0), libndp0 (>= 1.2), libnewt0.52, libnl-3-200 (>= 3.2.7), libnm0 (>= 1.1.90), libpolkit-agent-1-0 (>= 0.99), libpolkit-gobject-1-0 (>= 0.104), libreadline6 (>= 6.0), libsoup2.4-1 (>= 2.40), libsystemd0, libteamdctl0 (>= 1.9), libuuid1 (>= 2.16), init-system-helpers (>= 1.18~), lsb-base (>= 3.2-14), wpasupplicant (>= 0.7.3-1), dbus (>= 1.1.2), udev, adduser, isc-dhcp-client (>= 4.1.1-P1-4), libpam-systemd, policykit-1
Recommends: ppp, dnsmasq-base, iptables, modemmanager, crda, iputils-arping
Suggests: libteam-utils
Breaks: ppp (>= 2.4.7-2~), ppp (<< 2.4.7-1+~)
Conffiles:
 /etc/NetworkManager/NetworkManager.conf 914f22205f2ed4d4bc84f3682ecd3153
 /etc/NetworkManager/dispatcher.d/01ifupdown 299819a8e64f00a1edbdfc99d05a8594
 /etc/dbus-1/system.d/nm-dispatcher.conf 5711a76c31a3763750fe2c331741f679
 /etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf 293db8ed3188eb8b5b164571d753bd60
 /etc/init.d/network-manager 59b97edb8cc5f8db9882118fbf102a88
Description: network management framework (daemon and userspace tools)
 NetworkManager is a system network service that manages your network devices
 and connections, attempting to keep active network connectivity when
 available. It manages ethernet, WiFi, mobile broadband (WWAN), and PPPoE
 devices, and provides VPN integration with a variety of different VPN
 services.
 .
 This package provides the userspace daemons and a command line interface to
 interact with NetworkManager.
 .
 Optional dependencies:
  * ppp: Required for establishing dial-up connections (e.g. via GSM).
  * dnsmasq-base/iptables: Required for creating Ad-hoc connections and
    connection sharing.
    address configuration.
  * libteam-utils: Network Team driver allows multiple network interfaces to be
    teamed together and act like a single one. This process is called "ethernet
    bonding", "channel teaming" or "link aggregation".
Homepage: https://wiki.gnome.org/Projects/NetworkManager
Comment 7 arne anka 2016-02-06 21:55:27 UTC
$ dpkg -s network-manager-vpnc
Package: network-manager-vpnc
Status: install ok installed
Priority: optional
Section: net
Installed-Size: 82
Maintainer: Utopia Maintenance Team <pkg-utopia-maintainers@lists.alioth.debian.org>
Architecture: amd64
Version: 1.1.90-2
Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.37.3), libnm0 (>= 1.1.90), vpnc
Conffiles:
 /etc/NetworkManager/VPN/nm-vpnc-service.name 7f51a018f71365892e1a374df3942c93
 /etc/dbus-1/system.d/nm-vpnc-service.conf fd1972dab1966261b4cc7aaa274d3e84
Description: network management framework (VPNC plugin core)
 NetworkManager is a system network service that manages your network devices
 and connections, attempting to keep active network connectivity when
 available. It manages ethernet, WiFi, mobile broadband (WWAN), and PPPoE
 devices, and provides VPN integration with a variety of different VPN
 services.
 .
 This package provides a VPN plugin for vpnc, providing easy access to Cisco
 Concentrator based VPN's.
Homepage: https://www.gnome.org/projects/NetworkManager/
Comment 8 Jan Grulich 2017-03-22 11:02:10 UTC
Cannot reproduce. Given the issue is pretty old and many things has changed since then I'm closing now this bug. Re-open it please if you still have this problem with latest Plasma release.
Comment 9 Ben Cooksley 2024-12-23 18:25:46 UTC
Bulk transfer as requested in T17796