uncommented 'deb cdrom:[Ubuntu 12.10 _Quantal Quetzal_ - Beta i386 (20121011)]/ quantal main restricted' in sources.list after i386 installation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
The line, 'deb cdrom:[Ubuntu 12.10 _Quantal Quetzal_ - Beta i386 (20121011)]/ quantal main restricted' in /etc/apt/
The steps:
1. Install quantal amd64 desktop (preferably not using live usb route), use Erase ubuntu12.10 and reinstall option if there is already quantal installed
2, Reboot and check sources.list--> it could be noticed that the above line is commented there.
2. Then install quantal desktop i386 (20121011). ( Do not use live usb route. Installation should be directly using ubiquity)
3. Reboot after the installation and it could be noticed that the above live is uncommented there.
(A fresh i386 install, i.e. using Erase ubuntu and reinstall option also leaves the line commented. So it is only when reinstalling i386 from amd64 using ubiquity whilst keeping the personal files/folders causes this issue)
If uncommenting is the right thing to do, then all the other installations need to be fixed, (amd64 fresh or erase and reinstall, i386 fresh or erase and reainstall, using live usb session to reinstall etc. )because the line is appearing commented on those installations.
Could not notice any other effects of leaving the line uncommented than the software-center keeping asking for the cdrom.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: ubiquity (not installed)
ProcVersionSign
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu3
Architecture: i386
Date: Thu Oct 11 12:38:51 2012
InstallCmdLine: BOOT_IMAGE=
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | added: rls-q-incoming |
Changed in ubiquity (Ubuntu): | |
importance: | Undecided → Medium |
importance: | Medium → Low |
tags: |
added: rls-q-notfixing removed: rls-q-incoming |
Could not run ubiquity -d from live session because when using live session this behaviour is not seen