gwibber crashed with SIGSEGV in g_slist_reverse() (list=0xaaaaaaaaaaaaaaaa)

[Matt Zimmerman]

Binary package hint: gwibber

I opened Gwibber, updated my Facebook account preferences to authorize it to receive status updates, read through a few pages of updates, then switched to another window to do something else. Some time later, I saw that Gwibber had crashed.

ProblemType: Crash
Architecture: amd64
Date: Sun May 31 11:00:07 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
Package: gwibber 0.9.2~bzr263-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.30-6.7-generic
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 g_slist_reverse () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libpango-1.0.so.0
 ?? () from /usr/lib/libpango-1.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: gwibber crashed with SIGSEGV in g_slist_reverse()
Uname: Linux 2.6.30-6-generic x86_64
UserGroups: adm admin audio cdrom dialout fuse kvm lpadmin plugdev sambashare video
SegvAnalysis:
 Segfault happened at: 0x7fe1f0d769d3 <g_slist_reverse+19>: mov 0x8(%rdi),%rax
 PC (0x7fe1f0d769d3) ok
 source "0x8(%rdi)" (0xaaaaaaaaaaaaaab2) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA

[Apport retracing service (apport)]

StacktraceTop:IA__g_slist_reverse (list=0xaaaaaaaaaaaaaaaa)
pango_layout_check_lines (layout=0x3973b30)
pango_layout_get_extents_internal (
gtk_label_size_request (widget=0x2ef7060,
IA__g_closure_invoke (closure=0x26e7af0,

[Alexander Sack (asac)]

sending ubuntu gwibber crashes upstream. If gwibber devs want us to just close them instead let me know (through identi.ca ;)?

[Omer Akram (om26er)]

we are wondering if this is still an issue for you. can you please update to latest version of gwibber in karmic the bug you reported was against a development release. Have you faced this with gwibber 2.0

[Matt Zimmerman (mdz)]

On Tue, Feb 23, 2010 at 11:45:41AM -0000, Omer Akram wrote:
> we are wondering if this is still an issue for you. can you please
> update to latest version of gwibber in karmic the bug you reported was
> against a development release. Have you faced this with gwibber 2.0

I haven't seen this with 2.0.

--
 - mdz

[Omer Akram (om26er)]

marking this fixed as per last comment