Summary: | The icon doesn't correctly show the vpn status | ||
---|---|---|---|
Product: | [Plasma] plasma-nm | Reporter: | Weng Xuetian <wengxt> |
Component: | applet | Assignee: | Jan Grulich <jgrulich> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | carsten, clay, fabien.goglio, jgrulich, kaj, lasse.liehu, lukas, rkhozinov |
Priority: | NOR | ||
Version: | 0.9.3.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/plasma-nm/932a9b17b72a0eed6ff7f619c6603644de92b8da | Version Fixed In: | 0.9.3.2 |
Sentry Crash Report: |
Description
Weng Xuetian
2013-10-17 20:31:05 UTC
There is a lock overlay when you are connected to VPN, but in your case there is something wrong. Can you please enable plasma-nm in kdebugdialog (enable everything just for sure) and reproduce again your problem? Then send me here the content of .xsession-error. *** Bug 326304 has been marked as a duplicate of this bug. *** What distribution and version of NetworkManager do you use? I use Kubuntu 13.10 so KDE 4.11.2 and the new plasma-nm. I have the same problem with a VPN connection using PPTP. Distribution is Arch Linux with the following package versions: networkmanager 0.9.8.8-1 networkmanager-pptp 0.9.8.4-1 libnm-qt 0.9.0.1-1 kdeplasma-applets-plasma-nm 0.9.3.1-2 Enabled all plasma-nm options in kdebugdialog, but didn't get anything in .xsession-errors (the file doesn't exist). *** Bug 326014 has been marked as a duplicate of this bug. *** Git commit 932a9b17b72a0eed6ff7f619c6603644de92b8da by Jan Grulich. Committed on 20/10/2013 at 17:54. Pushed by grulich into branch 'master'. Fix the icon when you are connected to VPN M +17 -7 declarative-plugins/applet/connectionicon.cpp http://commits.kde.org/plasma-nm/932a9b17b72a0eed6ff7f619c6603644de92b8da Can someone please test the fix above? Thanks *** Bug 326358 has been marked as a duplicate of this bug. *** Works fine for me after the fix *** Bug 326403 has been marked as a duplicate of this bug. *** *** Bug 326401 has been marked as a duplicate of this bug. *** The fix solves the bug for me. |