update-notifier crashed with SIGSEGV in free()

[David Baucum]

Crashed occured immediately after logging in.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: update-notifier 0.132
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic i686
ApportVersion: 2.9.2-0ubuntu5
Architecture: i386
CrashCounter: 1
Date: Sat Apr 6 15:58:55 2013
ExecutablePath: /usr/bin/update-notifier
InstallationDate: Installed on 2012-10-25 (163 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
ProcCmdline: update-notifier
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6c1b0f6 <free+38>: mov -0x4(%ecx),%ecx
 PC (0xb6c1b0f6) ok
 source "-0x4(%ecx)" (0x893cec7f) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
 free () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_free () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_strfreev () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgioremote-volume-monitor.so
Title: update-notifier crashed with SIGSEGV in free()
UpgradeStatus: Upgraded to raring on 2013-02-22 (43 days ago)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Stacktrace:
 #0 0xb6c1b0f6 in ?? ()
 No symbol table info available.
StacktraceTop: ?? ()

[Launchpad Janitor (janitor)]

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

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This crash occurred in update-notifier's monitoring of disks for a disc that contains Ubuntu packages. Beginning with Ubuntu 13.10 this code has been replaced with an upstart user session job and subsequently this crash can no long occur. Therefore this bug is being marked as invalid.