ubuntu-webapps-update-index crashed with SIGSEGV in unity_webapps_url_db_insert_url_prepare_statement()

[janderson3m]

open system

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity-webapps-service 2.3.8-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.3-0ubuntu1
Architecture: amd64
Date: Fri Sep 28 20:11:32 2012
ExecutablePath: /usr/bin/ubuntu-webapps-update-index
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
ProcCmdline: ubuntu-webapps-update-index
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=pt_BR:pt:en
 TERM=xterm
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x402346: mov 0x0(%r13),%rdi
 PC (0x00402346) ok
 source "0x0(%r13)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libunity-webapps
StacktraceTop:
 ?? ()
 ?? ()
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: ubuntu-webapps-update-index crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 unity_webapps_url_db_insert_url_prepare_statement (package=<optimized out>, url=<optimized out>, url_db=0x0) at ../unity-webapps-url-db.c:37
 unity_webapps_url_db_insert_url (url_db=0x0, url=<optimized out>, package=package@entry=0x78c8500 "unity-webapps-angrybirds") at ../unity-webapps-url-db.c:128
 package_info_done (channel=<optimized out>, condition=<optimized out>, user_data=<optimized out>) at ubuntu-webapps-update-index.c:89
 g_main_dispatch (context=0x242d060) at /build/buildd/glib2.0-2.34.0/./glib/gmain.c:2715
 g_main_context_dispatch (context=context@entry=0x242d060) at /build/buildd/glib2.0-2.34.0/./glib/gmain.c:3219

[Launchpad Janitor (janitor)]

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