update-notifier crashed with SIGSEGV in g_object_ref()

[Lockal]

update-notifier is unstable and crashes after unplugging (or maybe even plugging) canon camera.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: update-notifier 0.121ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.1-0ubuntu2
Architecture: amd64
Date: Tue Aug 28 20:19:26 2012
ExecutablePath: /usr/bin/update-notifier
ExecutableTimestamp: 1345906501
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
ProcCmdline: update-notifier
ProcCwd: /home/lockal
SegvAnalysis:
 Segfault happened at: 0x7fe16a9bbd91 <g_object_ref+17>: cmpq $0x50,(%rax)
 PC (0x7fe16a9bbd91) ok
 source "$0x50" ok
 destination "(%rax)" (0x0000008b) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
 g_object_ref (_object=0x7fe15c011e90) at /build/buildd/glib2.0-2.33.10/./gobject/gobject.c:2883
 g_list_foreach (list=<optimized out>, func=0x7fe16a9bbd80 <g_object_ref>, user_data=0x0) at /build/buildd/glib2.0-2.33.10/./glib/glist.c:942
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
 get_mounts (volume_monitor=<optimized out>) at /build/buildd/glib2.0-2.33.10/./gio/gunionvolumemonitor.c:119
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
Title: update-notifier crashed with SIGSEGV in g_object_ref()
UpgradeStatus: Upgraded to quantal on 2012-07-22 (37 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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 #1032953, 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.