[gutsy] Update-manager doesn't work

Bug #126307 reported by Quinten
8
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I was working on my computer with Gutsy Gibbon Tribe 2. It was just installed and the icon "update-notification" came on, so I hit it. It said that there were 297 updates, but he couldn't install al of them. So he removed a few to update. I hit the "Update" button and I thought that it started. A few seconds later I saw that the icon in the panel above was disapeard and that a new "update icon " appeard, that said again that there were 297 updates. The first open "Update-manager" wasn't responding any more. I tried to hit the new "update icon" but nothing happened.
So I can not update my system!!

Revision history for this message
Kees Cook (kees) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

Revision history for this message
Heiko Sieger (heiko-actcom) wrote :

Confirm.

Found this older bug here:
https://bugs.launchpad.net/ubuntu/gutsy/+source/adept/+bug/121456

Tried all suggestions, incl.:
sudo apt-setup -- not found
sudo apt-get clean
sudo apt-get install deptags
sudo rm /var/cache/apt/*.bin
sudo apt-get update

and so forth.

synaptic works.

Seems that the bug listed above is back as of July 21.

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

Thanks for your bugreport.

Is this issue reproducible? If so, could you please open a terminal and run "update-manager" there and see if anything is printed on the terminal when it hangs? Could you please also check if there is a crash file in /var/crash after this problem happens?

Thanks,
 Michael

Changed in update-manager:
status: New → Incomplete
Revision history for this message
Michael Vogt (mvo) wrote :

I'm pretty sure that #121456 is unrelated to this problem. A strace of the hanging process might be helpful too.

Revision history for this message
Paul Dufresne (paulduf) 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.