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 671475 - Can't configure wireless without trying to connect
Can't configure wireless without trying to connect
Status: RESOLVED DUPLICATE of bug 665874
Product: gnome-control-center
Classification: Core
Component: Network
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-03-06 15:09 UTC by Michael Clerx
Modified: 2012-04-19 22:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Clerx 2012-03-06 15:09:09 UTC
The current network settings panel in gnome3 has some major usability issues.
To configure my wireless, I need to 
  1. Enable it
  -> The system now starts trying to connect using my old, flawed settings
  2. I can now hit "configure"
  3. While I'm configuring, I get asked for a password
  4. I go back to configuring
  5. Meanwhile, the connection fails, I click cancel to ignore the new password request.
  6. A second, differently styled dialog appears requesting my password
  7. I cancel this too and try to finish configuring.
  8. Since the connection failed, the network I selected is unselected and the configure option disappears again.
  (9. No feedback is given on why the connection failed, at which point it failed, what is was doing etc, but this is a different issue)

Long story short, I need to be able to select a network to configure _without_ trying to connect to it. I know it won't work with the current settings, that's why I'm trying to configure it.
For the use case where you know the right settings the first time the UI works fine, for the scenario where you need to tweak your settings it fails miserably.

Sorry if my frustrations shine through to clearly on this issue, I would sincerely appreciate any effort towards improving the situation.
Comment 1 Milan Bouchet-Valat 2012-03-07 10:00:13 UTC
(Just in case ;-)
Comment 2 Milan Bouchet-Valat 2012-04-19 22:25:37 UTC
I knew I had already seen another report about that...

*** This bug has been marked as a duplicate of bug 665874 ***