PDA

View Full Version : Kopete crashing when connecting to MSN - only on KDE 3.5.8


UrbanSlayer
October 16th, 2007, 08:00 PM
As above, whenever I launch Kopete after updating to KDE 3.5.8 today on both my desktop (an upgrade from Feisty) and laptop (clean install of Gutsy about 3 days ago, updated tonight) if I allow it to connect to MSN, it crashes with the following -

The application Kopete crashed and caused the signal 11 (SIGSEGV).

Details of the Backtrace follow -

(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)
[Thread debugging using libthread_db enabled]
[New Thread -1242023440 (LWP 8801)]
(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)
[KCrash handler]
#6 0xb58bb11a in MSNAccount::slotNotifySocketClosed ()
from /usr/lib/libkopete_msn_shared.so.0
#7 0xb58c3668 in MSNAccount::qt_invoke ()
from /usr/lib/libkopete_msn_shared.so.0
#8 0xb6823893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#9 0xb6824338 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#10 0xb58cc8dc in MSNSocket::socketClosed ()
from /usr/lib/libkopete_msn_shared.so.0
#11 0xb58e04cd in MSNNotifySocket::disconnect ()
from /usr/lib/libkopete_msn_shared.so.0
#12 0xb58dcf3b in MSNNotifySocket::sslLoginFailed ()
from /usr/lib/libkopete_msn_shared.so.0
#13 0xb58e30f5 in MSNNotifySocket::qt_invoke ()
from /usr/lib/libkopete_msn_shared.so.0
#14 0xb6823893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#15 0xb6824338 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#16 0xb58fd16c in MSNSecureLoginHandler::loginFailed ()
from /usr/lib/libkopete_msn_shared.so.0
#17 0xb58fd40f in MSNSecureLoginHandler::slotTweenerReceived ()
from /usr/lib/libkopete_msn_shared.so.0
#18 0xb58fe5a6 in MSNSecureLoginHandler::qt_invoke ()
from /usr/lib/libkopete_msn_shared.so.0
#19 0xb6823893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#20 0xb745e021 in KIO::Job::result () from /usr/lib/libkio.so.4
#21 0xb74b68cd in KIO::Job::emitResult () from /usr/lib/libkio.so.4
#22 0xb74b6d2e in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.4
#23 0xb74b743d in KIO::TransferJob::slotFinished () from /usr/lib/libkio.so.4
#24 0xb74b6301 in KIO::SimpleJob::qt_invoke () from /usr/lib/libkio.so.4
#25 0xb74b6363 in KIO::TransferJob::qt_invoke () from /usr/lib/libkio.so.4
#26 0xb6823893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#27 0xb6baf8ec in QSignal::signal () from /usr/lib/libqt-mt.so.3
#28 0xb6843842 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#29 0xb684b258 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#30 0xb67baaf0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#31 0xb67bc91f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#32 0xb6f80ca2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#33 0xb674d209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#34 0xb67ad53b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#35 0xb6761d49 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#36 0xb67d51ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#37 0xb67d4fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#38 0xb67bc699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#39 0x0807f95c in ?? ()
#40 0xbfa64394 in ?? ()
#41 0xbfa6438c in ?? ()
#42 0xbfa64384 in ?? ()
#43 0x00000000 in ?? ()

This only happens when connecting to MSN, if I dont connect to MSN it works fine. Also, until I upgraded my laptop tonight to KDE 3.5.8 from 3.5.7 that Gutsy had initially installed, all was ok. Now, it doesnt matter which version of Kopete I use.

Ive searched, but I cant find a bug on this, has anyone else had this problem? If not, I'll raise a new bug report (but under what, Kopete or KDE?).

Cheers.

KLineD
October 16th, 2007, 11:06 PM
I can confirm this bug. It happens only with the latest update. I have another machine running gutsy without today's updates and kopete runs fine.

k_f
October 16th, 2007, 11:38 PM
Confirmed. Same thing happens to me too after upgrade to 3.5.8.

High Roller
October 17th, 2007, 12:47 AM
Confirmed here as well. Bug is open at: https://bugs.launchpad.net/ubuntu/+source/kopete/+bug/149263

**edit: I'm wondering if there's an updated Kopete package that has been withheld or "in the pipes" and the updated KDE is incompatible with the older Kopete. But this close to release it makes me leary.

ramibotros
October 17th, 2007, 07:37 AM
confirmed .. will go confirm it on the bugs page

XenThraL
October 17th, 2007, 09:57 AM
Confirmed here as well

phew, thought _I_ had screwed something up somehow

jakster
October 17th, 2007, 10:15 AM
Confirmed, crashes only with MSN. Doesn't matter if I remove kopeterc or the kopete directory in ~/.kde/share/apps

crozar
October 17th, 2007, 03:12 PM
i confirm on this

the last gutsy update on early 17th of October have made this protocol mess

diJenerate
October 17th, 2007, 10:07 PM
Get the fix here (http://www.kdedevelopers.org/node/3041).

diJenerate

pyrrhicvictory
October 18th, 2007, 12:26 AM
It is an i386 package... Im running amd64. Id much rather have a 64 bit package.

revenant_org
October 18th, 2007, 03:36 AM
It is an i386 package... Im running amd64. Id much rather have a 64 bit package.
me too plz.:popcorn:

XenThraL
October 18th, 2007, 05:55 AM
me too

XenThraL
October 18th, 2007, 06:03 AM
oops, seemes its here, link found on the bug report
http://launchpadlibrarian.net/10054427/Archive.tar.bz2

Mr. Dude
October 18th, 2007, 08:01 AM
The .deb did nothing =(

hypnoticmorpheus
October 18th, 2007, 08:10 AM
64bit deb did the trick for me. Is this new deb also in the final version?
And I am wondering why it did not come in through the repos. Have not seen an update today.

Mr. Dude
October 18th, 2007, 08:24 AM
For some unknown reason, gDebi didn't install it properly, yet it said it had. I decided to install it from the command line (had been a while) and it worked perfectly =]