After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 726764 - Needlessly prompts (and interrupts) for password (with modal dialog) for "hidden" wifi networks at login and on intermittent network issues
Needlessly prompts (and interrupts) for password (with modal dialog) for "hid...
Status: RESOLVED INCOMPLETE
Product: gnome-shell
Classification: Core
Component: network-indicator
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2014-03-20 05:17 UTC by Jeremy Nickurak
Modified: 2019-02-27 20:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jeremy Nickurak 2014-03-20 05:17:53 UTC
On login, or in the event of any temporary disconnection (ie, passing out of range and then back in range), I get a gnome-shell modal dialog asking for a password, which already has the password filled in, so I just have to hit "ok" to get a network connection back again.

Note: I'm not sure if this is more common since upgrading from Fedora 19 to Fedora 20, and only on hidden wifi APs, although I'm not sure if that's just anecdotal.

In my case, it's for an "accessible to all users" connection in NetworkManager.

Per bug #388434:

> Milan Bouchet-Valat [developer] 2014-01-03 20:28:47 UTC
> (In reply to comment #31)
> > I should note that this problem is certainly not limited to Evolution.
> > Gnome-shell/NetworkManager will also spotonaneously pop up a password dialog
> > in some situations of intermittent connection problems. (Just hit this a minute
> > ago on Fedora 19, gnome-shell 3.8.4.
>
> Yeah, but please also file a bug. Even if password dialogs weren't modal,
> popping them out of the blue is never a good design.
Comment 1 Jeremy Nickurak 2014-03-20 05:20:39 UTC
I'll also note that I'm seeing this on two totally different machines, one being a HP2140 netbook (with a broadcom BCM4312 wifi chip) and a Lenovo W530 (with a "Intel Corporation Centrino Advanced-N 6205").
Comment 2 Dan Winship 2014-03-20 12:13:38 UTC
The shell controls whether a dialog is or is not displayed. The bug that's actually for this issue (dialogs popping up at random times) is 693674, so I'm duping this to that, even though that bug has already been dup'ed to a slightly-unrelated bug that just happens to have a patch that also fixes this problem.

*** This bug has been marked as a duplicate of bug 693674 ***
Comment 3 Jeremy Nickurak 2014-03-20 13:46:21 UTC
Re-opening.

I'd like this to track one specific bug: the fact that it doesn't just connect automatically when it has all the information to successfully do so.

The fact that it pops up a modal dialog out of the blue is a side-effect of that. A genuine connection failure should pop something up out of the blue, like a notification, but not a modal dialog. That's a separate issue. Whether it's a duplicate of one thing or another isn't actually part of the root issue here.
Comment 4 Allan Day 2014-11-26 13:27:05 UTC
I have a docking station with a wired network connection. While I am using it, I regularly get prefilled Wi-Fi password dialogs popping up (this is GNOME 3.14/Fedora 21).

My password is known and correct, and my laptop has no problems connecting when I am in other parts of the house. I suspect that it is because the Wi-Fi signal is weak where the docking station is.

As per comment 3, I've filed bug 740750 to cover the use of the modal password dialog, so this issue can focus on the actual connection issue itself.
Comment 5 Michael Catanzaro 2017-06-27 23:59:06 UTC
I think this behavior has changed over the past three years. I don't think this happens anymore. Is that right? Are you still experiencing this problem?
Comment 6 Florian Müllner 2019-02-27 20:53:28 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!