Version: inconnu (using KDE 3.5.2, Debian Package 4:3.5.2-1 (testing/unstable)) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.15-1-686-smp when I push left button mouse on an icon in desktop, kdesktop freezes. I must kill and restart kdesktop. I've no problem with the same takedown with konqueror in /home/gml/Desktop. I've this bug since I've upgraded KDE to 3.5.2 version. My previous version was 3.5.1.
Run "kill -SEGV <pid-of-kdesktop>" to get a backtrace, and attach the backtrace here. Does the same freeze happen with a newly-created user?
When kdesktop freezes, I've launched "kill -SEGV <pid-of-kdesktop>". No backtrace appears, yet now kdesktop doesn't freezed when I push left button mouse on an icon in desktop. Have you any idea ?
Do you mean that the problem has gone away?
Problem looks like it has gone away. PS: don't attach backtraces; paste them.
The bug is always present when I restart kde.
I'm hit by this bug almost every day, but I found no way to reproduce it. Sometimes I had the feeling that this is a timing issue between the mouse-over popup window and a left mouse-button click or only appears by selecting icons which were just created seconds before a LMB click. but the bug also appears on "older" icons. the main problem with this bug is that it captures keyboard input. If I am not going directly to a console and "killall -9 kdesktop", but am moving my mouse around (kicker, kdesktop), in most cases no running app is able to get any further keyboard input. Therefore I have to kill kdesktop in these cases solely with the mouse, usually with ksysguard because there is an entry in kmenu and it does not need keyboard input. I'm sure that this regression was not present in KDE-3.5.0. I'm using kubuntu dapper; Qt: 3.3.6; KDE: 3.5.2; KDesktop: 3.5.2
sorry, some left-right confusion in by brain during the above posting; mostly kdesktop crashes during a right-click to open the context menu...
I can confirm this behavior with 3.5.2 on SuSE10. Have only noticed it with right-button clicks. Trying to kill the KDesktop proc usually freezes all of KDE, so now I just ctl-alt-backspace and login again. Happens about once a day.
Please to correct this, I can't use my desktop. I wish help you for debug this. How I track this bug ? Kdestop doesn't crash. Do you have any idea ?
This bug has also been reported in Kubuntu Dapper. https://launchpad.net/distros/ubuntu/+source/kdebase/+bug/43065
I have exactly the same problem here on Gentoo Linux, KDE 3.5.2. I am almost certain that this problem did not occur on KDE 3.5.0. What happens is that sometimes when I press the right mouse button on a KDesktop icon, KDesktop freezes. Whenever I call the RMB menu in any Konqueror window, this Konqueror window will freeze again. Only when I kill KDesktop, the Konqueror windows show the RMB menus and are alive again. Seems like the RMB menu calls KDesktop and blocks until it responds or dies. Here is the backtrace, created when KDesktop was frozen: #0 0x4faae128 in read () from /lib/libpthread.so.0 #1 0xb7485fe8 in ?? () from /usr/kde/3.5/lib/libDCOP.so.4 #2 0xb7480a0e in _kde_IceTransSocketRead (ciptr=0xfffffe00, buf=0xfffffe00 <Address 0xfffffe00 out of bounds>, size=-512) at Xtranssock.c:1710 #3 0xb7480e6f in _kde_IceTransRead (ciptr=0x8, buf=0xfffffe00 <Address 0xfffffe00 out of bounds>, size=-512) at Xtrans.c:845 #4 0xb747960c in _kde_IceRead (iceConn=0x8056278, nbytes=8, ptr=0x8056458 "\002\001") at misc.c:249 #5 0xb7479bd6 in KDE_IceProcessMessages (iceConn=0x8056278, replyWait=0xbff127e0, replyReadyRet=0xbff1274c) at process.c:153 #6 0xb74658b7 in DCOPClient::callInternal(QCString const&, QCString const&, QCString con st&, QMemArray<char> const&, DCOPClient::ReplyStruct*, bool, int, int) (this=0x8054fe0, remApp=@0x8, remObjId=@0x8, remFun=@0xfffffe00, data=@0xbff12a60, replyStruct=0xbff12890, useEventLoop=false, timeout=-1, minor_opcode=2) at dcopclient.cpp:1930 #7 0xb7465cc7 in DCOPClient::callInternal(QCString const&, QCString const&, QCString con st&, QMemArray<char> const&, QCString&, QMemArray<char>&, bool, int, int) ( this=0xfffffe00, remApp=@0xfffffe00, remObjId=@0xfffffe00, remFun=@0xfffffe00, data=@0xfffffe00, replyType=@0xfffffe00, replyData=@0xfffffe00, useEventLoop=false, timeout=-512, minor_opcode=-512) at dcopclient.cpp:1821 #8 0xb74693fb in DCOPClient::call(QCString const&, QCString const&, QCString const&, QMe ---Type <return> to continue, or q <return> to quit--- mArray<char> const&, QCString&, QMemArray<char>&, bool, int) (this=0x8054fe0, remApp=@0xbff12a10, remObjId=@0xbff12a20, remFun=@0xbff12a30, data=@0xbff12a60, replyType=@0xbff12a40, replyData=@0xbff12a50, useEventLoop=false, timeout=-512) at dcopclient.cpp:1764 #9 0xb7469467 in DCOPClient::call(QCString const&, QCString const&, QCString const&, QMe mArray<char> const&, QCString&, QMemArray<char>&, bool) (this=0xfffffe00, remApp=@0xfffffe00, remObjId=@0xfffffe00, remFun=@0xfffffe00, data=@0xfffffe00, replyType=@0xfffffe00, replyData=@0xfffffe00, useEventLoop=false) at dcopclient.cpp:1730 #10 0xb6d75416 in KIMIface_stub::allContacts() (this=0x823c578) at kimiface_stub.cpp:39 #11 0xb6d76ae6 in KIMProxy::pollApp(QCString const&) (this=0x82314e0, appId=@0x823c540) at kimproxy.cpp:598 #12 0xb6d77825 in KIMProxy::initialize() (this=0x82314e0) at kimproxy.cpp:255 #13 0xb71e9ef0 in KMetaMenu::KMetaMenu(QWidget*, KURL const&, QString const&, QString con st&, KIMProxy*) () from /usr/kde/3.5/lib/kde3/libkuickplugin.so #14 0xffffffff in ?? () #15 0xffffffff in ?? () #16 0xbff12d90 in ?? () #17 0x4fab0ff4 in ?? () from /lib/libpthread.so.0 #18 0xbff12e50 in ?? () #19 0xbff12e40 in ?? () ---Type <return> to continue, or q <return> to quit--- #20 0xbff12d58 in ?? () #21 0xbff12f30 in ?? () #22 0xbff12f20 in ?? () #23 0x082093cc in ?? () #24 0xbff12f10 in ?? () #25 0x4fab0ff4 in ?? () from /lib/libpthread.so.0 #26 0xbff12ed0 in ?? () #27 0xb71eec5a in typeinfo name for KGenericFactory<KTestMenu, KonqPopupMenu> () from /usr/kde/3.5/lib/kde3/libkuickplugin.so #28 0xbff12ea0 in ?? () #29 0x4faa928f in pthread_mutex_unlock () from /lib/libpthread.so.0 Previous frame inner to this frame (corrupt stack?) According to equery, libkuickplugin.so belongs to a konqueror plugin. Maybe this is a plugin that adds entries to the RMB menu?
*** This bug has been confirmed by popular vote. ***
I've a new complete backtrace for you, my kdesktop freezes and crashes now when I launch "kill -SEGV <pid-of-kdesktop>" : Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1500940064 (LWP 6574)] [KCrash handler] #6 0xffffe40e in __kernel_vsyscall () #7 0xa7d4dc43 in read () from /lib/tls/i686/cmov/libc.so.6 #8 0xa6ae5eee in _kde_IceTransSocketRead (ciptr=0x3, buf=0x3 <Address 0x3 out of bounds>, size=3) at Xtranssock.c:1710 #9 0xa6ae635f in _kde_IceTransRead (ciptr=0x8, buf=0x3 <Address 0x3 out of bounds>, size=3) at Xtrans.c:845 #10 0xa6adee7f in _kde_IceRead (iceConn=0x80a6b58, nbytes=8, ptr=0x80a6d48 "\002\003") at /build/buildd/kdelibs-3.5.2/./dcop/KDE-ICE/misc.c:249 #11 0xa6adf4bf in KDE_IceProcessMessages (iceConn=0x80a6b58, replyWait=0xafc4c038, replyReadyRet=0xafc4c088) at /build/buildd/kdelibs-3.5.2/./dcop/KDE-ICE/process.c:153 #12 0xa6ad34c1 in DCOPClient::callInternal (this=0x80a6400, remApp=@0x8, remObjId=@0x8, remFun=@0x3, data=@0xafc4c234, replyStruct=0xafc4c0e4, useEventLoop=false, timeout=-1, minor_opcode=2) at dcopclient.cpp:1931 #13 0xa6ad36e6 in DCOPClient::callInternal (this=0x3, remApp=@0x3, remObjId=@0x3, remFun=@0x3, data=@0x3, replyType=@0x3, replyData=@0x3, useEventLoop=false, timeout=3, minor_opcode=3) at dcopclient.cpp:1821 #14 0xa6ad3d43 in DCOPClient::call (this=0x80a6400, remApp=@0xafc4c24c, remObjId=@0xafc4c244, remFun=@0xafc4c23c, data=@0xafc4c234, replyType=@0xafc4c224, replyData=@0xafc4c22c, useEventLoop=false, timeout=3) at dcopclient.cpp:1765 #15 0xa6ad3da8 in DCOPClient::call (this=0x3, remApp=@0x3, remObjId=@0x3, remFun=@0x3, data=@0x3, replyType=@0x3, replyData=@0x3, useEventLoop=false) at dcopclient.cpp:1730 #16 0xa5d199fd in KIMIface_stub::allContacts (this=0x83db300) at kimiface_stub.cpp:39 #17 0xa5d1704e in KIMProxy::pollApp (this=0x83cd2f0, appId=@0x83d95b0) at kimproxy.cpp:598 #18 0xa5d1771d in KIMProxy::initialize (this=0x83cd2f0) at kimproxy.cpp:255 #19 0xa534087b in KMetaMenu::KMetaMenu () from /usr/lib/kde3/libkuickplugin.so #20 0xa5341b4c in KTestMenu::slotPrepareMenu () from /usr/lib/kde3/libkuickplugin.so #21 0xa5341fab in KTestMenu::qt_invoke () from /usr/lib/kde3/libkuickplugin.so #22 0xa722b54b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #23 0xa722bfdc in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #24 0xa75d7c11 in QPopupMenu::aboutToShow () from /usr/lib/libqt-mt.so.3 #25 0xa7350699 in QPopupMenu::popup () from /usr/lib/libqt-mt.so.3 #26 0xa7355061 in QPopupMenu::exec () from /usr/lib/libqt-mt.so.3 #27 0xa65e80b9 in KDIconView::popupMenu () from /usr/lib/libkdeinit_kdesktop.so #28 0xa65e826a in KDIconView::slotContextMenuRequested () from /usr/lib/libkdeinit_kdesktop.so #29 0xa660072f in KDIconView::qt_invoke () from /usr/lib/libkdeinit_kdesktop.so #30 0xa722b54b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #31 0xa75f25b3 in QIconView::contextMenuRequested () from /usr/lib/libqt-mt.so.3 #32 0xa74213f8 in QIconView::contentsContextMenuEvent () from /usr/lib/libqt-mt.so.3 #33 0xa735ffcc in QScrollView::viewportContextMenuEvent () from /usr/lib/libqt-mt.so.3 #34 0xa73626ab in QScrollView::eventFilter () from /usr/lib/libqt-mt.so.3 #35 0xa7416630 in QIconView::eventFilter () from /usr/lib/libqt-mt.so.3 #36 0xa72286b0 in QObject::activate_filters () from /usr/lib/libqt-mt.so.3 #37 0xa722872e in QObject::event () from /usr/lib/libqt-mt.so.3 #38 0xa7265b9a in QWidget::event () from /usr/lib/libqt-mt.so.3 #39 0xa71c187a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #40 0xa71c2271 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #41 0xa789802e in KApplication::notify (this=0xafc4d9e0, receiver=0x8130398, event=0xafc4d35c) at kapplication.cpp:550 #42 0xa715306f in QApplication::sendSpontaneousEvent () from /usr/lib/libqt-mt.so.3 #43 0xa714e801 in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3 #44 0xa714cc94 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #45 0xa71662a2 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #46 0xa71da255 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #47 0xa71da17a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #48 0xa71c038d in QApplication::exec () from /usr/lib/libqt-mt.so.3 #49 0xa65fe12f in kdemain () from /usr/lib/libkdeinit_kdesktop.so #50 0xa7f31524 in kdeinitmain () from /usr/lib/kde3/kdesktop.so #51 0x0804e1d6 in launch (argc=1, _name=0x80a31a4 "kdesktop", args=0x80a31ad "", cwd=0x0, envc=0, envs=0x80a31b1 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x3 <Address 0x3 out of bounds>) at kinit.cpp:639 #52 0x0804e897 in handle_launcher_request (sock=8) at kinit.cpp:1205 #53 0x0804ee13 in handle_requests (waitForPid=0) at kinit.cpp:1406 #54 0x0804fe9b in main (argc=2, argv=0xafc4e384, envp=0x3) at kinit.cpp:1850 #55 0xa7ca0eb0 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #56 0x0804b861 in _start () at ../sysdeps/i386/elf/start.S:119
as Harm van Bakel discovered, kopete seems responsible for the freezing of kdesktop: https://launchpad.net/distros/ubuntu/+source/kdebase/+bug/43065 after the desktop freezes, a "killall kopete" brings kdesktop back to its normal state. after killing kopete, the following messages are appearing in ~/.xsession-errors: DCOP aborting call from 'kdesktop' to 'kopete' DCOP aborting while waiting for answer from 'kdesktop' DCOPServer::DCOPReply for unknown connection. In contrast to the reports above, I was never able to generate backtraces of kdesktop during its freezed state.
Here is a backtrace of kopete, if that helps: (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1241172288 (LWP 6262)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xffffe40e in __kernel_vsyscall () #7 0xb641756b in __read_nocancel () from /lib/tls/i686/cmov/libpthread.so.0 #8 0xb6f30a71 in _kde_IceTransFreeConnInfo () from /usr/lib/libDCOP.so.4 #9 0xb6f30e41 in _kde_IceTransRead () from /usr/lib/libDCOP.so.4 #10 0xb6f29b95 in _kde_IceRead () from /usr/lib/libDCOP.so.4 #11 0xb6f2a149 in KDE_IceProcessMessages () from /usr/lib/libDCOP.so.4 #12 0xb6f1ecf8 in DCOPClient::callInternal () from /usr/lib/libDCOP.so.4 #13 0xb6f1ef24 in DCOPClient::callInternal () from /usr/lib/libDCOP.so.4 #14 0xb6f1f540 in DCOPClient::call () from /usr/lib/libDCOP.so.4 #15 0xb6f211f8 in DCOPRef::callInternal () from /usr/lib/libDCOP.so.4 #16 0xb6f21300 in DCOPRef::callInternal () from /usr/lib/libDCOP.so.4 #17 0xb7e9b063 in Kopete::Away::slotTimerTimeout () from /usr/lib/libkopete.so.1 #18 0xb7e9b296 in Kopete::Away::qt_invoke () from /usr/lib/libkopete.so.1 #19 0xb699fe29 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #20 0xb69a08c4 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #21 0xb6d34f1e in QTimer::timeout () from /usr/lib/libqt-mt.so.3 #22 0xb69c4e21 in QTimer::event () from /usr/lib/libqt-mt.so.3 #23 0xb6935dc6 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #24 0xb6935fc2 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #25 0xb70b8e31 in KApplication::notify () from /usr/lib/libkdecore.so.4 #26 0xb68c70ef in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #27 0xb69277b3 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #28 0xb68daeff in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #29 0xb694e8b7 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #30 0xb694e7da in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #31 0xb69348d5 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #32 0x08078c52 in ?? () #33 0xbfc6bd30 in ?? () #34 0xbfc6be64 in ?? () #35 0xbfc6be5c in ?? () #36 0x00000000 in ?? () I'm now using kde-3.5.3/kopete-0.11.3 (kubuntu packages) and kopete was always connected to AIM (not tested it without connection)
You are right! I did not have Kopete loaded for two weeks now, and the freezes were gone. I just loaded Kopete again, and after right-clicking KDesktop icons about 20 times, KDesktop froze again. Killing Kopete unlocks the desktop again. I do not get any relevant messages in my .xsession-errors, because Kopete has no debug info on my setup. My backtrace: 0xffffe410 in ?? () (gdb) backtrace #0 0xffffe410 in ?? () #1 0xbfeff9c8 in ?? () #2 0x00000008 in ?? () #3 0x0812d998 in ?? () #4 0xb65784db in __read_nocancel () from /lib/tls/libpthread.so.0 #5 0xb6dc7a1e in _kde_IceTransSocketRead (ciptr=0xfffffe00, buf=0xfffffe00 <Address 0xfffffe00 out of bounds>, size=-512) at Xtranssock.c:1710 #6 0xb6dc7e7f in _kde_IceTransRead (ciptr=0x8, buf=0xfffffe00 <Address 0xfffffe00 out of bounds>, size=-512) at Xtrans.c:845 #7 0xb6dc061c in _kde_IceRead (iceConn=0x812d7c0, nbytes=8, ptr=0x812d998 "\002\002") at misc.c:249 #8 0xb6dc0be6 in KDE_IceProcessMessages (iceConn=0x812d7c0, replyWait=0xbfeffb60, replyReadyRet=0xbfeffacc) at process.c:153 #9 0xb6dac8c7 in DCOPClient::callInternal(QCString const&, QCString const&, QCString const&, QMemArray<char> const&, DCOPClient::ReplyStruct*, bool, int, int) (this=0x812d1d0, remApp=@0x8, remObjId=@0x8, remFun=@0xfffffe00, data=@0xbfeffe00, replyStruct=0xbfeffc10, useEventLoop=false, timeout=-1, minor_opcode=2) at dcopclient.cpp:1930 #10 0xb6daccd7 in DCOPClient::callInternal(QCString const&, QCString const&, QCString const&, QMemArray<char> const&, QCString&, QMemArray<char>&, bool, int, int) ( this=0xfffffe00, remApp=@0xfffffe00, remObjId=@0xfffffe00, remFun=@0xfffffe00, ---Type <return> to continue, or q <return> to quit--- data=@0xfffffe00, replyType=@0xfffffe00, replyData=@0xfffffe00, useEventLoop=false, timeout=-512, minor_opcode=-512) at dcopclient.cpp:1821 #11 0xb6db040b in DCOPClient::call(QCString const&, QCString const&, QCString const&, QMemArray<char> const&, QCString&, QMemArray<char>&, bool, int) (this=0x812d1d0, remApp=@0xbfeffe40, remObjId=@0xbfeffe48, remFun=@0xbfeffd40, data=@0xbfeffe00, replyType=@0xbfeffe18, replyData=@0xbfeffe10, useEventLoop=false, timeout=-512) at dcopclient.cpp:1764 #12 0xb6db28f9 in DCOPRef::callInternal(QCString const&, QCString const&, QMemArray<char> const&, DCOPRef::EventLoopFlag, int) (this=0xbfeffe40, fun=@0x812d1d0, args=@0xbfeffe30, data=@0xfffffe00, useEventLoop=NoEventLoop, timeout=-512) at dcopref.cpp:77 #13 0xb6db298e in DCOPRef::callInternal(QCString const&, QCString const&, QMemArray<char> const&) (this=0xfffffe00, fun=@0xfffffe00, args=@0xfffffe00, data=@0xfffffe00) at dcopref.cpp:52 #14 0x4f47511a in Kopete::Away::slotTimerTimeout() () from /usr/kde/3.5/lib/libkopete.so.1 #15 0xbfeffe00 in ?? () #16 0x0000000f in ?? () #17 0x0828feb4 in ?? () #18 0xb735ef0c in ?? () from /usr/kde/3.5/lib/libkdeui.so.4
Yes, it's true !!! At last, we have found the origin of this problem. It's necessary to change this bug's category, it's a kopete bug, not a kdesktop bug. Could someone change the category ?
bug is already report here http://bugs.kde.org/show_bug.cgi?id=127749 as a kopete bug
A more detailed backtrace, this time with debug info compiled into Kopete: 0xffffe410 in ?? () (gdb) backtrace #0 0xffffe410 in ?? () #1 0xbf8d6238 in ?? () #2 0x00000008 in ?? () #3 0xb6d47e7f in _kde_IceTransRead (ciptr=0x8, buf=0xfffffe00 <Address 0xfffffe00 out of bounds>, size=-512) at Xtrans.c:845 #4 0xb6d4061c in _kde_IceRead (iceConn=0x81347c0, nbytes=8, ptr=0x8134998 "\002\002") at misc.c:249 #5 0xb6d40be6 in KDE_IceProcessMessages (iceConn=0x81347c0, replyWait=0xbf8d63d0, replyReadyRet=0xbf8d633c) at process.c:153 #6 0xb6d2c8c7 in DCOPClient::callInternal(QCString const&, QCString const&, QCString const&, QMemArray<char> const&, DCOPClient::ReplyStruct*, bool, int, int) (this=0x81341d0, remApp=@0x8, remObjId=@0x8, remFun=@0xfffffe00, data=@0xbf8d6650, replyStruct=0xbf8d6480, useEventLoop=false, timeout=-1, minor_opcode=2) at dcopclient.cpp:1930 #7 0xb6d2ccd7 in DCOPClient::callInternal(QCString const&, QCString const&, QCString const&, QMemArray<char> const&, QCString&, QMemArray<char>&, bool, int, int) ( this=0xfffffe00, remApp=@0xfffffe00, remObjId=@0xfffffe00, remFun=@0xfffffe00, data=@0xfffffe00, replyType=@0xfffffe00, replyData=@0xfffffe00, useEventLoop=false, timeout=-512, minor_opcode=-512) at dcopclient.cpp:1821 #8 0xb6d3040b in DCOPClient::call(QCString const&, QCString const&, QCString const&, QMemArray<char> const&, QCString&, QMemArray<char>&, bool, int) (this=0x81341d0, ---Type <return> to continue, or q <return> to quit--- remApp=@0xbf8d66d0, remObjId=@0xbf8d66d8, remFun=@0xbf8d65b0, data=@0xbf8d6650, replyType=@0xbf8d66a8, replyData=@0xbf8d66a0, useEventLoop=false, timeout=-512) at dcopclient.cpp:1764 #9 0xb6d328f9 in DCOPRef::callInternal(QCString const&, QCString const&, QMemArray<char> const&, DCOPRef::EventLoopFlag, int) (this=0xbf8d66d0, fun=@0x81341d0, args=@0xbf8d6640, data=@0xfffffe00, useEventLoop=NoEventLoop, timeout=-512) at dcopref.cpp:77 #10 0xb6d3298e in DCOPRef::callInternal(QCString const&, QCString const&, QMemArray<char> const&) (this=0xfffffe00, fun=@0xfffffe00, args=@0xfffffe00, data=@0xfffffe00) at dcopref.cpp:52 #11 0xb7f219e1 in DCOPRef::call(QCString const&) (this=0xfffffe00, fun=@0xfffffe00) at dcopref.h:419 #12 0xb7ef4682 in Kopete::Away::slotTimerTimeout() (this=0x82bacd8) at kopeteaway.cpp:291 #13 0xb7ef47dc in Kopete::Away::qt_invoke(int, QUObject*) (this=0x82bacd8, _id=2, _o=0xfffffe00) at kopeteaway.moc:106 #14 0xb6829c24 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/qt/3/lib/libqt-mt.so.3 #15 0xb682a342 in QObject::activate_signal(int) () from /usr/qt/3/lib/libqt-mt.so.3 #16 0xb6b83049 in QTimer::timeout() () from /usr/qt/3/lib/libqt-mt.so.3 #17 0xb684b80e in QTimer::event(QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 ---Type <return> to continue, or q <return> to quit--- #18 0xb67c55ff in QApplication::internalNotify(QObject*, QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #19 0xb67c579c in QApplication::notify(QObject*, QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #20 0xb6f01c15 in KApplication::notify(QObject*, QEvent*) (this=0xbf8d6df0, receiver=0x828a290, event=0xbf8d6b70) at kapplication.cpp:550 #21 0xb67b8a4c in QEventLoop::activateTimers() () from /usr/qt/3/lib/libqt-mt.so.3 #22 0xb6771cfb in QEventLoop::processEvents(unsigned) () from /usr/qt/3/lib/libqt-mt.so.3 #23 0xb67dbcd2 in QEventLoop::enterLoop() () from /usr/qt/3/lib/libqt-mt.so.3 #24 0xb67dbc26 in QEventLoop::exec() () from /usr/qt/3/lib/libqt-mt.so.3 #25 0xb67c47af in QApplication::exec() () from /usr/qt/3/lib/libqt-mt.so.3 #26 0x08082dcd in main (argc=-512, argv=0xfffffe00) at main.cpp:103 I think this is enough evidence to assign this bug to Kopete. Maybe it should have a higher severity settings as well, as if freezes a large part of the KDE desktop. *** This bug has been marked as a duplicate of 127749 ***
Bug closed. Kdesktop is no more mantained.