update-manager crashed with AttributeError in resize_to_standard_width(): 'NoneType' object has no attribute 'get_resolution' if $DISPLAY is not set

Status changed to 'Confirmed' because the bug affects multiple users.

Fixed wtih http://bazaar.launchpad.net/~ubuntu-core-dev/update-manager/main/revision/2678

Hello Karma, or anyone else affected,

Accepted update-manager into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/update-manager/1:0.196.12 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

No crash. The test case gives the expected result with http://launchpad.net/ubuntu/+source/update-manager/1:0.196.12

$ unset DISPLAY
$ update-manager

(update-manager:15801): Gtk-WARNING **: cannot open display:
$

I remember that I have called update-manager by accident from the console (no X11-DISPLAY).

Probably it would be nice, if it would have a text mode interface that could be used when no display is available, but I know there are other commands that do the same at the command line, so it could also output some help text that might be useful for beginners . For example:

  update-manager is a graphical user interface that needs an X11 Display.

  If you do not have an X11 display, at the command line, you can use apt-get instead. See man apt-get for details.

This bug was fixed in the package update-manager - 1:0.196.12

---------------
update-manager (1:0.196.12) trusty-proposed; urgency=low

  * use Gtk.init() to ensure update-manager fails with a
    runtime error message instead of crashing if the display
    can not be opened (LP: #1269397)
 -- Michael Vogt <email address hidden> Thu, 24 April 2014 14:58:38 +0200

The verification of the Stable Release Update for update-manager has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

This bug was fixed in the package update-manager - 1:0.196.12

---------------
update-manager (1:0.196.12) trusty-proposed; urgency=low

  * use Gtk.init() to ensure update-manager fails with a
    runtime error message instead of crashing if the display
    can not be opened (LP: #1269397)
 -- Michael Vogt <email address hidden> Thu, 24 April 2014 14:58:38 +0200

Apport is giving me information that this issue is raising now at cosmic. Upgrade done today.

Reopening, this regressed on Cosmic.

Works for me:

$ env -i update-manager
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused

(update-manager:13433): Gtk-WARNING **: 08:47:49.719: cannot open display:

Here is the crash file from Cosmic. From the information in this crash file it happens when update-manager is launched by update-notifier:

 mai 30 08:33:36 sark update-notifier.desktop[6220]: Traceback (most recent call last):
 mai 30 08:33:36 sark update-notifier.desktop[6220]: File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line 100, in <lambda>
 mai 30 08:33:36 sark update-notifier.desktop[6220]: self.resize_to_standard_width())
 mai 30 08:33:36 sark update-notifier.desktop[6220]: File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line 141, in resize_to_standard_width
 mai 30 08:33:36 sark update-notifier.desktop[6220]: GObject.signal_handler_block(ctx, self.signal_changed)
 mai 30 08:33:36 sark update-notifier.desktop[6220]: AttributeError: 'UpdateManager' object has no attribute 'signal_changed'
 mai 30 08:33:36 sark update-notifier.desktop[6220]: Traceback (most recent call last):
 mai 30 08:33:36 sark update-notifier.desktop[6220]: File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line 100, in <lambda>
 mai 30 08:33:36 sark update-notifier.desktop[6220]: self.resize_to_standard_width())
 mai 30 08:33:36 sark update-notifier.desktop[6220]: File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line 141, in resize_to_standard_width
 mai 30 08:33:36 sark update-notifier.desktop[6220]: GObject.signal_handler_block(ctx, self.signal_changed)
 mai 30 08:33:36 sark update-notifier.desktop[6220]: AttributeError: 'UpdateManager' object has no attribute 'signal_changed'
 mai 30 08:33:36 sark update-notifier.desktop[6220]: Traceback (most recent call last):
 mai 30 08:33:36 sark update-notifier.desktop[6220]: File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line 100, in <lambda>
 mai 30 08:33:36 sark update-notifier.desktop[6220]: self.resize_to_standard_width())
 mai 30 08:33:36 sark update-notifier.desktop[6220]: File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line 141, in resize_to_standard_width
 mai 30 08:33:36 sark update-notifier.desktop[6220]: GObject.signal_handler_block(ctx, self.signal_changed)
 mai 30 08:33:36 sark update-notifier.desktop[6220]: AttributeError: 'UpdateManager' object has no attribute 'signal_changed'

It is actually not a duplicate but apport being confused by a similar trace.

for anyone landing on this bug report and running Cosmic I reported bug 1774131.

Sorry for the noise.

testing xubuntu 18.10