gwibber-service crashed with SIGSEGV in g_simple_async_result_complete()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gwibber-service 3.5.90-0ubuntu2
ProcVersionSign
Uname: Linux 3.5.0-15-generic i686
NonfreeKernelMo
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
Date: Tue Sep 25 21:54:47 2012
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
SegvAnalysis:
Segfault happened at: 0xb52aa61c: mov 0x8(%eax),%eax
PC (0xb52aa61c) ok
source "0x8(%eax)" (0x00000008) 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/
g_simple_
?? () from /usr/lib/
?? () from /lib/i386-
g_main_
Title: gwibber-service crashed with SIGSEGV in g_simple_
UpgradeStatus: Upgraded to quantal on 2012-09-06 (19 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video
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 #1053622, 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.