Version: unknown (using KDE 3.5.2, Gentoo) Compiler: gcc version 3.3.6 (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7.8) OS: Linux (i686) release 2.6.16-suspend2-r5-justbudget I installed the latest SVN of /branches/kopete/0.12 to test latest jingle and it was crashing on me on startup. unfortunatelly the backtrace was never totally readable. so I decided to reinstaller 0.12beta2. and now this one crash as well, while it was working fine before. could be something special about my config, i'm not sure. here is the backtrace with kopete 0.12beta2 System configuration startup check disabled. Using host libthread_db library "/lib/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 3447)] [KCrash handler] #6 0xbfe68826 in ?? () #7 0x08680c68 in ?? () #8 0xb65c6818 in QObject (this=0x8680c68, parent=0xbfe687c8, name=0x0) at qobject.cpp:407 #9 0xb7e5f916 in Contact (this=0x8680c68, account=0xbfe68810, contactId=@0x8675640, parent=0xbfe687c8, icon=@0x812c088) at kopetecontact.cpp:84 #10 0xb529d6f9 in OscarContact (this=0x8680c68, account=0xbfe68810, name=@0x8675640, parent=0xbfe687c8, icon=@0x812c088, ssiItem=@0x80773f5) at oscarcontact.cpp:49 #11 0xb46b6014 in AIMContact (this=0x8680c68, account=0xbfe68821, name=@0xbfe68821, parent=0xbfe68821, icon=@0xbfe68821, ssiItem=@0xbfe68821) at aimcontact.cpp:49 #12 0xb46ae36d in AIMAccount::createNewContact (this=0xbfe68821, contactId=@0xbfe68821, parentContact=0xbfe68821, ssiItem=@0x80773f5) at aimaccount.cpp:238 #13 0xb7eb2c1d in Kopete::PasswordedAccount::connect (this=0x8675640, initialStatus=@0xbfe68850) at kopetepasswordedaccount.cpp:74 #14 0xb7e91529 in Kopete::AccountManager::connectAll (this=0x8283048) at kopeteaccountmanager.cpp:102 #15 0x08075d81 in KopeteApplication::slotAllPluginsLoaded (this=0xbfe69190) at kopeteapplication.cpp:215 #16 0x0807661a in KopeteApplication::qt_invoke (this=0xbfe69190, _id=23, _o=0xbfe68a40) at kopeteapplication.moc:94 #17 0xb65ca7e6 in QObject::activate_signal (this=0x82b1720, clist=0x833e5e8, o=0xbfe68a40) at qobject.cpp:2379 #18 0xb65ca504 in QObject::activate_signal (this=0x82b1720, signal=3) at qobject.cpp:2324 #19 0xb7e68ab5 in Kopete::PluginManager::allPluginsLoaded (this=0x82b1720) at kopetepluginmanager.moc:154 #20 0xb7e679f3 in Kopete::PluginManager::slotLoadNextPlugin (this=0x82b1720) at kopetepluginmanager.cpp:314 #21 0xb7e68c6a in Kopete::PluginManager::qt_invoke (this=0x82b1720, _id=10, _o=0xbfe68b80) at kopetepluginmanager.moc:168 #22 0xb65ca6ac in QObject::activate_signal (this=0x8292038, clist=0x87f6220, o=0xbfe68b80) at qobject.cpp:2355 #23 0xb69adb47 in QSignal::signal (this=0x8292038, t0=@0x8292060) at moc_qsignal.cpp:100 #24 0xb65ec56b in QSignal::activate (this=0x8292038) at qsignal.cpp:212 #25 0xb65f6478 in QSingleShotTimer::event (this=0x8292010) at qtimer.cpp:286 #26 0xb655a235 in QApplication::internalNotify (this=0xbfe69190, receiver=0x8292010, e=0xbfe68ee0) at qapplication.cpp:2635 #27 0xb6559478 in QApplication::notify (this=0xbfe69190, receiver=0x8292010, e=0xbfe68ee0) at qapplication.cpp:2358 #28 0xb6da1ddf in KApplication::notify (this=0xbfe69190, receiver=0x8292010, event=0xbfe68ee0) at kapplication.cpp:550 #29 0xb79ee62b in QApplication::sendEvent (receiver=0xbfe68821, event=0xb5ed2a02) at qapplication.h:491 #30 0xb654575f in QEventLoop::activateTimers (this=0x822f2e0) at qeventloop_unix.cpp:556 #31 0xb64f5d5d in QEventLoop::processEvents (this=0x822f2e0, flags=4) at qeventloop_x11.cpp:389 #32 0xb65717d9 in QEventLoop::enterLoop (this=0x822f2e0) at qeventloop.cpp:198 #33 0xb65716f2 in QEventLoop::exec (this=0x822f2e0) at qeventloop.cpp:145 #34 0xb655a3d7 in QApplication::exec (this=0xbfe69190) at qapplication.cpp:2758 #35 0x080752cc in main (argc=7, argv=0xbfe69314) at main.cpp:107
can you move your current config (probably your contactlist too) somewhere else and then start over with a new config and if there's no crash, do a diff between the two? If you need guidance to make sure that you don't lose any of your data, please let us know.
I tried keeping my contact list(share/apps/kopete* folders) and only drop the config, it would not crash on startup, but it crash when I create my first account and try to connect. can I recreate all from scratch but keep my chat history ?
I kill both the config and the apps folders nothing left about kopete under my .kde folder. created a jabber account (google) and it crash on connect again. System configuration startup check disabled. Using host libthread_db library "/lib/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [KCrash handler] #19 0x00000000 in ?? () #20 0xb7ea3c1d in ?? () #21 0xbfb55fb0 in ?? () #22 0x083c2100 in ?? () #23 0xbfb55f78 in ?? () #24 0x080a23c8 in KopeteMetaLVIProps::slotEnableAndDisableWidgets ( this=0x83c2100) at kopetelviprops.cpp:343 #25 0x0808abe9 in KIMIface::process (this=0x831ed68, fun=@0x0, data=@0xbfb56088, replyType=@0x2, replyData=@0x82e4d00) at kimiface_skel.cpp:101 #26 0xb69d5271 in ?? () #27 0x0831ed68 in ?? () #28 0x00000000 in ?? () #29 0xbfb56088 in ?? () #30 0x00000002 in ?? () #31 0xb6bb3c40 in ?? () #32 0xbfb560a8 in ?? () #33 0xb69d9eb1 in ?? () #34 0x0831ed68 in ?? () #35 0x0000002f in ?? ()
I restarted from scratch again, starting with msn account this time, worked fine. created AOL account, kopete crashed. System configuration startup check disabled. Using host libthread_db library "/lib/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [KCrash handler] #20 0x088af282 in ?? () #21 0xb665d818 in ?? () #22 0xbfefb578 in ?? () #23 0x083a6370 in ?? () #24 0x000069cc in ?? () #25 0x00000000 in ?? () #26 0x083a6370 in ?? () #27 0xb7fa4310 in ?? () #28 0xbfefb458 in ?? () #29 0xb7ef3916 in ?? () #30 0x083a6370 in ?? () #31 0xbfefb578 in ?? () #32 0x00000000 in ?? () #33 0x00000000 in ?? () #34 0xb51c852c in ?? () #35 0xb52033d4 in ?? () #36 0x000003f7 in ?? () #37 0xb4856834 in ?? () #38 0x083a6370 in ?? () #39 0x083a6478 in ?? () #40 0xbfefb478 in ?? () #41 0xb47d06f9 in ?? () #42 0x083a6370 in ?? () #43 0xbfefb5b0 in ?? () #44 0x088af280 in ?? () #45 0xbfefb578 in ?? () #46 0x0810d828 in QLAYOUTSIZE_MAX () #47 0xb5202a88 in ?? () #48 0xbfefb4c8 in ?? () #49 0xb51ec014 in ?? () #50 0x083a6370 in ?? () #51 0xbfefb5b0 in ?? () #52 0x088af280 in ?? () #53 0xbfefb578 in ?? () #54 0x0810d828 in QLAYOUTSIZE_MAX () #55 0x080a23c8 in KopeteMetaLVIProps::slotEnableAndDisableWidgets ( this=0x83a6370) at kopetelviprops.cpp:343
creating jabber (jabber.org or google) or AIM account make kopete 0.12 SVN crash. if it does not for you, i dont know what is special about my install. I compiled kopete with ./configure --debug=full --enable-jingle && make && su -c 'make install'
Your backtraces look pretty useless. You used "--debug=full" instead of "--enable-debug=full".
my bad actually config.log says It was created by configure, which was generated by GNU Autoconf 2.59. Invocation command line was $ ./configure --enable-jingle --enable-debug=full but I'll redo it again, just to make sure.
I dont know why my backtrace are screwed. I recompiled again, using --enable-debug=full and all I get is this. System configuration startup check disabled. Using host libthread_db library "/lib/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [KCrash handler] #19 0x00000000 in ?? () #20 0xb7eccc1d in ?? () #21 0xbfd81060 in ?? () #22 0x085e6168 in ?? () #23 0xbfd81028 in ?? () #24 0x080a23c8 in KopeteMetaLVIProps::slotEnableAndDisableWidgets ( this=0x85e6168) at kopetelviprops.cpp:343 #25 0x0808abe9 in KIMIface::process (this=0x843a108, fun=@0x0, data=@0xbfd81138, replyType=@0x2, replyData=@0x85779f8) at kimiface_skel.cpp:101 #26 0xb69fe271 in ?? () #27 0x0843a108 in ?? () #28 0x00000000 in ?? () #29 0xbfd81138 in ?? () #30 0x00000002 in ?? () #31 0xb6bdcc40 in ?? () #32 0xbfd81158 in ?? () #33 0xb6a02eb1 in ?? () #34 0x0843a108 in ?? () #35 0x0000002f in ?? () my entire KDE is compiled with debug symbols and my backtrace used to be perfect. I dont know what could have went wrong.
I tried running it under valgrind 2.4.0 valgrind -v --num-callers=12 kopete --nofork but it so slow, the UI freeze, it did not get to the point to load existing MSN account. and the UI would not unfreeze. so I could not create the jabber account for testing. I let it run more than half an hour. stayed frozen, I'm doing another try and I will upgrade valgrind to 3.1.1 maybe it will be better.
Created attachment 16322 [details] valgrind 2.4.0 outout I waited long enough and finally went through. I hope this is usefull.
want a funny backtrace ? took a very long time to generate, although its very tiny ;) I was trying to use msn(since jabber does not work), send message, close window, open window..... System configuration startup check disabled. Using host libthread_db library "/lib/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 9040)] [New Thread 32769 (LWP 9041)] [KCrash handler] #7 0x08628047 in ?? () #8 0xb7e37b23 in Kopete::Contact::execute (this=0xffffdd76) at kopetecontact.cpp:447
I guess that you have some binary incompatibilities. make sure to type make clean before compiling again. and make sure the --prefix , the $PATH , the $LD_LIBRARY_PATH are set correctly.
I cannot reproduce.
Same happens on my setup. I am using SuSE 10.1, comes with kopete 0.11.1. I downloaded both the 0.12.0 release and svn (on 22 June 06) and it crashes immediately on startup. How do I provide you with a backtrace? I configured with ./configure --enable-debug=full --prefix=$HOME/kopete --enable-jingle I also tried installing to a local directory as outlined on the kopete webpage, same thing happens.
try uninstalling kdenetwork and/or the old kopete and reinstall 0.12
OK, this seems to fix the problem. thanks! On 23 Jun 2006 00:18:08 -0000, Mathieu Jobin <somekool@somekool.net> wrote: [bugs.kde.org quoted mail] OK, this seems to fix the problem.<br>thanks!<br><br><div><span class="gmail_quote">On 23 Jun 2006 00:18:08 -0000, <b class="gmail_sendername">Mathieu Jobin</b> <<a href="mailto:somekool@somekool.net">somekool@somekool.net </a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">------- You are receiving this mail because: -------<br>You are a voter for the bug, or are watching someone who is. <br><br><a href="http://bugs.kde.org/show_bug.cgi?id=128160">http://bugs.kde.org/show_bug.cgi?id=128160</a><br><br><br><br><br>------- Additional Comments From somekool somekool net 2006-06-23 02:18 -------<br>try uninstalling kdenetwork and/or the old kopete and reinstall 0.12<br></blockquote></div><br>
I think this bug could be reopen, kopete 0.12 should not crash because 0.11 is there. what kinda files enter in conflicts ? should not it only use library in the same PREFIX path ? why does old files creates this problem, can:t this be fixed ?