Bug 359746 - VPN: Applet remains spinning upon established connection
Summary: VPN: Applet remains spinning upon established connection
Status: RESOLVED DUPLICATE of bug 352326
Alias: None
Product: plasma-nm
Classification: Plasma
Component: applet (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-24 11:45 UTC by Stephan Mueller
Modified: 2016-02-29 12:12 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Mueller 2016-02-24 11:45:27 UTC
When using a VPN and triggering a VPN connection, the applet starts spinning for the connection attempt. During that time the "authorization required" is displayed.

When the connection is successfully established (i.e. I can use the VPN) and a notification is displayed that the connection is established, the applet still remains spinning with "authorization required". The issue is now that this spinning burns about 1 CPU core and drains battery fast.

Note, this applies irrespectively of the type of VPN (I use OpenVPN and vpnc).

Note, this behavior is not seen immediately. I.e. when you create a new user with a clean KDE configuration, the VPN connection behaves nicely and the spinning stops when the connection is there.

But after a couple of days without changing anything in the VPN configs (at least I did not noticeably change anything), the described behavior appears again.

Reproducible: Always
Comment 1 Jan Grulich 2016-02-24 11:59:09 UTC

*** This bug has been marked as a duplicate of bug 352326 ***
Comment 2 Stephan Mueller 2016-02-24 13:07:06 UTC
Bug 352326 references that the Fedora package kf5-networkmanager-qt-5.18.0-2 fixes the bug.

I use Fedora 23 with kf5-networkmanager-qt-5.19.0-1.fc23.x86_64 and see the problem.
Comment 3 Jan Grulich 2016-02-24 13:30:06 UTC
Ok, could you provide information from here https://techbase.kde.org/Projects/Solid/Plasma-nm#My_connection_in_the_applet_shows_wrong_information?
Comment 4 Stephan Mueller 2016-02-24 13:51:38 UTC
if `qdbus org.kde.kded5 /kded org.kde.kded5.loadedModules | grep networkmanagement > /dev/null`; then echo "running"; else echo "not running"; fi
running



dbus-monitor --system "type='signal',sender='org.freedesktop.NetworkManager'"dbus-monitor: unable to enable new-style monitoring: org.freedesktop.DBus.Error.AccessDenied: "Rejected send message, 1 matched rules; type="method_call", sender=":1.80" (uid=1000 pid=8396 comm="dbus-monitor --system type='signal',sender='org.fr") interface="org.freedesktop.DBus.Monitoring" member="BecomeMonitor" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus)". Falling back to eavesdropping.
signal time=1456321482.894590 sender=org.freedesktop.DBus -> destination=:1.80 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.80"
signal time=1456321486.301909 sender=:1.9 -> destination=(null destination) serial=33816 path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; member=PropertiesChanged
   array [
      dict entry(
         string "Connectivity"
         variant             uint32 3
      )
   ]
signal time=1456321495.842268 sender=:1.9 -> destination=(null destination) serial=33817 path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; member=PropertiesChanged
   array [
      dict entry(
         string "Connectivity"
         variant             uint32 3
      )
   ]
signal time=1456321500.236990 sender=:1.9 -> destination=(null destination) serial=33818 path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; member=PropertiesChanged
   array [
      dict entry(
         string "Connectivity"
         variant             uint32 3
      )
   ]


Regarding the logs: there is a lot of private information in those logs which I do not want to post publicly. Is there anything in particular you are interested in? Here is the last part of the log which contains some strangeness (the German part means: connection failed: network is not reachable):

<info>  connectivity: check for uri 'http://fedoraproject.org/static/hotspot.txt' failed with 'Verbindung ist gescheitert:Das Netzwerk ist nicht erreichbar'
<info>  NetworkManager state is now CONNECTED_SITE
<info>  connectivity: check for uri 'http://fedoraproject.org/static/hotspot.txt' failed with 'Verbindung ist gescheitert:Das Netzwerk ist nicht erreichbar'
<info>  connectivity: check for uri 'http://fedoraproject.org/static/hotspot.txt' failed with 'Verbindung ist gescheitert:Das Netzwerk ist nicht erreichbar'
<info>  connectivity: check for uri 'http://fedoraproject.org/static/hotspot.txt' failed with 'Verbindung ist gescheitert:Das Netzwerk ist nicht erreichbar'
<info>  connectivity: check for uri 'http://fedoraproject.org/static/hotspot.txt' failed with 'Verbindung ist gescheitert:Das Netzwerk ist nicht erreichbar'
Comment 5 Jan Grulich 2016-02-29 12:12:37 UTC

*** This bug has been marked as a duplicate of bug 352326 ***