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

Bug #853377 reported by Marco Biscaro
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Undecided
Unassigned

Bug Description

The crash just happened, without apparent reason.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-lens-gwibber 3.1.90-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Sun Sep 18 14:40:43 2011
ExecutablePath: /usr/lib/gwibber/unity-gwibber-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110721)
ProcCmdline: /usr/lib/gwibber/unity-gwibber-daemon
ProcCwd: /
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0xa0170d: mov (%esi),%eax
 PC (0x00a0170d) ok
 source "(%esi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 ?? () from /usr/lib/libgwibber.so.2
 gwibber_streams_messages () from /usr/lib/libgwibber.so.2
 ?? () from /usr/lib/libgwibber.so.2
 g_timeout_dispatch (source=0x9def710, callback=0xa08190, user_data=0x9ded9d0) at /build/buildd/glib2.0-2.29.90/./glib/gmain.c:3907
 g_main_dispatch (context=0x9dcaae8) at /build/buildd/glib2.0-2.29.90/./glib/gmain.c:2441
Title: unity-gwibber-daemon crashed with SIGSEGV in gwibber_streams_messages()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #835385, 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
tags: removed: need-i386-retrace
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.