telepathy-gabble crashed with SIGSEGV in sqlite3_exec()

[Cristian Tala]

Binary package hint: telepathy-gabble

In the first start of empathy, after inser the data of the account, this error ocurred.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: telepathy-gabble 0.8.12-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Fri Apr 30 14:17:20 2010
ExecutablePath: /usr/lib/telepathy/telepathy-gabble
LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/lib/telepathy/telepathy-gabble
ProcEnviron:
 SHELL=/bin/bash
 LANG=es_ES.UTF-8
SegvAnalysis:
 Segfault happened at: 0xf37519 <sqlite3_exec+41>: mov 0x44(%edx),%eax
 PC (0x00f37519) ok
 source "0x44(%edx)" (0x00000044) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-gabble
StacktraceTop:
 sqlite3_exec () from /usr/lib/libsqlite3.so.0
 ?? ()
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
 g_object_new () from /usr/lib/libgobject-2.0.so.0
Title: telepathy-gabble crashed with SIGSEGV in sqlite3_exec()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 sqlite3_exec (db=0x0,
 gabble_caps_cache_constructor (type=170689968, n_props=1,
 IA__g_object_newv (object_type=170689968, n_parameters=1,
 IA__g_object_new_valist (object_type=170689968,
 IA__g_object_new (object_type=170689968,

[Omer Akram (om26er)]

thanks for the bug report. is this still an issue?

[Omer Akram (om26er)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Vish (vish)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".