Ubiquity fails to detect active internet connection

Bug #1008707 reported by Nicholas Skaggs on 2012-06-04
26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Low
Unassigned

Bug Description

Installer shows active wired connection, but shows an 'X' under connected to the internet and disallows installing updates as part of the connection

<info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete.
<info> (eth0): IP6 addrconf timed out or failed.

ProblemType: BugDistroRelease: Ubuntu 12.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 3.4.0-3.8-generic 3.4.0
Uname: Linux 3.4.0-3-generic i686
ApportVersion: 2.1.1-0ubuntu2
Architecture: i386
Date: Mon Jun 4 16:13:19 2012
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash --
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120604.2)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bashSourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Nicholas Skaggs (nskaggs) wrote :
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1008707

tags: added: iso-testing
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report.

I duplicated your other reports because they are all caused by a non-working network connection.

The following message is displayed in syslog
Jun 4 15:29:01 ubuntu ntpdate[2249]: Can't find host ntp.ubuntu.com: Name or service not known (-2)
[...]
Jun 4 15:47:02 ubuntu ubiquity[2834]: Geoname lookup for "New York" failed: 2 Cannot resolve hostname (geoname-lookup.ubuntu.com)
[...]
Jun 4 15:52:21 ubuntu in-target: Err http://us.archive.ubuntu.com quantal Release.gpg
Jun 4 15:52:21 ubuntu in-target: Something wicked happened resolving 'us.archive.ubuntu.com:http' (-5 - No address associated with hostname)
Jun 4 15:52:21 ubuntu in-target: Err http://us.archive.ubuntu.com quantal-updates Release.gpg
Jun 4 15:52:21 ubuntu in-target: Something wicked happened resolving 'us.archive.ubuntu.com:http' (-5 - No address associated with hostname)

Your system is unable to do DNS resolution. According to the log, the nameserver is set to 10.0.2.2#53
Is this nameserver working properly on your network ?

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Nicholas Skaggs (nskaggs) wrote :

It's seemingly not, my alt images are having the same issue -- I *thought* I wouldn't get full language support if the installer doesn't see my active network connection, interesting all the other issues occur for the same reason. I will investigate -- post-install the network does work, and network manager shows the connection.

Fabio Marconi (fabiomarconi) wrote :

Hallo
Have you already tried to uncheck and recheck `Enable Networking` in network-manager icon or to restart the modem/router ?
Thanks
Fabio
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

description: updated
description: updated
Nicholas Skaggs (nskaggs) wrote :

If I disable and then re-enable networking, ubiquity sees that I am connected to the internet again. Note that this occurred in a VM,; trying to see if it's i386 only or not.

Nicholas Skaggs (nskaggs) wrote :

Yes I can confirm this is happening to me running i386 images on a 64bit ubuntu inside virtualbox. amd64 builds seem unaffected. Likely just a VM bug if no one on real hardware can confirm it,

Changed in ubiquity (Ubuntu):
importance: Undecided → Low
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
Vector (general-5) wrote :

I've seen this as well. However, it's when installing linux MCE which uses the Ubiquity installer. Everyone just seems to recognize it as a bug and move on. Unfortunately in the linux MCE installer there is no option disable and then re-enable networking as far as I can tell. I've seen it when doing the i386 installation and I've reproduced it with real hardware and using VMware. It looks like this expired but was it ever resolved?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers