asks for cdrom during online upgrade

Bug #152611 reported by Marvin M
2
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Undecided
Michael Vogt

Bug Description

Binary package hint: update-manager

during online upgrade to u 7.10
upgrade manager window had just put a check mark on 'modifying the software channels'
I got a message- please insert Ubuntu 7.10 gutsy gibbon release candidate amd 64 20071010 into drive '/cdrom'.
I put a Ububtu7.10-rc desktop- amd 64.iso disk into the drive.
Waited until browser displayed contents of drive, then clicked on continue.
gutsy proceded to download the installation files from the website.
occasionally I heard the cdrom spin up and shutdown during the install.
After the install- I do not see a cdrom icon in 'places', the cdrom spins up but does not display contents on screen. It fails for any cd- data or music.

I had previously used this disk to preview gutsy.
Also, I had started to install from disk but aborted (before partitioning) when I did not see any 'update' path.
Then I found update instructions online.
Then tried to update online Sat about 4:00 cst. Had the same bug, it called for cd, let it proceed a few minutes,
but the download was so slow, I canceled it.
Note: At that time, I couldn't even access the ubuntu website or forums, but could access other websites.

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log files from '/var/log/dist-upgrade/' to this bugreport as attachments to your bug report? Thanks in advance.

Changed in update-manager:
assignee: nobody → mvo
status: New → Incomplete
Revision history for this message
Marvin M (cdpm23a) wrote :

On 10/18 00:25 the problem re-occurred.
I was using synapic to load java and got the message to load cd (see screenshot attachment).
I loaded cd and clicked on ok. Packages loaded ok.
If it happens again, I will click cancel and see what happens.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in update-manager:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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