gwibber crashed with SIGSEGV in pango_context_get_gravity()

[Laura Czajkowski]

Binary package hint: gwibber

running karmic and laptop had recently come back after issues related to a different problem and launched the crash report for gwibber. Gwibber was not running nor was it selected to run

ProblemType: Crash
Architecture: i386
Date: Sun Jul 26 20:17:57 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
Package: gwibber 1.2.0~bzr346-0ubuntu2
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcCwd: /home/czajkowski
ProcEnviron:
 LANG=en_IE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.22-generic
SegvAnalysis:
 Segfault happened at: 0xad03b9 <pango_context_get_gravity+25>: mov 0x1c(%eax),%eax
 PC (0x00ad03b9) ok
 source "0x1c(%eax)" (0xaaaaaac6) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 pango_context_get_gravity (context=0xaaaaaaaa)
 line_set_resolved_dir (line=0x9777940,
 pango_layout_check_lines (layout=<value optimized out>)
 pango_layout_get_extents_internal (
 IA__gtk_label_set_selectable (label=0x915f680, setting=0)
Title: gwibber crashed with SIGSEGV in pango_context_get_gravity()
Uname: Linux 2.6.30-6-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[Apport retracing service (apport)]

StacktraceTop:pango_context_get_gravity (context=0xaaaaaaaa)
line_set_resolved_dir (line=0x9777940,
pango_layout_check_lines (layout=<value optimized out>)
pango_layout_get_extents_internal (
IA__gtk_label_set_selectable (label=0x915f680, setting=0)

[Victor Vargas (kamus)]

Can you try to reproduce this issue in latest version of gwibber? Thanks!

[Laura Czajkowski (czajkowski)]

never happened again, launched other applications, tried to make it recrash again. No gwibber crash report was launched.

[Victor Vargas (kamus)]

This bug report is being closed due to your last comment regarding this being fixed with an update. Thanks!