ggl-qt crashed with SIGSEGV in QMetaObject::activate()

[danisensei]

Error when I start the application

ProblemType: Crash
Architecture: i386
Date: Mon Sep 14 22:37:11 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/ggl-qt
Package: google-gadgets-qt 0.10.5-0.2ubuntu1
ProcCmdline: /usr/bin/ggl-qt
ProcEnviron:
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
SegvAnalysis:
 Segfault happened at: 0x37bed1 <_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+113>: test %edx,0x30(%eax)
 PC (0x0037bed1) ok
 source "%edx" ok
 destination "0x30(%eax)" (0x00000191) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: google-gadgets
StacktraceTop:
 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
 QHttp::stateChanged(int) () from /usr/lib/libQtNetwork.so.4
 ?? () from /usr/lib/libQtNetwork.so.4
 ?? () from /usr/lib/libQtNetwork.so.4
 ?? () from /usr/lib/libQtNetwork.so.4
Title: ggl-qt crashed with SIGSEGV in QMetaObject::activate()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #361063, 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.