gnome-control-center crashed with SIGSEGV in gtk_tree_model_get_valist()

[Egor]

When I update my Ubuntu 10.04 LTS to Ubuntu 12.04 LTS my update-manager don't want start and an error.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.2.2-2ubuntu8
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sun Feb 12 23:10:20 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
ProcCmdline: gnome-control-center sound-nua
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
SegvAnalysis:
 Segfault happened at: 0x68a51c <gtk_tree_model_get_valist+332>: mov 0x18(%eax),%ebp
 PC (0x0068a51c) ok
 source "0x18(%eax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%ebp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 gtk_tree_model_get_valist () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 gtk_tree_model_get () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/control-center-1/panels/libsoundnua.so
 g_cclosure_marshal_VOID(unsigned int0_t) () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in gtk_tree_model_get_valist()
UpgradeStatus: Upgraded to precise on 2012-02-12 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev root sambashare
usr_lib_gnome-control-center:
 deja-dup 21.2-0ubuntu4
 gnome-bluetooth 3.2.2-0ubuntu1
 indicator-datetime 0.3.1-0ubuntu5

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #930133, 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.