Your message dated Thu, 10 Mar 2016 12:58:26 +0100
with message-id <[email protected]>
and subject line Bug#815140: network-manager: lib update breaks openconnect in
NM
has caused the Debian Bug report #815140,
regarding network-manager: lib update breaks openconnect in NM
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
815140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815140
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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]: <info> 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]: <info>
vpn-connection[0x236a460,9a74ca3e-439c-481b-bf98-8e05656d5a6e,"VPN",0]: Started
the VPN service, PID 10408
Feb 19 10:57:51 inaba NetworkManager[958]: <info>
vpn-connection[0x236a460,9a74ca3e-439c-481b-bf98-8e05656d5a6e,"VPN",0]: Saw the
service appear; activating connection
Feb 19 10:57:51 inaba NetworkManager[958]: <info>
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]: <info> 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]: <error> [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]: <info> keyfile: update
/etc/NetworkManager/system-connections/EMEA VPN
(9a74ca3e-439c-481b-bf98-8e05656d5a6e,"VPN")
Feb 19 10:58:19 inaba NetworkManager[958]: <info> 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
Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages network-manager depends on:
ii adduser 3.113+nmu3
ii dbus 1.10.6-1
ii init-system-helpers 1.24
ii isc-dhcp-client 4.3.3-5
ii libbluetooth3 5.36-1
ii libc6 2.21-7
ii libglib2.0-0 2.46.2-3
ii libgnutls30 3.4.9-2
ii libgudev-1.0-0 230-2
ii libmm-glib0 1.4.12-1
ii libndp0 1.4-2
ii libnewt0.52 0.52.18-2
ii libnl-3-200 3.2.27-1
ii libnm0 1.1.90-6
ii libpam-systemd 228-6
ii libpolkit-agent-1-0 0.105-14.1
ii libpolkit-gobject-1-0 0.105-14.1
ii libreadline6 6.3-8+b4
ii libsoup2.4-1 2.52.2-1
ii libsystemd0 228-6
ii libteamdctl0 1.23-1
ii libuuid1 2.27.1-3
ii lsb-base 9.20160110
ii policykit-1 0.105-14.1
ii udev 228-6
ii wpasupplicant 2.3-2.3
Versions of packages network-manager recommends:
pn crda <none>
ii dnsmasq-base 2.75-1
ii iptables 1.6.0-2
ii iputils-arping 3:20121221-5+b2
ii modemmanager 1.4.12-1
ii ppp 2.4.7-1+2
Versions of packages network-manager suggests:
pn libteam-utils <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On 19.2.2016 20:22, Mike Miller wrote:
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.
I've tried recreating the connections that were failing and they worked.
So I checked original profiles and for some reason password fields that
was supposed to be blank 'not required' were set to 'store'. Not sure if
this was caused by update itslef or something else and I don't have time
to replicate this.
As nobody seem to have encountered this and works-for-me now, closing.
--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
