Ubuntu
ubiquity package

[Feature Request] Add Wireless configuration screen to oem-config if wireless is available

Bug #371444 reported by Jerone Young
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
Undecided
Unassigned
Maverick
Fix Released
Undecided
Unassigned

Bug Description

This is a requests to add a wireless network selection screen to oem-config if wireless is avaliable.

This would set the wireless settings for the newly created user that is created during the use of oem-config. If no wireless is available then don't show the wireless selection screen. Also feature a skip button if users do not want to setup wireless.

It has been reported that many users have a hard time figuring out how to connect to their home wireless network. By having a screen in oem-config it would greatly help with usablity. This is a feature that is in newer versions of competing operation systems during the initial setup by users.

See original description
Jerone Young (jerone)
visibility: private → public
Colin Watson (cjwatson)
affects: oem-config (Ubuntu) → ubiquity (Ubuntu)
Colin Watson (cjwatson)
tags: added: oem-config
Revision history for this message
Brent Fox (brent-s-fox) wrote :

Jerone, I'm curious to see if this is something that OEM Engineering could code up.

Changed in dell:
status: New → Triaged
Revision history for this message
Jerone Young (jerone) wrote : Re: [Bug 371444] Re: [Feature Request] Add Wireless configuration screen to oem-config if wireless is available

It was in the platform teams blue print for oem-config for Karmic:
https://wiki.ubuntu.com/FoundationsTeam/Specs/KarmicOEMConfigImprovements

Though it looks like it wasn't done. I think with the new plugin system
it will make it much easier to pull off.

Brent Fox wrote:
> Jerone, I'm curious to see if this is something that OEM Engineering
> could code up.
>
> ** Changed in: dell
> Status: New => Triaged
>
>

Revision history for this message
Brent Fox (brent-s-fox) wrote :

Assigning to Mike Terry based on Pat McGowan's input.

Changed in ubiquity (Ubuntu):
assignee: nobody → Michael Terry (mterry)
Revision history for this message
Brent Fox (brent-s-fox) wrote :

Jerone, this is a great test case to try out our new feature request justification document we created in the sprint. Can you put that together? Then we'll push this for Lucid.

Revision history for this message
Michael Terry (mterry) wrote :

Just FYI, I owned the spec with this for Karmic. This got delayed in part because it was so time-consuming.

Part of the problem is that you need to create a new frontend for NetworkManager and embed it. The existing frontends do not lend themselves to being incorporated as widgets (GNOME frontend requires panel for example and isn't written as a library).

So it's doable, just not a small project. I'd gladly do it (sounds fun), but would need time.

Tony Espy (awe)
Changed in dell:
importance: Undecided → Wishlist
status: Triaged → Confirmed
Revision history for this message
Tony Espy (awe) wrote :

Per discussion during our engineering meeting this morning, changing the Status in the Dell task to WontFix, as this project is used to track non-public hardware enablement work.

Changed in dell:
status: Confirmed → Won't Fix
nUboon2Age (nuboon2age)
description: updated
nUboon2Age (nuboon2age)
description: updated
papukaija (papukaija)
tags: added: maverick
tags: added: wishlist
Revision history for this message
Michael Terry (mterry) wrote :

10.10 had NetworkManager in the panel during install. (Not done by me)

Changed in ubiquity (Ubuntu Maverick):
assignee: Michael Terry (mterry) → nobody
status: New → Fix Released
Revision history for this message
Michael Terry (mterry) wrote :

Same. (10.10 had it)

Changed in ubiquity (Ubuntu):
assignee: Michael Terry (mterry) → nobody
status: New → Fix Released
Timothy R. Chavez (timrchavez)
Changed in somerville:
importance: Undecided → Wishlist
status: New → Won't Fix
no longer affects: dell
Revision history for this message
Timothy R. Chavez (timrchavez) wrote :

The bug task for the somerville project has been removed by an automated script. This bug has been cloned on that project and is available here: https://bugs.launchpad.net/bugs/1305454

no longer affects: somerville
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.