GNOME Bugzilla – Bug 667760
empathy crashed with SIGSEGV in g_object_ref()
Last modified: 2012-03-06 06:02:52 UTC
Originally reported at: https://bugs.launchpad.net/bugs/819485 also present in 12.04 ubuntu and empathy 3.3.3 more peopleare affected. ubuntu 11.10 empathy 3.1.4-1ubuntu1 trying to launch empathy under kde resulted in a crash ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: empathy 3.1.4-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0 Uname: Linux 3.0.0-7-generic x86_64 Architecture: amd64 Date: Mon Aug 1 21:14:40 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110728) ProcCmdline: /usr/bin/empathy ProcEnviron: LANGUAGE=en_GB:en LANG=en_HK.UTF-8 LC_MESSAGES=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fa464646831 <g_object_ref+17>: cmpq $0x50,(%rax) PC (0x7fa464646831) ok source "$0x50" ok destination "(%rax)" (0x4808245c8b48c031) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: empathy StacktraceTop: g_object_ref () 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 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: empathy crashed with SIGSEGV in g_object_ref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace with debug symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance! Also, why did you file this under "Accessibility"?
andre klapper..cassidy said me to upstream it and i guess so it will be accessibility you can set it if you know because you are a deveoper and i say now that its the problem with accounts than it will be in accounts.. thanks
Okay, but we still need a stacktrace, as for every crash, in general. > StacktraceTop: > g_object_ref () 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 > ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 is definitely not enough to find the problem.
The proper trace is available in the downstream bug: https://launchpadlibrarian.net/76514844/Stacktrace.txt Muhammad: when upstreaming crashes, you should always attach such trace. The simplified (ie, not retraced) version is basically useless to use.
ok i will take care next time.
I didn't manage to reproduce this issue. Was the account created using empathy-accounts or GNOME's online accounts UI? Anyway, I'd be interested to know if the bug is still reproductible using Empathy 3.3.4 (I'll release it today); I added some checks in this code. If it is, could you please attach a new trace and the ouput of ~/.xsession-errors?
ok if again this crash occur than i will get the trace by reporter or try to reproduce it by my self and than attach it.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!