On Tue, May 12, 2015 at 05:33:10AM CEST, Mike Miller <mtmil...@debian.org> said: > On Mon, May 11, 2015 at 18:26:20 +0200, Erwan David wrote: > > I use KDE as desktop, the problem is the same using the KDE applet, > > nmcli and nmtui. Whatever I use I get the attached window (with gateway > > name blurred) > > > > There seems to be something between the "automatically connect" and > > "view logs" line. Maybe the bug is there ? > > Thanks for the extra information. > > I have two freshly installed Debian 8 VMs, one with a GNOME desktop and > one with a KDE desktop. In the GNOME environment, I can create an > OpenConnect VPN and connect to it without an error. In the KDE > environment, I can create an OpenConnect VPN but I get the same error > that you are reporting here. I tried connecting both with and without > the KDE Wallet enabled. > > If I copy the VPN configuration from the working GNOME system to the KDE > system, it still fails to connect under KDE. > > On the KDE system, if I log in to an XFCE desktop instead, I can > successfully connect to the OpenConnect VPN that was created but failed > to connect in KDE. > > It's looking to me like this bug is in the plasma-nm package, which is > the KDE frontend for NetworkManager. It seems like plasma-nm can create > a valid VPN configuration but can't connect. > > Do you have any additional information that may still point to a bug in > network-manager-openconnect? Otherwise I will reassign to plasma-nm.
Ok, I am not very welle aware of the boundaries between packages, since I have only KDE, I think you may reassign without problem. Thanks for the help. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
