Bug 132299 - Kopete crashes by using Jingle
Summary: Kopete crashes by using Jingle
Status: RESOLVED REMIND
Alias: None
Product: kopete
Classification: Unmaintained
Component: Jabber Plugin (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-12 13:08 UTC by Florian Schmid
Modified: 2008-02-02 20:11 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Schmid 2006-08-12 13:08:55 UTC
Version:           0.12.2 (using KDE 3.5.4, Kubuntu Package 4:3.5.4-0ubuntu2~dapper1 )
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-26-386

I compiled Kopete 0.12.2 on Kubuntu Dapper. All protocols work fine except AudioSupport for Jabber.

Here are the errors I get:
 I start conversation:
kopete: [QString ChatMessagePart::formatStyleKeywords(const QString&, const Kope
kopete (jabber): [void JabberResource::slotGetTimedClientVersion()] Requesting c
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(cons                                                           
<query xmlns="jabber:iq:version"/>
</iq>
kopete (jabber - raw protocol):
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(cons                                                           
<query xmlns="jabber:iq:version">
<name>Kopete</name>
<version>0.12.2</version>
<os>Linux 2.6.15-26-386</os>
</query>
</iq>
kopete (jabber - raw protocol):
kopete (jabber): [void JabberResourcePool::slotResourceUpdated(JabberResource*)]
kopete (jabber): [JabberResource* JabberResourcePool::bestJabberResource(const X                                                           
kopete (jabber): [JabberResource* JabberResourcePool::lockedJabberResource(const
kopete (jabber): [JabberResource* JabberResourcePool::bestJabberResource(const X
kopete (jabber): [virtual void JingleVoiceCaller::call(const XMPP::Jid&)] jingle
kopete (jabber): [void JingleClientSlots::callCreated(cricket::Call*)]

----------------------------------------------------------------------------------------------------
COnversation started by peer:
kopete (jabber - raw protocol):
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML IN: <iq from="********@amessage.at/Gaim" type="result" id="aab8a" to="****@amessage.at/Kopete" >
<query xmlns="jabber:iq:version">
<name>gaim</name>
<version>1.5.1cvs</version>
<os>Linux 2.6.15-23-386 i686</os>
</query>
</iq>
kopete (jabber - raw protocol):
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML IN: <iq from="**************@amessage.de/Laptop" type="set" to="**********@amessage.at/Kopete" >
<session xmlns="http://www.google.com/session" initiator="**********@amessage.de/Laptop" type="initiate" id="2218166741" >
<description xmlns="http://www.google.com/session/phone">
<payload-type id="110" name="speex" />
<payload-type id="0" name="PCMU" />
</description>
</session>
</iq>
kopete (jabber - raw protocol):
kopete (jabber): [void JingleVoiceCaller::receiveStanza(const QString&)] jinglevoicecaller.cpp: Handing down <iq from="****@amessage.de/Laptop" type="set" to="****@amessage.at/Kopete" >
<session xmlns="http://www.google.com/session" initiator="******@amessage.de/Laptop" type="initiate" id="2218166741" >
<description xmlns="http://www.google.com/session/phone">
<payload-type id="110" name="speex" />
<payload-type id="0" name="PCMU" />
</description>
</session>
</iq>
kopete (jabber):
kopete (jabber): [void JingleClientSlots::callCreated(cricket::Call*)]
kopete (jabber): [void JingleClientSlots::stateChanged(cricket::Call*, cricket::Session*, cricket::Session::State)] jinglevoicecaller.cpp: State changed (2)
kopete (jabber): [void JingleVoiceCaller::registerCall(const XMPP::Jid&, cricket::Call*)] jinglevoicecaller.cpp: Registering call
kopete (jabber):
kopete: [void JingleVoiceCaller::registerCall(const XMPP::Jid&, cricket::Call*)] ****@amessage.de/Laptop
kopete (jabber): [void JabberAccount::slotIncomingVoiceCall(const XMPP::Jid&)]
kopete (jabber): [void JabberAccount::slotIncomingVoiceCall(const XMPP::Jid&)] Showing voice dialog.

GLib-ERROR **: The thread system is not yet initialized.
aborting...
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kopete path = <unknown> pid = 5208
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML OUT: <iq type="result" to="****@amessage.de/Laptop" />
kopete (jabber - raw protocol):
kopete (oscar - raw protocol): [void Client::nextICQAwayMessageRequest()] request queue count 1
kopete (oscar - raw protocol): [void Client::requestICQAwayMessage(const QString&, Client::ICQStatus)] requesting away message for 141015250
kopete (oscar - raw protocol): [void SendMessageTask::addChannel2Data(Buffer*)] Trying to send type 2 message!
kopete (oscar - raw protocol): [virtual void SendMessageTask::onGo()] SENDING:

kopete (oscar - raw protocol):
kopete: [virtual bool KopeteWindow::queryExit()]  shutting down plugin manager
libkopete: [void Kopete::PluginManager::slotPluginReadyForUnload()] NowListeningPluginready for unload
libkopete: [virtual void Kopete::Protocol::aboutToUnload()] 322032963 is still connected, disconnecting...
kopete (oscar): [void OscarAccount::logOff(Kopete::Account::DisconnectReason)] accountId='322032963'
kopete (oscar - raw protocol): [void ConnectionHandler::clear()] Clearing all connections
kopete (oscar - raw protocol): [void SSIManager::clear()] Clearing the SSI list
kopete: [void KopeteWindow::slotAccountStatusIconChanged(Kopete::Contact*)] [variant:  toString=]
In file kernel/qpixmap_x11.cpp, line 747: Out of memory
Unable to start Dr. Konqi
---------------------------------------------------------------------------------------------------------------------
Maybe they are useful, it worked with Kopete 0.12.1 in most cases.
Comment 1 Pino Toscano 2007-11-04 20:16:30 UTC
Are you still ale to reproduce the problem?
If so, can you please get a backtrace of the crash by following the page:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 Matt Rogers 2008-02-02 20:11:56 UTC
Waiting for a backtrace of the crash. When you provide one, please reopen this bug.