gwibber crashed with SIGSEGV in is_end()

[JG]

This happened while trying to open Gwibber.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gwibber 3.3.6-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 16 20:26:44 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: gwibber
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ffef0ba949b: mov 0x18(%rdx),%rcx
 PC (0x7ffef0ba949b) ok
 source "0x18(%rdx)" (0x00000058) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_sequence_get () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/libdee-1.0.so.4
 ?? () from /usr/lib/libdee-1.0.so.4
 ?? () from /usr/lib/libgwibber.so.2
Title: gwibber crashed with SIGSEGV in g_sequence_get()
UpgradeStatus: Upgraded to precise on 2012-01-28 (19 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 is_end (iter=0x299d6a0) at /build/buildd/glib2.0-2.31.16/./glib/gsequence.c:199
 g_sequence_get (iter=0x299d6a0) at /build/buildd/glib2.0-2.31.16/./glib/gsequence.c:1167
 dee_sequence_model_peek_value (self=0x186c250, iter=0x299d6a0, column=0) at dee-sequence-model.c:586
 dee_sequence_model_get_value (self=0x186c250, iter=0x299d6a0, column=0) at dee-sequence-model.c:603
 ?? () from /tmp/tmpaW8MfV/usr/lib/libgwibber.so.2

[Bilal Shahid (s9iper1)]

Thank you for taking the time to report this bug and helping to make Ubuntu better,
* can you reproduce it ?
* if so than describe the steps to reproduce it?

[JG (jdogzz-g5)]

I'm not sure if it's because I'm clicking it too fast or what, but this is generally reproducible just by launching it once I'm logged in.

[Bilal Shahid (s9iper1)]

leaving it incomplete as its dups were found or any steps to reproduce it