gwibber crashed with SIGSEGV

[Matt Robinson]

Binary package hint: gwibber

Gwibber loaded for first time, I added my Twitter account. Immediately afterwards all Gwibber windows became inactive (greyed) then it crashed. On second load, all worked fine and my Twitter account was fully functional.

ProblemType: Crash
Architecture: i386
Date: Sat Oct 31 20:42:53 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
Package: gwibber 2.0.0~bzr476-0ubuntu3
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x84b26c7: mov (%eax),%edi
 PC (0x084b26c7) ok
 source "(%eax)" (0xffffffff) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 ?? () from /usr/lib/libwebkit-1.0.so.2
 ?? () from /usr/lib/libwebkit-1.0.so.2
 ?? () from /usr/lib/libwebkit-1.0.so.2
 ?? () from /usr/lib/libwebkit-1.0.so.2
 ?? () from /usr/lib/libwebkit-1.0.so.2
Title: gwibber crashed with SIGSEGV
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip ext_users fax floppy fuse mythtv plugdev sambashare scanner tape users

[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 #442693, 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.