unity-gwibber-daemon crashed with SIGSEGV

[Dennis van der Staal]

at startup

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-lens-gwibber 3.3.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Feb 29 05:19:00 2012
ExecutablePath: /usr/lib/gwibber/unity-gwibber-daemon
ProcCmdline: /usr/lib/gwibber/unity-gwibber-daemon
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=nl_NL.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f7e990c7687: mov (%rax,%r12,8),%rax
 PC (0x7f7e990c7687) ok
 source "(%rax,%r12,8)" (0x100000006) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 ?? () from /usr/lib/libdee-1.0.so.4
 ?? () from /usr/lib/libdee-1.0.so.4
 ?? () from /usr/lib/libgwibber.so.2
 ?? () from /usr/lib/libgwibber.so.2
 ?? () from /usr/lib/libgwibber.so.2
Title: unity-gwibber-daemon crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-02-22 (6 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

[Dennis van der Staal (dvdstaal)]

at startup program

[Apport retracing service (apport)]

StacktraceTop:
 dee_sequence_model_peek_value (self=0xa07d90, iter=0x174d4d0, column=0) at dee-sequence-model.c:595
 dee_sequence_model_get_value (self=0xa07d90, iter=0x174d4d0, column=0) at dee-sequence-model.c:603
 gwibber_streams_parse_message (self=<optimized out>, obj=<optimized out>, change=<optimized out>) at /storage/1/src/gwibber/trunk/libgwibber/streams.vala:705
 gwibber_streams_parse_messages (self=0x9b9c10, data=<optimized out>) at /storage/1/src/gwibber/trunk/libgwibber/streams.vala:357
 __lambda14_ (_data1_=<optimized out>) at /storage/1/src/gwibber/trunk/libgwibber/streams.vala:290

[Bilal Shahid (s9iper1)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible now ?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.