'installing updates' windows hangs after asking question

Bug #29774 reported by Chris Moore
14
Affects Status Importance Assigned to Milestone
Baltix
Invalid
Medium
Unassigned
update-manager (Ubuntu)
Fix Released
High
Michael Vogt

Bug Description

When installing a gdm update, the 'installing updates' asked me in the 'terminal' panel whether to overwrite gdm.conf with the new version. I typed 'y' and hit return. It seemed to work.

Then it complained:

  debconf: unable to initialize frontend: Gnome
  debconf: (Can't locate object method "signal_connect" via package "Gtk2::Window" at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 73.)
  debconf: falling back to frontend: Dialog

and hung. I suspect it's waiting for me to answer the same question again in a dialog window. Why does it ask the same question twice, once in the terminal panel and once in a new dialog window?

Revision history for this message
Chris Moore (dooglus) wrote : screenshot

I've answered the question, but nothing is happening.

Could it be that I have to answer the question again in the dialog that's in the top left hand corner, hiding behind other windows?

Changed in update-manager:
assignee: nobody → mvo
Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

Can can confirm the problem here and will look into it later.

The actual bug is that synaptic (as the backend for update-manager) does not set the conffile dialog transient for the update-manager window.

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

This problem should be fixed with the latest synaptic/update-notifier. Please let me know if you still have trouble with.

Thanks,
 Michael

Changed in update-manager:
status: Confirmed → Needs Info
Revision history for this message
Chris Moore (dooglus) wrote :

Since this bug originally showed itself when installing 'gdm', I thought the best way to test it now would be to revert to the previous version of gdm and then let the update-manager install the current version again. But I don't have the previous version of 'gdm', and I don't see it in the package pool at archive.ubuntu.com either.

So instead I reverted to an old version of the kernel and let the update-notifier reinstall the current version. I left the embedded terminal window hidden while the kernel package installed, and when it got to the question about whether to install a boot block using /etc/lilo.conf the embedded terminal was opened up, showing the question. I was working in a different window at the time, so I didn't see the question for quite a long time. I could quite easily have missed it.

When I came to writing this response, I wanted to copy/paste the question from the embedded terminal, but couldn't, so I raised a new bug ( https://launchpad.net/distros/ubuntu/+source/update-notifier/+bug/31396 ) about that.

I think the question needs to be brought to the front so the user can see it and answer it before this bug can be considered fixed.

Revision history for this message
Chris Moore (dooglus) wrote :

I raised the other concern (about the kernel update question not being presented to the user if the window isn't visible) as bug #31436.

Revision history for this message
Leslie Satenstein (lsatenstein) wrote :

Leslie Satenstein
Montreal Canada

On fresh 5.10 install, updates hang after selection. No file download takes place.

Revision history for this message
Chris Moore (dooglus) wrote :

Wouldn't that be a different bug Leslie?

Revision history for this message
Mantas Kriaučiūnas (mantas) wrote :

I don't thing, that this bug exist in Baltix GNU/Linux

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

The original bug has been fixed, I close this for new. The various sub-bugs that sprang off from this report are dealt with in their own bug pages.

Cheers,
 Michael

Changed in update-manager:
status: Needs Info → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Baltix because there has been no activity for 60 days.]

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

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

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