Summary: | Unable to recognize existing vpn connection on logging in. | ||
---|---|---|---|
Product: | [Unmaintained] Network Management | Reporter: | Yichao Yu <yyc1992> |
Component: | Plasma Widget | Assignee: | Sebastian Kügler <sebas> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | lamarque, wstephenson |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 0.9.0.3 | |
Sentry Crash Report: |
Description
Yichao Yu
2012-06-09 00:34:06 UTC
Which Plasma NM version do you use? You can see the version in "Manage Connections" -> "Other". Git commit 2a9f66ea262e0c020a1edb00c2ed430ba933eb03 by Lamarque V. Souza. Committed on 12/06/2012 at 18:42. Pushed by lvsouza into branch 'master'. Fix connection list if the plasmoid is launched before the kded module. Related: bug 301666 M +15 -13 applet/networkmanager.cpp M +6 -0 libs/client/remoteactivatablelist.cpp http://commits.kde.org/networkmanagement/2a9f66ea262e0c020a1edb00c2ed430ba933eb03 ~ Just in case u still need my version. It's 0.9.0.2 (nm09 20120507) from the 4.8.80 package of archlinux. Git commit bbb8431d5664e64b5816052ab2a60a5fcfdd0901 by Lamarque V. Souza. Committed on 12/06/2012 at 18:42. Pushed by lvsouza into branch 'nm09'. Fix connection list if the plasmoid is launched before the kded module. Related: bug 301666 M +16 -13 applet/networkmanager.cpp M +6 -0 libs/client/remoteactivatablelist.cpp M +1 -1 plasma_nm_version.h http://commits.kde.org/networkmanagement/bbb8431d5664e64b5816052ab2a60a5fcfdd0901 Can you check if Plasma NM 0.9.0.3 fixes this problem for you? Sorry I am not able to use 0.9.0.3 due to a problem on [openconnect support](https://bugs.archlinux.org/task/30398) (plasma-nm 0.9.0.3 with my current version of nm support neither openconnect 1:3.18 or 1:4.00) Well, I have teste it here and the problem seems fixed. Reopen the bug if it happens again. THX, will test when new networkmanager release is available. (In reply to comment #7) > Well, I have teste it here and the problem seems fixed. Reopen the bug if it > happens again. |