update-notifier crashed with SIGSEGV in g_signal_emit_valist()

[Conrad Steenberg]

I logged in and this appeared.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: update-notifier 0.126
ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
CrashCounter: 1
Date: Thu Mar 14 15:06:24 2013
ExecutablePath: /usr/bin/update-notifier
InstallationDate: Installed on 2012-07-21 (236 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64+mac (20120425.1)
MarkForUpload: True
ProcCmdline: update-notifier
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f68affd9e46 <__strcmp_sse42+22>: movdqu (%rdi),%xmm1
 PC (0x7f68affd9e46) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: update-notifier crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: Upgraded to quantal on 2012-11-07 (127 days ago)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo vboxusers

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