unity-gwibber-daemon crashed with SIGSEGV in g_sequence_get()

Bug #938564 reported by James Tait on 2012-02-22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)

Bug Description

This may indeed be a duplicate. I'm not able to reproduce the crash on demand - this time it happened after a reboot, but it seems to happen intermittently during normal operation. Version information is (should be) in the apport output - 12.04 x86_64 with latest updates as of 2012-02-22 ~10:00am.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-lens-gwibber 3.3.6-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
CheckboxSubmission: dd3689fa6394f60ec14dbe98d0bab891
CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
CrashCounter: 1
Date: Wed Feb 22 10:49:56 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gwibber/unity-gwibber-daemon
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: /usr/lib/gwibber/unity-gwibber-daemon
 Segfault happened at: 0x7fa1f33866ab: mov 0x18(%rdx),%rcx
 PC (0x7fa1f33866ab) ok
 source "0x18(%rdx)" (0x0000002c) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gwibber
 ?? () 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: unity-gwibber-daemon crashed with SIGSEGV in g_sequence_get()
UpgradeStatus: Upgraded to precise on 2012-01-13 (40 days ago)
UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare vde2-net

James Tait (jamestait) wrote :

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #937607, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers