Bug 1258049

Summary:	[network] After GNOME Shell crash, causes issues with VPN password dialog
Product:	[Fedora] Fedora	Reporter:	Dave Neary <dneary>
Component:	gnome-shell	Assignee:	Owen Taylor <otaylor>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	dcbw, fmuellner, lkundrak, otaylor, rkhan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 17:42:21 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:

Description Dave Neary 2015-08-28 19:25:29 UTC

Using Fedora 22 with an X1 Atom, I have had frequent GNOME Shell clashes on wake-up from a locked screen, when using a docking station.

This causes several issues. This one is that when I try to re-connect to my employer's VPN (Red Hat, uses 2 factor auth), instead of seeing the expected VPN password dialogm the network status in the Shell menubar shows the message "authentication required..." but no password dialog appears on the screen.

It seems like that the modal dialog for the password "appears" somewhere else.

Comment 1 Jirka Klimes 2015-09-01 11:36:59 UTC

This seems like a gnome-shell applet issue that should show password dialog.
Can you connect from gnome-control-center's network panel?

Would you attach a screenshot and/or logs?

Comment 2 Fedora End Of Life 2016-07-19 17:42:21 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.