Bug 1272023
Summary: | vpn password request still visible after timeout (3 mins) | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Vladimir Benes <vbenes> | ||||
Component: | NetworkManager | Assignee: | Lubomir Rintel <lrintel> | ||||
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 7.2 | CC: | bgalvani, dcbw, jklimes, lmiksik, lrintel, rkhan, thaller | ||||
Target Milestone: | rc | Keywords: | Regression | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | NetworkManager-1.0.6-25.el7 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-11-19 11:06:26 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Vladimir Benes
2015-10-15 09:57:54 UTC
Increasing timeout to 3 minutes was an intentional change [1]. Closing the dialog is gnome-shell responsibility. I am not sure whether the timeout is meaningfully signalled to clients, though. [1] http://pkgs.devel.redhat.com/cgit/rpms/NetworkManager/commit/?h=rhel-7.2&id=b839d6f10752cad2d629d7cbadcf7a243db39fb2 Created attachment 1084850 [details]
Suggested fix
This indeed is a cosmetic issue; I don't think it should be a blocker. nm-1-0: 2419588 libnm-glib,vpn-plugin: remove old connect timer when adding new one 0a95f00 agent-manager: cancel secrets requests on an error master: a5feb44 libnm,vpn-service-plugin: remove old connect timer when adding new one 842889b libnm-glib,vpn-plugin: remove old connect timer when adding new one 5d1cac8 agent-manager: cancel secrets requests on an error 1. timeout was tested 2. 3 times bad password and connecting with correct one 3. correct connecting and persistence all is working right Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-2315.html |