Bug 187404 - Crash when accessing buddy of deleted account
Summary: Crash when accessing buddy of deleted account
Status: RESOLVED DUPLICATE of bug 176592
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-17 15:03 UTC by Clemens Eisserer
Modified: 2009-12-25 13:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Clemens Eisserer 2009-03-17 15:03:11 UTC
Version:           0.70.0 (using KDE 4.2.1)
Compiler:          gcc -4.4 
OS:                Linux
Installed from:    Fedora RPMs

This is what I did:

* 3 accounts: Jabber, ICQ and MSN
* Deleted MSN account
* Right-click on buddy which was an msn-buddy (in order to delete it)
-> crash

Stacktrace:
Application: Kopete (kopete), signal SIGSEGV
0x009f9c4c in nanosleep () from /lib/libc.so.6
[Current thread is 1 (Thread 0xb7f21ab0 (LWP 5211))]

Thread 3 (Thread 0xb66f2b70 (LWP 5212)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:123
#1  0x05213557 in QWaitConditionPrivate::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:87
#2  QWaitCondition::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:159
#3  0x05477eda in QHostInfoAgent::run (this=0x87eb8e0) at kernel/qhostinfo.cpp:260
#4  0x052124ee in QThreadPrivate::start (arg=0x87eb8e0) at thread/qthread_unix.cpp:189
#5  0x00b067d7 in start_thread (arg=0xb66f2b70) at pthread_create.c:297
#6  0x00a3ba0e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xb5affb70 (LWP 5213)):
#0  0x00c3bfb6 in *__GI_clock_gettime (clock_id=12845044, tp=0xb5afef68) at ../sysdeps/unix/clock_gettime.c:100
#1  0x05331e3b in QTimerInfoList::getTime (this=0x879b4cc, t=@0x879b4f0) at kernel/qeventdispatcher_unix.cpp:339
#2  0x05332041 in QTimerInfoList::updateCurrentTime (this=0x879b4cc) at kernel/qeventdispatcher_unix.cpp:297
#3  0x05332aec in QTimerInfoList::timerWait (this=0x879b4cc, tm=@0xb5afeff4) at kernel/qeventdispatcher_unix.cpp:420
#4  0x05330550 in timerSourcePrepare (source=0x879b498, timeout=0xb5aff05c) at kernel/qeventdispatcher_glib.cpp:140
#5  0x0511bff0 in IA__g_main_context_prepare (context=0x879bf38, priority=0xb5aff0dc) at gmain.c:2134
#6  0x0511c3c1 in g_main_context_iterate (context=0x879bf38, block=<value optimized out>, dispatch=1, self=0x87a1760) at gmain.c:2428
#7  0x0511c90a in IA__g_main_context_iteration (context=0x879bf38, may_block=1) at gmain.c:2511
#8  0x053303a7 in QEventDispatcherGlib::processEvents (this=0x879bec8, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:325
#9  0x05303379 in QEventLoop::processEvents (this=0x879b5b0, flags=) at kernel/qeventloop.cpp:149
#10 0x053037c2 in QEventLoop::exec (this=0x879b5b0, flags={i = 0}) at kernel/qeventloop.cpp:200
#11 0x01573d0a in QCA::SyncThread::run() () from /usr/lib/libqca.so.2
#12 0x052124ee in QThreadPrivate::start (arg=0x87a0d38) at thread/qthread_unix.cpp:189
#13 0x00b067d7 in start_thread (arg=0xb5affb70) at pthread_create.c:297
#14 0x00a3ba0e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Current language:  auto; currently asm

Thread 1 (Thread 0xb7f21ab0 (LWP 5211)):
[KCrash Handler]
#5  0x070652ba in Kopete::Account::myself() const () from /usr/lib/libkopete.so.4
#6  0x0707f6ec in Kopete::Contact::isOnline() const () from /usr/lib/libkopete.so.4
#7  0x07098fb9 in Kopete::MetaContact::isOnline() const () from /usr/lib/libkopete.so.4
#8  0x0709995e in Kopete::MetaContact::isReachable() const () from /usr/lib/libkopete.so.4
#9  0x08069f5e in _start ()
Current language:  auto; currently c


I used pidgin a long time, but kopete is way better :)
Thanks a lot for kopete.
Comment 1 Dario Andres 2009-03-17 15:26:08 UTC
The first lines of the backtrace are similar to the first ones of the one posted at bug 176592. Also, the situations have some common points
Thanks for reporting
Comment 2 Roman Jarosz 2009-12-25 13:38:21 UTC

*** This bug has been marked as a duplicate of bug 176592 ***