gtk? visual/input lockup at calculating new packages

Bug #199955 reported by foampeace
4
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

update-manager -d from gutsy to hardy upgrade. Expected upgrade to hardy. Sources list changed. Killed process "hardy". Often, it appears like gtk gui locks up after calculating new packages. Similar lockups occur in firefox regularly. Requires process kill.

Revision history for this message
Hanno Stock (hefe_bia) (hanno-stock) wrote :

Foampeace, thank you for your bug report.

There is a known issue with update-manager in Gutsy that could lead to an unresponsive GUI. However usually the program is still working. You should see high CPU usage in gnome-systemmonitor.

Please tell us, how long you have waited for the program to be responsive again and give us information about your system (What type and how fast is your CPU, how much RAM do you have installed?).

Also please attach your /var/log/dist-upgrade/apt.log file, so we can see whether problems occurred before the lockup.

Revision history for this message
Hanno Stock (hefe_bia) (hanno-stock) wrote :

setting to incomplete as reporter input is needed.

Changed in update-manager:
status: New → Incomplete
Revision history for this message
Hanno Stock (hefe_bia) (hanno-stock) wrote :

Sorry I forgot to mention: Foampeace, please attach all files from /var/log/dist-upgrade (there should be three of them).

Revision history for this message
foampeace (bitkrom) wrote :

ok no problem

Revision history for this message
foampeace (bitkrom) wrote :
Revision history for this message
foampeace (bitkrom) wrote :
Revision history for this message
foampeace (bitkrom) wrote :

term.log is empty

Revision history for this message
Hanno Stock (hefe_bia) (hanno-stock) wrote :

Hi foampeace,

thank you very much for attaching the log files.
Please also answer the other questions about your system. We have to identify whether this is a known issue or a completely new problem.

Thanks in advance.

Revision history for this message
foampeace (bitkrom) wrote : Re: [Bug 199955] Re: gtk? visual/input lockup at calculating new packages

Thanks you :) I have not had the problem at all since after the hardy
upgrade. Aside how can I gather the information you need?

On Sat, Mar 22, 2008 at 1:42 PM, Hanno Stock (hefe_bia)
<email address hidden> wrote:
> Hi foampeace,
>
> thank you very much for attaching the log files.
> Please also answer the other questions about your system. We have to identify whether this is a known issue or a completely new problem.
>
> Thanks in advance.
>
>
>
> --
> gtk? visual/input lockup at calculating new packages
> https://bugs.launchpad.net/bugs/199955
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
foampeace (bitkrom) wrote :

I attached an html file with sys specs. take care :)

On Sat, Mar 22, 2008 at 1:42 PM, Hanno Stock (hefe_bia)
<email address hidden> wrote:
> Hi foampeace,
>
> thank you very much for attaching the log files.
> Please also answer the other questions about your system. We have to identify whether this is a known issue or a completely new problem.
>
> Thanks in advance.
>
>
>
> --
> gtk? visual/input lockup at calculating new packages
> https://bugs.launchpad.net/bugs/199955
> You received this bug notification because you are a direct subscriber
> of the bug.
>

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

Thanks for oyur bugreport.

could you please try the upgrade again? Some gui hangs have been corrected and I'm curious if you still see it.

Changed in update-manager:
status: Triaged → Incomplete
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.