ubiquity tells me my computer name already exists on the network - hostname lookup can be slow
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Whatever ubiquity is doing when it tries to find out if a chosen hostname already exists, it's not working very well.
Ubiquity tells me that the hostname "already exists on the network" regardless of whether I'm actually ON a network, or whether that name already exists. It shows me big, warning red letters until it starts verifying my user name as I type that, at which point the hostname turns from a red warning to a green checkbox.
BUT the warning is confusing. If I didn't know better, I could easily stand there and re-enter hostnames over and over trying to get one that doesn't generate that warning. In fact, I gave it 4 different hostnames (test, edubuntu, edubuntu-64-1 and edubuntu-64) all of which caused the red "Name Exists" warning to appear, until I started typing in a different field.
This is very confusing to the users, and I imagine is not liminted to Edubuntu, but to ubiquity in general.
I'm attaching before and after screenshots to highlight this.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.9.15
ProcVersionSign
Uname: Linux 3.2.0-12-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CasperVersion: 1.302
Date: Tue Jan 31 15:45:08 2012
LiveMediaBuild: Edubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120131)
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | added: ubi-usersetup |
Changed in ubiquity (Ubuntu): | |
status: | Triaged → Incomplete |
tags: | added: quantal |
Changed in ubiquity (Ubuntu): | |
status: | Confirmed → Triaged |
tags: | added: vivid |
Changed in ubiquity (Ubuntu): | |
assignee: | Stéphane Graber (stgraber) → nobody |
tags: | added: groovy |
Screenshot showing one of the host-names I tried that generated the "name already exists on network" error