update-manager crashed when I changed to main server

[David Coggins]

Binary package hint: update-manager

I want to get the new eclipse 3.5 with apt-get so changed software sources from Australia server to Main server. Then I ran update manager. All the updates downloaded OK including linux...-12 however hlaf through installing the updates the machine rebooted by itself. I then started linux...-11 in recovery mode and chose the dpkg option. Now I have restarted into linux...-12. I am running Karmic on an Asus EEE PC 701.

ProblemType: Crash
Architecture: i386
Date: Fri Oct 9 15:35:34 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/update-manager
InterpreterPath: /usr/bin/python2.6
Package: update-manager 1:0.126
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.6 /usr/bin/update-manager --no-focus-on-map
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_AU.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
PythonArgs: ['/usr/bin/update-manager', '--no-focus-on-map']
SourcePackage: update-manager
Tags: ubuntu-unr
Title: update-manager crashed with RuntimeError in <module>()
Traceback:
 Traceback (most recent call last):
   File "/usr/bin/update-manager", line 43, in <module>
     gtk.init_check()
 RuntimeError: could not open display
Uname: Linux 2.6.31-12-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:1975): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1975): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2105): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2203): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #350988, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.