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

[Alexander Anisimov]

I just delete one user account from system. After it, gnome-control-center crashed

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.2.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
Uname: Linux 3.0.0-16-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Tue Feb 21 09:08:27 2012
ExecutablePath: /usr/bin/gnome-control-center
ProcCmdline: gnome-control-center --overview
SegvAnalysis:
 Segfault happened at: 0xb4bb01 <g_hash_table_iter_init+33>: mov 0x2c(%edx),%edx
 PC (0x00b4bb01) ok
 source "0x2c(%edx)" (0x0000032d) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_hash_table_iter_init () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgdk-3.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_hash_table_iter_init()
UpgradeStatus: Upgraded to oneiric on 2011-10-18 (125 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lp lpadmin netdev plugdev sambashare tape tty vboxusers video
usr_lib_gnome-control-center:
 gnome-bluetooth 3.2.0-0ubuntu2
 indicator-datetime 0.3.1-0ubuntu1.1

[Apport retracing service (apport)]

StacktraceTop:
 g_io_channel_fill_buffer (channel=0xbfea72e4, err=0xc7e94d) at /build/buildd/glib2.0-2.30.0/./glib/giochannel.c:1507
 gdk_threads_dispatch (data=0x212d4d90) at /build/buildd/gtk+3.0-3.2.0/./gdk/gdk.c:754
 g_main_dispatch (context=0x211cc410) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:2412
 g_main_context_dispatch (context=0x211cc410) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3011
 gdk_threads_leave () at /build/buildd/gtk+3.0-3.2.0/./gdk/gdk.c:666

[Sebastien Bacher (seb128)]

the bug is years old without activity nor new report and the code changed quite a lot since, closing, feel free to register new bugs if you have issues in newer versions though