Bug 172539 - Kopete crashes (Signal 11) when tried to open main window from tray icon.
Summary: Kopete crashes (Signal 11) when tried to open main window from tray icon.
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-10 20:24 UTC by Maxi Schimmel
Modified: 2008-10-22 20:45 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maxi Schimmel 2008-10-10 20:24:24 UTC
Version:           0.60.80 (KDE: 4.1.68 (KDE 4.1.68 (KDE 4.2 >= 20081001)) "release 3.2" ) (using Devel)
Compiler:           KDE: 4.1.68 (KDE 4.1.68 (KDE 4.2 >= 20081001)) "release 3.2"
OS:                Linux
Installed from:    Compiled sources

When I start a KDE session, kopete opens and show its icon on system tray, when I try to open the main window the application crashes.

On command line I has this:
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
kopete(9570)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '!
Calling appendChild() on a null node does nothing.
Object::connect: Parentheses expected, signal QSslSocket::QAbstractSocket::SocketError
Object::connect: No such signal QSslSocket::closed()
Object::connect: Parentheses expected, signal QSslSocket::QAbstractSocket::SocketError
Object::connect: No such signal QSslSocket::closed()
MMX: 1, SSE: 1, SSE2: 1, MMX-SSE: 1, 3dNow: 0, 3dNow+: 0
KCrash: Application 'kopete' crashing...
sock_file=/home/maxx/.kde4/socket-austin/kdeinit4__0

And the kde bug report is this:
Aplicación: Kopete (kopete), señal SIGSEGV
[Current thread is 1 (Thread 0xb58d3b00 (LWP 9570))]

Thread 3 (Thread 0xb2170b90 (LWP 9573)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb62bf057 in poll () from /lib/libc.so.6
#2  0xb5da5ef2 in ?? () from /usr/lib/libglib-2.0.so.0
#3  0xb5da6221 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#4  0xb675cec7 in QEventDispatcherGlib::processEvents (this=0x8537098, flags={i = -1307114824}) at kernel/qeventdispatcher_glib.cpp:321
#5  0xb6730f0a in QEventLoop::processEvents (this=0x9d6d108, flags={i = -1307114760}) at kernel/qeventloop.cpp:143
#6  0xb67310ca in QEventLoop::exec (this=0x9d6d108, flags={i = -1307114680}) at kernel/qeventloop.cpp:194
#7  0xb2865640 in QCA::SyncThread::run() () from /usr/lib/libqca.so.2
#8  0xb664275e in QThreadPrivate::start (arg=0x8a7f8a0) at thread/qthread_unix.cpp:185
#9  0xb65e11b5 in start_thread () from /lib/libpthread.so.0
#10 0xb62c8d0e in clone () from /lib/libc.so.6

Thread 2 (Thread 0xb196fb90 (LWP 9574)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb65e4bd5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb6643772 in QWaitCondition::wait (this=0x9fcda60, mutex=0x9fcda5c, time=4294967295) at thread/qwaitcondition_unix.cpp:82
#3  0xb720e0d2 in QHostInfoAgent::run (this=0x9fcda50) at kernel/qhostinfo.cpp:241
#4  0xb664275e in QThreadPrivate::start (arg=0x9fcda50) at thread/qthread_unix.cpp:185
#5  0xb65e11b5 in start_thread () from /lib/libpthread.so.0
#6  0xb62c8d0e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb58d3b00 (LWP 9570)):
[KCrash Handler]
#6  QMovie::state (this=0x81bd400) at image/qmovie.cpp:723
#7  0x0808b7ac in _start ()

I'm using KDE 4.1.68 from OpenSUSE Factory repos.
Comment 1 Maxi Schimmel 2008-10-22 20:45:17 UTC
Hi, with KDE 4.1.70 this issue has been resolved.
Thanks.