Third party VPN disconnect button is not working in reconnecting state in "Docked Mode" only
Reported by
f5client...@gmail.com,
Jul 29 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 8530.30.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.29 Safari/537.36 Platform: 8530.30.0 (Official Build) dev-channel swanky Steps to reproduce the problem: 1. Connect a external monitor 2. Close the lid so it will goes to docked mode 3. Connect to a third party VPN 4. Turn off the wifi (from system tray it will go to reconnecting state, this is a new feature from 51) 5. Try to click "disconnect" button, refer attached image What is the expected behavior? disconnect event should be sent to third party vpn What went wrong? button is clickable, but no event is sent to third party vpn Did this work before? N/A Chrome version: 53.0.2785.29 Channel: dev OS Version: 8530.30.0 Flash Version: Shockwave Flash 22.0 r0
,
Nov 1 2016
Not sure what might be going on here, I will try to repro and investigate this cycle.
,
Nov 1 2016
cc varkha@ as FYI, and applying CrOS MD label to keep this on the radar for this milestone.
,
Dec 1 2016
+cernekee@, +emaxx@ IIRC, we don't do anything special for third party VPN disconnect. The third party extension handles configuration of a VPN, but that is all. Connect / Disconnect are still handled by Shill. To investigate further, we would require: 1) A minimal set of steps to reproduce this. It seems unlikely (but not impossible) that this only occurs when an external monitor is connected. 2) A feedback report filed just after disconnect fails. Specifically we would want to look at the contents of chrome://device-log/ to confirm whether or not a disconnect event was sent to Shill (and if there were any errors reported back to Chrome), and chrome://system > netlog to see if Shill logged any errors. Thanks!
,
Dec 1 2016
This is not an exact match for the symptoms you described, but in bug 661597 we just fixed a shill crash that happened when a VPN service is in the Configuring (connecting/reconnecting) state. Suggest retesting with canary channel to see if the problem goes away. It is more likely to be another case of that bug if your 3rd party VPN does not advertise the ability to reconnect when it calls setParameters, or if the crash is seen on the initial connection.
,
Jan 17 2017
@f5client007@gmail.com could you please try reproducing the issue and submit feedback if it happens again (Alt+Shift+I)? Moving to M57 for now
,
Mar 6 2017
Without further details I'll closing this for now, but please let us know if you can submit a feedback report. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by tbuck...@chromium.org
, Nov 1 2016Components: -UI Internals>Network>VPN
Owner: steve...@chromium.org
Status: Assigned (was: Unconfirmed)