gwibber-service crashed with SIGSEGV in ffi_call_unix64()

[Levan Chelidze]

I do not know just crash I was watching videos online

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gwibber-service 3.6.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
Uname: Linux 3.8.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Fri Feb 22 19:05:11 2013
ExecutablePath: /usr/bin/gwibber-service
InstallationDate: Installed on 2012-10-31 (113 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fa0e0258cc6: cmp %rbp,(%rax)
 PC (0x7fa0e0258cc6) ok
 source "%rbp" ok
 destination "(%rax)" (0x1f00000020) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libsignon-glib.so.1
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gwibber-service crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: Upgraded to raring on 2013-01-22 (30 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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 #1123780, 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.