It's not clear to me what we can or should do here. This is easily reproducible by starting update-manager in an environment without a $DISPLAY, e.g. from an ssh session where the display is not forwarded.
The error message is perhaps too cryptic to be useful, so one fix might be to catch the exception and print a more helpful error message. If that fairly easy fix is enough, let me know and I'll work on that. ** Summary changed: - update-manager crashed with RuntimeError in /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py: Gtk couldn't be initialized + cryptic traceback when running update-manager w/no X $DISPLAY -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/848915 Title: cryptic traceback when running update-manager w/no X $DISPLAY To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/848915/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
