Bug 172956 - kopete crashes when logging into currently active jabber account from second computer
Summary: kopete crashes when logging into currently active jabber account from second ...
Status: RESOLVED DUPLICATE of bug 175753
Alias: None
Product: kopete
Classification: Applications
Component: Jabber Plugin (show other bugs)
Version: 0.60.81
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-16 15:22 UTC by Oliver Putz
Modified: 2008-12-29 11:39 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 Oliver Putz 2008-10-16 15:22:20 UTC
Version:           0.60.80 (using 4.1.68 (KDE 4.1.68 (KDE 4.2 >= 20081001)), Gentoo)
Compiler:          i686-pc-linux-gnu-gcc
OS:                Linux (i686) release 2.6.26-gentoo-r1

Steps to reproduce:

1) open kopete
2) log into some jabber account
3) log into the same jabber account from another machine
4) see a popup that notifies you that there was a connection problem (the other computer logged into this account)
5) click ok
6) see kopete crash with the following backtrace:

Application: Kopete (kopete), signal SIGSEGV
[Current thread is 0 (LWP 8231)]

Thread 3 (Thread 0xb32ffb90 (LWP 8232)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb6055021 in select () from /lib/libc.so.6
#2  0xb7fad92b in QEventDispatcherUNIX::select (this=0x84781a8, nfds=29, readfds=0x84c5f2c, writefds=0x84c6140, exceptfds=0x84c6354, timeout=0x0) at kernel/qeventdispatcher_unix.cpp:608
#3  0xb7fae5c3 in QEventDispatcherUNIXPrivate::doSelect (this=0x84c5e40, flags={i = -1288703448}, timeout=0x0) at kernel/qeventdispatcher_unix.cpp:172
#4  0xb7faf4d6 in QEventDispatcherUNIX::processEvents (this=0x84781a8, flags={i = -1288703400}) at kernel/qeventdispatcher_unix.cpp:895
#5  0xb7f816b0 in QEventLoop::processEvents (this=0x8478570, flags={i = -1288703336}) at kernel/qeventloop.cpp:149
#6  0xb7f81852 in QEventLoop::exec (this=0x8478570, flags={i = -1288703192}) at kernel/qeventloop.cpp:200
#7  0xb3683def in QCA::SyncThread::run (this=0x84c25a8) at support/syncthread.cpp:195
#8  0xb7e91a24 in QThreadPrivate::start (arg=0x84c25a8) at thread/qthread_unix.cpp:191
#9  0xb7e11160 in start_thread (arg=0xb32ffb90) at pthread_create.c:297
#10 0xb605bc0e in clone () from /lib/libc.so.6

Thread 2 (Thread 0xb2afeb90 (LWP 8233)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb7e14be5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb7e92c8f in QWaitCondition::wait (this=0x869e738, mutex=0x869e734, time=4294967295) at thread/qwaitcondition_unix.cpp:88
#3  0xb65ee9a3 in QHostInfoAgent::run (this=0x869e728) at kernel/qhostinfo.cpp:247
#4  0xb7e91a24 in QThreadPrivate::start (arg=0x869e728) at thread/qthread_unix.cpp:191
#5  0xb7e11160 in start_thread (arg=0xb2afeb90) at pthread_create.c:297
#6  0xb605bc0e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb5a17720 (LWP 8231)):
[KCrash Handler]
#6  0xb66062a1 in QAbstractSocketPrivate::canReadNotification (this=0x86376e8) at socket/qabstractsocket.cpp:593
#7  0xb65f6b9b in QAbstractSocketEngine::readNotification (this=0x8671c80) at socket/qabstractsocketengine.cpp:142
#8  0xb65f7f5d in QReadNotifier::event (this=0x8620140, e=0xbfd85ef0) at socket/qnativesocketengine.cpp:974
#9  0xb67b6fab in QApplicationPrivate::notify_helper (this=0x80c0fc8, receiver=0x8620140, e=0xbfd85ef0) at kernel/qapplication.cpp:3809
#10 0xb67bdae5 in QApplication::notify (this=0xbfd863e8, receiver=0x8620140, e=0xbfd85ef0) at kernel/qapplication.cpp:3399
#11 0xb7a022b1 in KApplication::notify (this=0xbfd863e8, receiver=0x8620140, event=0xbfd85ef0) at /var/tmp/portage/kde-base/kdelibs-9999/work/kdelibs-9999/kdeui/kernel/kapplication.cpp:307
#12 0xb7f82b21 in QCoreApplication::notifyInternal (this=0xbfd863e8, receiver=0x8620140, event=0xbfd85ef0) at kernel/qcoreapplication.cpp:593
#13 0xb7fae450 in QEventDispatcherUNIX::activateSocketNotifiers (this=0x80c0b90) at kernel/qcoreapplication.h:215
#14 0xb7fae7f4 in QEventDispatcherUNIXPrivate::doSelect (this=0x80c6118, flags={i = -1076338552}, timeout=0xbfd86080) at kernel/qeventdispatcher_unix.cpp:252
#15 0xb7faf4d6 in QEventDispatcherUNIX::processEvents (this=0x80c0b90, flags={i = -1076337972}) at kernel/qeventdispatcher_unix.cpp:895
#16 0xb684c64f in QEventDispatcherX11::processEvents (this=0x80c0b90, flags={i = -1076337912}) at kernel/qeventdispatcher_x11.cpp:154
#17 0xb7f816b0 in QEventLoop::processEvents (this=0xbfd86380, flags={i = -1076337848}) at kernel/qeventloop.cpp:149
#18 0xb7f81852 in QEventLoop::exec (this=0xbfd86380, flags={i = -1076337784}) at kernel/qeventloop.cpp:200
#19 0xb7f83c6f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:851
#20 0xb67b6d43 in QApplication::exec () at kernel/qapplication.cpp:3337
#21 0x08086dff in main (argc=3, argv=0xbfd867d4) at /var/tmp/portage/kde-base/kopete-9999/work/kopete/kopete/kopete/main.cpp:102
Comment 1 Alan Jones 2008-12-29 07:26:16 UTC
Hi Oliver,

Thanks for the report. I've been unable to repro this, logging into a gmail jabber account from kopete, and then yoono. Could you check whether this still occurs on a recent build, and if so provide an updated backtrace?

Thanks very much.

Cheers,

Alan.
Comment 2 Alan Jones 2008-12-29 07:27:59 UTC
Hi again Oliver,

Also if you still do experience the crash, could you check whether using qt-copy helps as it sounds like it may be https://bugs.kde.org/show_bug.cgi?id=175753

Though the backtrace differs enough to make me think it may not be.

Cheers,

Alan.
Comment 3 Alan Jones 2008-12-29 08:15:08 UTC
Hi Oliver,

Thanks - it appears it is a dupe of 175753.

Cheers,

Alan.

*** This bug has been marked as a duplicate of bug 175753 ***
Comment 4 Oliver Putz 2008-12-29 11:39:28 UTC
Ok Alan, I will check once I have access to a KDE4 version again and reopen this bug report if it is no duplicate