Bug 326919 - OpenConnect VPN won't connect after upgrading to Kubuntu 13.10
Summary: OpenConnect VPN won't connect after upgrading to Kubuntu 13.10
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Networks widget (show other bugs)
Version: master
Platform: Kubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-31 01:02 UTC by Leon Maurer
Modified: 2024-12-23 18:25 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
The KDE VPN login winow (48.22 KB, image/png)
2013-10-31 01:06 UTC, Leon Maurer 		Details
The Cisco VPN connect window (45.23 KB, image/png)
2013-10-31 01:07 UTC, Leon Maurer 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Leon Maurer 2013-10-31 01:02:35 UTC 
I can no longer connect to my University's VPN -- which uses OpenConnect -- since upgrading to Kubuntu 13.10. The VPN is still listed as a connection, but it no longer works. When I enter my username and password (on a window titled "VPN secrets (openconnect) - KDE Daemon") and try to log on, I get a message stating "Login failed."

Cisco's AnyConnect client still connects without issue; the VPN server works, and my login information is correct.

Reproducible: Always
Comment 1 Leon Maurer 2013-10-31 01:06:47 UTC 
Created attachment 83244 [details]
The KDE VPN login winow
Comment 2 Leon Maurer 2013-10-31 01:07:10 UTC 
Created attachment 83245 [details]
The Cisco VPN connect window
Comment 3 Leon Maurer 2013-10-31 01:09:01 UTC 
I should add that the KDE VPN connect window asks for three things: group, username, and password. I recall I previously needed to select the network first. This option is still visible in Cisco's client -- the "Connect to" option, which has three options.
Comment 4 Jan Grulich 2014-12-04 09:12:57 UTC 
Is it still reproducible? Is there any error in NetworkManager log after you fail to activate your OpenConnect connection?
Comment 5 Leon Maurer 2014-12-04 15:17:04 UTC 
I'll test it if I get a chance. (I've been using the Cisco client instead.)
-Leon
Comment 6 Christoph Feck 2015-01-14 16:21:12 UTC 
Leon, any update?
Comment 7 Jan Grulich 2015-02-13 13:43:42 UTC 
Ping? Can I close this one?
Comment 8 Leon Maurer 2015-02-16 19:51:50 UTC 
It works for me. (The "Automatically start connecting next time" checkbox may not be working though.) Thanks for taking care of this!
Comment 9 Jan Grulich 2015-02-17 08:22:13 UTC 
The "Automatically start connecting next time" checkbox is also already fixed, but it is not released yet and will be in plasma-nm 0.9.3.6.
Comment 10 Ben Cooksley 2024-12-23 18:25:51 UTC 
Bulk transfer as requested in T17796