[Bug 2150178] Re: update-manager theoretically crashes due to Gtk.Window.run() in BuilderDialog

[Arnab Patra]

Hi,

Thanks for the detailed explanation — it makes sense.

I understand now that `BuilderDialog.run()` is not the root cause and
that the crashes I was seeing are happening earlier in the
dialog/backend initialization flow (specifically around objects like
`InstallBackendAptdaemon` and missing `window_dialog` attributes).

So I will not proceed with removing or modifying `BuilderDialog.run()`
or `window_dialog` at this stage, since it may only be legacy cleanup
and not related to the actual issue.

If you think there is a better entry point in the update-manager flow I
should start from, I’d appreciate your guidance.

Thanks again.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2150178

Title:
  update-manager theoretically crashes due to Gtk.Window.run() in
  BuilderDialog

Status in update-manager package in Ubuntu:
  Triaged

Bug description:
  In UpdateManager/Dialogs.py, BuilderDialog.run() calls
  self.window_dialog.run(), which causes a crash because
  Gtk.Window does not support the run() method (only Gtk.Dialog does).

  This leads to a runtime error when the dialog is shown.

  Proposed fix:
  Replace run() with show_all(), since update-manager already runs
  inside the GTK main loop.

  Patch attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2150178/+subscriptions