Bug 751139 - Anaconda doesn't ask for wifi password
Summary: Anaconda doesn't ask for wifi password
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Radek Vykydal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: https://fedoraproject.org/wiki/Common...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-03 16:17 UTC by Kamil Páral
Modified: 2013-06-18 16:53 UTC (History)
7 users (show)

Fixed In Version: anaconda-19.30.8-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-18 16:53:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kamil Páral 2011-11-03 16:17:43 UTC
Description of problem:
When installing from network repositories over wifi connection, anaconda doesn't ask for password automatically. You have to enter it inside nm-connection-editor that is opened after you select target wifi network. That is very counter-intuitive.

Anaconda should ask for wifi password.

Version-Release number of selected component (if applicable):
anaconda 16.25

How reproducible:
always

Steps to Reproduce:
1. install from netinst
2. select wifi network to connect to
3. you have to enter the password inside nm-connection-editor dialog that pops up, otherwise you can't join the network

Comment 1 Adam Williamson 2011-11-03 16:47:07 UTC
ah, this is why I couldn't reproduce: I actually did it that way first time. but yeah, it's a pretty unintuitive workflow.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 Radek Vykydal 2011-11-04 09:34:23 UTC
Yes, I was struggling quite a lot with that, and we will definitely address this in the new Anaconda UI. Generally we are missing in present Anaconda UI things that nm-applet offers (integration of which in present UI is very difficult).

For details see
https://fedoraproject.org/wiki/Anaconda/Network#Missing_GUI_pieces
https://fedoraproject.org/wiki/Anaconda/Network#Anaconda_UX_redesign

Comment 3 John Gotts 2012-12-17 20:07:31 UTC
One thing I would like to see fixed in the wireless user interface is a way to turn off the primary but keep the secondary enabled.

Why would you want this? My laptop is 802.11bgn, my access point is 802.11a, and I had to purchase a USB dongle that has 802.11a in order to use my access point. This issue will become hot when the next wireless standard becomes common (802.11??) and people want to start using it while their laptops only support 802.11n. It's somewhat worse for me because the laptop hardware will not connect to my access point in any way, even via some degraded mode. I have to use 802.11a.

What happens is that when you try to turn off the primary, it hardware disables it and tells you the secondary is disabled, although this can't be true. So you always have to enable all wireless interfaces or else you can use no wireless at all.

When you're connected via the secondary, if you have an access point in range of of the primary (which in the Detroit suburbs is always), the user interface nags you with countless dialogs. You have to dismiss them over and over, and every dialog is system modal, locking you out of whatever you were doing. It will interrupt any and all applications, every couple of minutes, stacking up multiple dialogs you have to dismiss. Sometimes there are so many dialogs you have to dismiss that it will cause some part of GNOME to crash.

You'd think that I could connect the primary to some 802.11bgn network, but there are none in range that are not password protected. Even if I did that, I would not want to actually use that connection, as I'm paying for the full bandwidth via my 802.11a access point.

Comment 4 Fedora End Of Life 2013-01-16 17:29:51 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-13 22:15:02 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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

Comment 6 Kamil Páral 2013-02-14 10:22:10 UTC
Still the same issue even in NewUI in Fedora 18 anaconda. Changing version to rawhide.

Comment 7 Fedora End Of Life 2013-04-03 19:43:47 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 8 Kamil Páral 2013-06-18 13:11:57 UTC
I verified this to be working with anaconda-19.30.8-1. Thanks.

Comment 9 Adam Williamson 2013-06-18 16:53:25 UTC
19.30.8 is stable already, so closing.


Note You need to log in before you can comment on or make changes to this bug.