zeitgeist-datahub crashed with SIGSEGV in PyObject_SetAttrString()

[lukas]

Description: Ubuntu karmic (development branch)
Release: 9.10 (beta)

ProblemType: Crash
Architecture: i386
CheckboxSubmission: ee69277f2904eadf27807477f16abd4e
CheckboxSystem: 5f97dbe7493563695babbf60c4c39eb2
Date: Fri Oct 2 23:20:48 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/zeitgeist-datahub
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: zeitgeist-core 0.2.1-0ubuntu1
PackageArchitecture: all
ProcCmdline: python /usr/bin/zeitgeist-datahub
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x8092468 <PyObject_SetAttrString+24>: mov 0x4(%ebx),%eax
 PC (0x08092468) ok
 source "0x4(%ebx)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: zeitgeist
Stacktrace:
 #0 0x08092468 in PyObject_SetAttrString ()
 No symbol table info available.
 Cannot access memory at address 0xbfaaed8c
StacktraceTop: PyObject_SetAttrString ()
ThreadStacktrace:
 .
 Thread 1 (Thread 5149):
 #0 0x08092468 in PyObject_SetAttrString ()
 No symbol table info available.
 Cannot access memory at address 0xbfaaed8c
Title: zeitgeist-datahub crashed with SIGSEGV in PyObject_SetAttrString()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:PyObject_SetAttrString ()

[Sense Egbert Hofstede (sense)]

Thank you for making Ubuntu and Zeitgeist better by reporting this bug. However, we could use a little bit more information. Could you describe what you were doing when the crash happened and what you think most likely caused the bug? Thanks in advance.

[Sense Egbert Hofstede (sense)]

It has been more than a month since I asked you can still confirm the bug. Because your last message was more than two months ago and because of the fact that Zeitgeist is still under heavy development I assume this bug no longer occurs and am therefore marking it as Invalid.
However, please feel free to reopen the bug if you can still confirm it and are able to provide more details.
Thanks!