Bug#815140: [Pkg-utopia-maintainers] Bug#815140: network-manager: lib update breaks openconnect in NM
On Fri, Feb 19, 2016 at 15:30:39 +0100, Michael Biebl wrote: > > Not sure whether this is a KDE issue or openconnect issue. > I use neither of them. > > Mike, can you have a look? I also don't use KDE. I've just updated to 1.1.90, and I don't see any openconnect connection problems here with gnome-shell. -- mike
Bug#815140: [Pkg-utopia-maintainers] Bug#815140: network-manager: lib update breaks openconnect in NM
Not sure whether this is a KDE issue or openconnect issue. I use neither of them. Mike, can you have a look? Am 19.02.2016 um 11:03 schrieb Matej Susta: > Package: network-manager > Version: 1.1.90-6 > Severity: important > > Dear Maintainer, > >* What led up to the situation? > In the latest upgrade I applied I got these NM related packages: > [UPGRADE] libnm-glib-vpn1:amd64 1.0.10-2+b1 -> 1.1.90-6 > [UPGRADE] libnm-glib4:amd64 1.0.10-2+b1 -> 1.1.90-6 > [UPGRADE] libnm-util2:amd64 1.0.10-2+b1 -> 1.1.90-6 > [UPGRADE] libnm0:amd64 1.0.10-2+b1 -> 1.1.90-6 > [UPGRADE] network-manager:amd64 1.0.10-2+b1 -> 1.1.90-6 > [UPGRADE] network-manager-openvpn:amd64 1.0.8-1 -> 1.1.90-3 > [UPGRADE] network-manager-pptp:amd64 1.0.8-2 -> 1.1.90-2 > [UPGRADE] network-manager-vpnc:amd64 1.0.8-1 -> 1.1.90-2 > >* What exactly did you do (or not do) that was effective (or > ineffective)? > After the upgrade connection to my corp VPN through NM UI in KDE fails. > Just to make sure I tried connecting with openconnect direcly in terminal and > everything worked so it should not be a problem with connection itself. > >* What was the outcome of this action? > After clicking OK in the username/password dialog there's usually a spinning > wheel or something on NM applet indicating that the connection is being made, > now there's nothing. > > Here's output from logs: (redacted names) > Feb 19 10:57:51 inaba NetworkManager[958]: op="connection-activate" > uuid="9a74ca3e-439c-481b-bf98-8e05656d5a6e" name="VPN" pid=9956 uid=1001 > result="success" > Feb 19 10:57:51 inaba NetworkManager[958]: > vpn-connection[0x236a460,9a74ca3e-439c-481b-bf98-8e05656d5a6e,"VPN",0]: > Started the VPN service, PID 10408 > Feb 19 10:57:51 inaba NetworkManager[958]: > vpn-connection[0x236a460,9a74ca3e-439c-481b-bf98-8e05656d5a6e,"VPN",0]: Saw > the service appear; activating connection > Feb 19 10:57:51 inaba NetworkManager[958]: > vpn-connection[0x236a460,9a74ca3e-439c-481b-bf98-8e05656d5a6e,"VPN",0]: VPN > plugin: state changed: init (1) > Feb 19 10:57:51 inaba NetworkManager[958]: (nm-openconnect-service:10408): > GLib-GObject-WARNING **: value "65" of type 'guint' is invalid or out of > range for property 'gateway-ping-timeout' of type 'guint' > Feb 19 10:57:51 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Broadcasting > identity packet > Feb 19 10:57:51 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Device > "user@computer" status changed. Reachable: false . Paired: false > Feb 19 10:57:51 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Destroying > device "user@computer" > Feb 19 10:57:51 inaba org.kde.kdeconnect[1551]: kdeconnect.core: Broadcasting > identity packet > Feb 19 10:57:51 inaba NetworkManager[958]: keyfile: update > /etc/NetworkManager/system-connections/EMEA VPN > (9a74ca3e-439c-481b-bf98-8e05656d5a6e,"VPN") > Feb 19 10:57:51 inaba NetworkManager[958]: (nm-openconnect-service:10408): > GLib-GObject-WARNING **: value "65" of type 'guint' is invalid or out of > range for property 'gateway-ping-timeout' of type 'guint' > Feb 19 10:57:51 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Broadcasting > identity packet > Feb 19 10:57:51 inaba org.kde.kdeconnect[1551]: kdeconnect.core: Broadcasting > identity packet > Feb 19 10:57:51 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Device > "user@computer" status changed. Reachable: false . Paired: false > Feb 19 10:57:51 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Destroying > device "user@computer" > Feb 19 10:58:16 inaba NetworkManager[958]: [1455875896.700300] > [vpn-manager/nm-vpn-connection.c:2266] get_secrets_cb(): > vpn-connection[0x236a460,9a74ca3e-439c-481b-bf98-8e05656d5a6e,"VPN",0]: > Failed to request VPN secrets #3: (4) No agents were available for this > request. > Feb 19 10:58:16 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Broadcasting > identity packet > Feb 19 10:58:16 inaba org.kde.kdeconnect[1551]: kdeconnect.core: Broadcasting > identity packet > Feb 19 10:58:16 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Device > "user@computer" status changed. Reachable: false . Paired: false > Feb 19 10:58:16 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Destroying > device "user@computer" > Feb 19 10:58:19 inaba NetworkManager[958]: keyfile: update > /etc/NetworkManager/system-connections/EMEA VPN > (9a74ca3e-439c-481b-bf98-8e05656d5a6e,"VPN") > Feb 19 10:58:19 inaba NetworkManager[958]: op="connection-update" > uuid="9a74ca3e-439c-481b-bf98-8e05656d5a6e" name="VPN" pid=9907 uid=1001 > result="success" > Feb 19 10:58:19 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Broadcasting > identity packet > Feb 19 10:58:19 inaba org.kde.kdeconnect[1551]: kdeconnect.core: Broadcasting > identity packet > Feb 19 10:58:19 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Device > "user@computer" status changed. Reachable: false . Paired: false > Feb 19 10:58:19 inaba org.kde.kdeconnect[9871]:
Bug#815140: network-manager: lib update breaks openconnect in NM
Package: network-manager Version: 1.1.90-6 Severity: important Dear Maintainer, * What led up to the situation? In the latest upgrade I applied I got these NM related packages: [UPGRADE] libnm-glib-vpn1:amd64 1.0.10-2+b1 -> 1.1.90-6 [UPGRADE] libnm-glib4:amd64 1.0.10-2+b1 -> 1.1.90-6 [UPGRADE] libnm-util2:amd64 1.0.10-2+b1 -> 1.1.90-6 [UPGRADE] libnm0:amd64 1.0.10-2+b1 -> 1.1.90-6 [UPGRADE] network-manager:amd64 1.0.10-2+b1 -> 1.1.90-6 [UPGRADE] network-manager-openvpn:amd64 1.0.8-1 -> 1.1.90-3 [UPGRADE] network-manager-pptp:amd64 1.0.8-2 -> 1.1.90-2 [UPGRADE] network-manager-vpnc:amd64 1.0.8-1 -> 1.1.90-2 * What exactly did you do (or not do) that was effective (or ineffective)? After the upgrade connection to my corp VPN through NM UI in KDE fails. Just to make sure I tried connecting with openconnect direcly in terminal and everything worked so it should not be a problem with connection itself. * What was the outcome of this action? After clicking OK in the username/password dialog there's usually a spinning wheel or something on NM applet indicating that the connection is being made, now there's nothing. Here's output from logs: (redacted names) Feb 19 10:57:51 inaba NetworkManager[958]: op="connection-activate" uuid="9a74ca3e-439c-481b-bf98-8e05656d5a6e" name="VPN" pid=9956 uid=1001 result="success" Feb 19 10:57:51 inaba NetworkManager[958]: vpn-connection[0x236a460,9a74ca3e-439c-481b-bf98-8e05656d5a6e,"VPN",0]: Started the VPN service, PID 10408 Feb 19 10:57:51 inaba NetworkManager[958]: vpn-connection[0x236a460,9a74ca3e-439c-481b-bf98-8e05656d5a6e,"VPN",0]: Saw the service appear; activating connection Feb 19 10:57:51 inaba NetworkManager[958]: vpn-connection[0x236a460,9a74ca3e-439c-481b-bf98-8e05656d5a6e,"VPN",0]: VPN plugin: state changed: init (1) Feb 19 10:57:51 inaba NetworkManager[958]: (nm-openconnect-service:10408): GLib-GObject-WARNING **: value "65" of type 'guint' is invalid or out of range for property 'gateway-ping-timeout' of type 'guint' Feb 19 10:57:51 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Broadcasting identity packet Feb 19 10:57:51 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Device "user@computer" status changed. Reachable: false . Paired: false Feb 19 10:57:51 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Destroying device "user@computer" Feb 19 10:57:51 inaba org.kde.kdeconnect[1551]: kdeconnect.core: Broadcasting identity packet Feb 19 10:57:51 inaba NetworkManager[958]: keyfile: update /etc/NetworkManager/system-connections/EMEA VPN (9a74ca3e-439c-481b-bf98-8e05656d5a6e,"VPN") Feb 19 10:57:51 inaba NetworkManager[958]: (nm-openconnect-service:10408): GLib-GObject-WARNING **: value "65" of type 'guint' is invalid or out of range for property 'gateway-ping-timeout' of type 'guint' Feb 19 10:57:51 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Broadcasting identity packet Feb 19 10:57:51 inaba org.kde.kdeconnect[1551]: kdeconnect.core: Broadcasting identity packet Feb 19 10:57:51 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Device "user@computer" status changed. Reachable: false . Paired: false Feb 19 10:57:51 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Destroying device "user@computer" Feb 19 10:58:16 inaba NetworkManager[958]: [1455875896.700300] [vpn-manager/nm-vpn-connection.c:2266] get_secrets_cb(): vpn-connection[0x236a460,9a74ca3e-439c-481b-bf98-8e05656d5a6e,"VPN",0]: Failed to request VPN secrets #3: (4) No agents were available for this request. Feb 19 10:58:16 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Broadcasting identity packet Feb 19 10:58:16 inaba org.kde.kdeconnect[1551]: kdeconnect.core: Broadcasting identity packet Feb 19 10:58:16 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Device "user@computer" status changed. Reachable: false . Paired: false Feb 19 10:58:16 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Destroying device "user@computer" Feb 19 10:58:19 inaba NetworkManager[958]: keyfile: update /etc/NetworkManager/system-connections/EMEA VPN (9a74ca3e-439c-481b-bf98-8e05656d5a6e,"VPN") Feb 19 10:58:19 inaba NetworkManager[958]: op="connection-update" uuid="9a74ca3e-439c-481b-bf98-8e05656d5a6e" name="VPN" pid=9907 uid=1001 result="success" Feb 19 10:58:19 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Broadcasting identity packet Feb 19 10:58:19 inaba org.kde.kdeconnect[1551]: kdeconnect.core: Broadcasting identity packet Feb 19 10:58:19 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Device "user@computer" status changed. Reachable: false . Paired: false Feb 19 10:58:19 inaba org.kde.kdeconnect[9871]: kdeconnect.core: Destroying device "user@computer" * What outcome did you expect instead? Connection works as expected. *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386
