unity-shopping-daemon crashed with SIGSEGV in g_main_context_remove_poll_unlocked()

[joshiss]

while installing thundirbird from synaptic package manager the error occured

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity-lens-shopping 6.0.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic i686
ApportVersion: 2.5.3-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Mon Oct 1 14:22:35 2012
ExecutablePath: /usr/lib/i386-linux-gnu/unity-shopping-daemon
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120324)
ProcCmdline: /usr/lib/i386-linux-gnu/unity-shopping-daemon
SegvAnalysis:
 Segfault happened at: 0xb73b79c7: mov 0x38(%eax),%edi
 PC (0xb73b79c7) ok
 source "0x38(%eax)" (0x00000038) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-lens-shopping
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_source_add_child_source () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgiognutls.so
Title: unity-shopping-daemon crashed with SIGSEGV in g_source_add_child_source()
UpgradeStatus: Upgraded to quantal on 2012-07-23 (69 days ago)
UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 g_main_context_remove_poll_unlocked (context=0x0, fd=0xb834d23c) at /build/buildd/glib2.0-2.34.0/./glib/gmain.c:3744
 block_source (source=0xb834d208) at /build/buildd/glib2.0-2.34.0/./glib/gmain.c:2610
 block_source (source=0xb82e4860) at /build/buildd/glib2.0-2.34.0/./glib/gmain.c:2619
 g_source_add_child_source (source=source@entry=0xb834d188, child_source=0xb82e4860) at /build/buildd/glib2.0-2.34.0/./glib/gmain.c:1339
 gnutls_source_sync (gnutls_source=gnutls_source@entry=0xb834d188) at gtlsconnection-gnutls.c:858

[Launchpad Janitor (janitor)]

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