Ubuntu
update-manager package

After new install, 151 packages update, install reports: Error committing changes, Possibly a problem DL some packages or commit would break packages. Re-installed three times, problem continues.. Please advise!

Bug #195572 reported by frankvlamings
6
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

First CD made from Kubuntu 7.10 on 11/07, installed OK. When updated 151 packages, DL OK. Install crashed after 59% installed in Update-Manager. Then second CD made on 2/24/08 Kubuntu 710, Alternate System, exactly the same identical error after 59% had been installed it crashed, when new version libqt3-mt... attempted to be installed.
Following came up: There was an error committing changes. Possibly there was a problem down loading some packages or the commit would break packages.. Thank you for any help to resolve..... Frank

Revision history for this message
petertheclock (petertheclock) wrote :

Looks like the same problem I have had, this is the third time this has happened to me - does anyone have an answer?

Revision history for this message
petertheclock (petertheclock) wrote :

Following the above any attempt to update showed a message to the effect of "unable to get exclusive lock" and that perhaps another update package was in use. An instruction followed to use the shell window with a command which I cannot remember - it was a single word with the suffix " -a". If I come across it again I will let you know, sorry to be unhelpful.

The use of this command offered the option of accepting a listing (or somesuch) provided by the package creator which, when accepted cleared the problem - apt-get update shows a list of some 43 packages - apt-get upgrade downloads nothing, so I assume that all is OK. Peter

Revision history for this message
ronny (ronny-standtke) wrote :

Same problem here. Fresh install from CD and then updating the system just failes with an error. What a shame.
Looks like this is related to Bug #183241.

Revision history for this message
Iulian Udrea (iulian) wrote :

Thank you for your bug report. This particular bug has already been reported and is a duplicate of bug #183241, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report.

Thank you.

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

Other bug subscribers

Remote bug watches

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