gwibber crashed with SIGSEGV

[Jorge Castro]

Binary package hint: gwibber

Updated Jaunty, pure crash on startup, didn't even see the window popup

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
Package: gwibber 0.8-0ubuntu3
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 ?? () from /usr/lib/libwebkit-1.0.so.1
 ?? () from /usr/lib/libwebkit-1.0.so.1
 ?? () from /usr/lib/libwebkit-1.0.so.1
 ?? () from /usr/lib/libwebkit-1.0.so.1
 ?? () from /usr/lib/libwebkit-1.0.so.1
Title: gwibber crashed with SIGSEGV
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:WTF::fastFree (ptr=0xb4cf7e20) at ../JavaScriptCore/wtf/FastMalloc.cpp:537
KJS::Lexer::clear (this=0xb4d34ea0)
KJS::Parser::parse (this=0xb4d7d780, exec=0xb38429d8,
KJS::Parser::parse<KJS::ProgramNode> (this=0xb4d7d780, exec=
KJS::Interpreter::evaluate (exec=0xb38429d8,

[Mean-Machine (mdanielski)]

also affects Ubuntu [9.10] Karmic

[Don Forigua (ingforigua)]

i use gwibber 2.0 on ubuntu karmic and it crash when i add a identi.ca account

[janmejay (singh-janmejay)]

i tried revno: 490 (on gentoo x86/10.0/desktop) (emerge --info is posted here -> http://pastie.org/757650)

the console out:

[janmejay@js:projects/gwibber]$ ./bin/gwibber -d -v
DEBUG:root:Launched from /home/janmejay/projects/gwibber/bin
INFO:root:Running from source tree; adjusting path
WARNING:root:desktopcouch is not available. . falling back to gconf
[1] 32140 segmentation fault ./bin/gwibber -d -v

[janmejay (singh-janmejay)]

gwibber 1.2.0_pre340 (which is the one portage tree pushes, had the same problem).

[Omer Akram (om26er)]

why was this upstreamed? is it an upstream issue?

[Hew (hew)]

Does this crash still occur with gwibber 2? The duplicate reports are only for 0.8.

[Omer Akram (om26er)]

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". Thanks again!