gwibber crashed with SIGSEGV in g_closure_invoke()

[Andres Mujica]

Binary package hint: gwibber

Read through updates, opened a link, after a while (more than 5 minutes) the apport popped up with the crash.

Release of Ubuntu: karmic alpha2 fully updated
Package Version: 1.2.0~bzr346-0ubuntu1

apt-cache policy gwibber
gwibber:
  Instalados: 1.2.0~bzr346-0ubuntu1
  Candidato: 1.2.0~bzr346-0ubuntu1
  Tabla de versión:
 *** 1.2.0~bzr346-0ubuntu1 0
        500 http://co.archive.ubuntu.com karmic/universe Packages
        100 /var/lib/dpkg/status
     1.2.0~bzr346-0ubuntu1~daily1 0
        500 http://ppa.launchpad.net karmic/main Packages

Expected Results: to work without interruptions/crashes
Actual Results: died after a while

ProblemType: Crash
Architecture: amd64
Date: Sat Jul 4 10:52:35 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
Package: gwibber 1.2.0~bzr346-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-10.12-generic
SegvAnalysis:
 Segfault happened at: 0x7f2d011be4a8: mov (%rbx),%rdi
 PC (0x7f2d011be4a8) ok
 source "(%rbx)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 ?? () 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
 g_signal_emit_valist ()
Title: gwibber crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.30-10-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape vboxusers video

[Apport retracing service (apport)]

StacktraceTop:pango_layout_clear_lines (layout=0x7f2cdc1123f0)
gtk_label_size_allocate (
IA__g_closure_invoke (closure=0x263a110,
signal_emit_unlocked_R (node=0x263a340,
IA__g_signal_emit_valist (instance=0x452e940,

[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)]

This bug was reported a while ago and since then there have been many changes in gwibber and also there are no duplicates/ and comment from any one else facing this issue. Can you please confirm if this is still an issue for you in Karmic

[Vish (vish)]

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".