kopete crashed with SIGSEGV in Kopete::PasswordedAccount::~PasswordedAccount()

Bug #440939 reported by Shura
74
This bug affects 10 people
Affects Status Importance Assigned to Milestone
kopete-facebook (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: kdenetwork

The problem appears when I close Kopete.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Oct 2 23:45:58 2009
Disassembly: 0x1a: Cannot access memory at address 0x1a
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kopete
NonfreeKernelModules: nvidia
Package: kopete 4:4.3.1-0ubuntu3
ProcCmdline: kopete -session 10d8d4e36b000125451036500000017520018_1254517718_763174
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x1a: Cannot access memory at address 0x1a
 PC (0x0000001a) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: kdenetwork
StacktraceTop:
 ?? ()
 Kopete::PasswordedAccount::~PasswordedAccount() ()
 ?? () from /usr/lib/kde4/kopete_facebook.so
 QObjectPrivate::deleteChildren() ()
 QObject::~QObject() () from /usr/lib/libQtCore.so.4
Title: kopete crashed with SIGSEGV in Kopete::PasswordedAccount::~PasswordedAccount()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Shura (shura01) wrote :
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

This is a problem with the Facebook Kopete plugin. It was an experimental plugin being considered for includsion for Kubuntu 9.10. Unfortunately, it was seen as too unstable for default inclusion and has been removed from the default lineup. You may wish to remove the "kopete-facebook" package so that Kopete will not crash because of it.

affects: kdenetwork (Ubuntu) → kopete-facebook (Ubuntu)
Revision history for this message
Shura (shura01) wrote :

Ok, thank you !

Revision history for this message
Joshua Dunamis (dunamis) wrote :

Thanks, now I know the problem is kopete-facebook. I'll keep it hoping a fix as soon as.

Revision history for this message
Andy St.Martin (andystmartin) wrote :

Here is a little extra information in the stack trace (I installed the kdenetwork-dbg package):

Application: Kopete (kopete), signal: Segmentation fault
[KCrash Handler]
#6 0x00000005 in ?? ()
#7 0x00d82385 in ~PasswordedAccount (this=0xa502108, __in_chrg=<value optimized out>) at ../../../kopete/libkopete/kopetepasswordedaccount.cpp:42
#8 0x0661122a in ?? () from /usr/lib/kde4/kopete_facebook.so
#9 0x057d946f in QObjectPrivate::deleteChildren (this=0xa438430) at kernel/qobject.cpp:1847
#10 0x057e17cf in ~QObject (this=0xa43ef18, __in_chrg=<value optimized out>) at kernel/qobject.cpp:836
#11 0x00d84560 in ~Plugin (this=0xa43ef18, __in_chrg=<value optimized out>) at ../../../kopete/libkopete/kopeteplugin.cpp:44
#12 0x00d8fbc3 in ~Protocol (this=0xa43ef18, __in_chrg=<value optimized out>) at ../../../kopete/libkopete/kopeteprotocol.cpp:77
#13 0x0660c0b8 in ?? () from /usr/lib/kde4/kopete_facebook.so
#14 0x00d8b4c4 in ~PluginManagerPrivate (this=0xa02bd90, __in_chrg=<value optimized out>) at ../../../kopete/libkopete/kopetepluginmanager.cpp:76
#15 0x00d8497a in destroy () at ../../../kopete/libkopete/kopetepluginmanager.cpp:102
#16 0x00cfc44b in ~KCleanUpGlobalStatic (this=0xdd1cd4, __in_chrg=<value optimized out>) at /usr/include/kglobal.h:62
#17 0x00a2f05f in __run_exit_handlers (status=0, listp=0xb40304, run_list_atexit=true) at exit.c:78
#18 0x00a2f0cf in *__GI_exit (status=0) at exit.c:100
#19 0x00a16b5e in __libc_start_main (main=0x8057040 <main>, argc=3, ubp_av=0xbf8f5e34, init=0x80733f0 <__libc_csu_init>, fini=0x80733e0 <__libc_csu_fini>, rtld_fini=0x91dd20 <_dl_fini>,
    stack_end=0xbf8f5e2c) at libc-start.c:252
#20 0x08056fa1 in _start () at ../sysdeps/i386/elf/start.S:119

Revision history for this message
Bruno Bigras (brunoqc) wrote :

do you still have this crash with the kopete-facebook package from karmic-proposed (kopete-facebook 0.1.4-0ubuntu1.1) ?

Revision history for this message
Joshua Dunamis (dunamis) wrote :

No, with this upgrade I don't have this crash anymore. I seems fixed. Thank you!!!

Changed in kopete-facebook (Ubuntu):
status: New → Fix Committed
Revision history for this message
Joshua Dunamis (dunamis) wrote :

Today the bug is here again. It shows itself after a message board "You are disconnected" from Facebook account and now it appears every time as before the upgrade.

Changed in kopete-facebook (Ubuntu):
status: Fix Committed → Confirmed
Revision history for this message
Steve King (steveoldmanse-launchpad) wrote :

I am running with kopete-facebook 0.1.4-0ubuntu1.1 and the problem is still there.

Revision history for this message
Steve King (steveoldmanse-launchpad) wrote :

I don't know whether this helps, but it looks to me that I get the crash when I quit Kopete after it has previously reported it has lost its connection to Facebook. It will always lose the Facebook connection if I run Kopete for long enough (e.g. 60 minutes or so), but if I quit Kopete before it loses the FB connection then there is no crash.

Revision history for this message
Lorenzo Bettini (bettini) wrote :

I'm experiencing the same crash and the backtrace shows the same problem in ~PasswordedAccount (I'm using kwallet to store password).

Revision history for this message
Harald Sitter (apachelogger) wrote :

Facebook now supports chat via XMPP (aka Jabber), which is a native plugin to Kopete. Due to this change of circumstances kopete-facebook was recently removed from the archives in favor of the present solution. It is currently not planed to deploy further updates to the version used in Kubuntu karmic.

http://duncan.mac-vicar.com/blog/archives/644

Changed in kopete-facebook (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.