Kubuntu Gutsy fails clean install on Dell d620

Bug #214947 reported by Michel
4
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

Clean install on Dell d620 of Kubuntu Gutsy 7.10 from CD.

$ lsb_release -rd
Description: Ubuntu 7.10
Release: 7.10

Events:
* Install proper runs OK, installs on 1GB /boot and 35GB /
* Rebooted OK
* Got information in tray about non-free SW needed by HW. Installed nonfree firmware for Broadcom WiFi, apparently OK. This apparently has its own installer, separate from update-manager.
* Started update manager:
  - Finds list of updates okay
  - downloads (large) collection of updates
  - halfway through the install reports failure, saying either files not d/l or conflict detected. At this time, progress indicator is halfway, popup window leaves no option but to abort update.
  - update manager offers to upgrade version (!)
    -- Upgrader fails with lock file conflict.

Attached: tarred /var/log

Revision history for this message
Michel (mbouckaert) wrote :
Revision history for this message
Michel (mbouckaert) wrote : Re: [Bug 214947] Re: Kubuntu Gutsy fails clean install on Dell d620

Worked. apt-get install update-manager allowed everything to finish
cleanly.

Congrats for the 24-hr turnaround! I am ashamed I didn't equal that
with my thank-you note.

Cheers,

Michel.

On Thu, 2008-04-10 at 17:12 +0000, Michael Vogt wrote:

> ** Changed in: adept (Ubuntu)
> Sourcepackagename: update-manager => adept
>

Revision history for this message
kko (kko) wrote :

This report seems to contain a number of different issues. Judging on this part - "halfway through the install reports failure, saying either files not d/l or conflict detected. At this time, progress indicator is halfway, popup window leaves no option but to abort update" - could this be handled as a duplicate of bug 54450? (In other words, is the problem mostly that adept-updater is unable to deal with / more precisely tell what exactly the problem was?

If I understood you correctly, you have otherwise solved the problem on your system?

Revision history for this message
Jonathan Thomas (echidnaman) 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 adept:
status: New → 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.