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 625757 - (Mobile Broadband) Asks for password when no password necessary
(Mobile Broadband) Asks for password when no password necessary
Status: RESOLVED INVALID
Product: NetworkManager
Classification: Platform
Component: general
0.8.x
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2010-08-01 12:49 UTC by Matthew East
Modified: 2010-08-03 15:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthew East 2010-08-01 12:49:40 UTC
From https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/518480

"Approximately 40% of the times where I boot my machine and load my Desktop, Network Manager throws up a password box that says "A password is required to connect to "Vodafone Contract" HUAWEI Technologies HUAWEI Mobile" (see screenshot). However, it does not accept my password. There appears to be no pattern to this. This happens when no changes have been made to my system - no recently installed updates etc. On one occasion it didn't happen for as long as five days, on another occasion it happened on four reboots in a row - it really does seem completely random. The only option is to open network-manager-applet, delete my mobile broadband connection settings, then run the connection wizard again to re-apply them from the beginning."

I've experienced this issue myself, NetworkManager asks me for a password and if I simply press enter with a blank field, eventually it will work after doing so a few times.
Comment 1 Dan Williams 2010-08-02 19:41:29 UTC
Do you have a GRPS username entered in the connection editor for that connection?  If so, try removing that.
Comment 2 Matthew East 2010-08-03 15:55:40 UTC
Yes, the problem appears to have been with the connection settings. I'm not sure why they went wrong but they are working now.

The original Ubuntu bug report may have been from a different problem so I'll let the original reporter reopen the bug if appropriate.