gwibber crashed with SIGSEGV in get_alignment()

Bug #356040 reported by David Dean
6
Affects Status Importance Assigned to Milestone
Gwibber
Invalid
Undecided
Unassigned
gwibber (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gwibber

gwibber crashed while I was away from the computer. I don't know what caused it directly.

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:
 PATH=(custom, user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 get_alignment (layout=0xb34748c8, line=0x9197c80)
 get_x_offset (layout=0x0, line=0x9197c80,
 get_line_extents_layout_coords (layout=0xb34748c8,
 pango_layout_get_extents_internal (layout=0xb34748c8,
 gtk_label_size_request (widget=0x89cc6e0,
Title: gwibber crashed with SIGSEGV in get_alignment()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape video

Revision history for this message
David Dean (ddean-ieee) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:get_alignment (layout=0xb34748c8, line=0x9197c80)
get_x_offset (layout=0x0, line=0x9197c80,
get_line_extents_layout_coords (layout=0xb34748c8,
pango_layout_get_extents_internal (layout=0xb34748c8,
gtk_label_size_request (widget=0x89cc6e0,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in gwibber (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Alexander Sack (asac) wrote :

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

Changed in gwibber (Ubuntu):
status: New → Triaged
Alexander Sack (asac)
visibility: private → public
Revision history for this message
Omer Akram (om26er) wrote :

this bug was reported a while ago and there have been many changes in gwibber since. can you please tell us if this issue still exist for you in gwibber 2.0. Thanks in advance.

Changed in gwibber (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Vish (vish) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.
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".

Changed in gwibber (Ubuntu):
status: Incomplete → Invalid
Changed in gwibber:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.