Bug#520316: marked as done (kopete: can't connect to google talk)
Your message dated Thu, 19 Mar 2009 00:04:45 +0100
with message-id <a96c33670903181604l18e8234tc67a424542aa826d@mail.gmail.com>
and subject line Re: Bug#520316: kopete: can't connect to google talk
has caused the Debian Bug report #520316,
regarding kopete: can't connect to google talk
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
520316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520316
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: kopete
Version: 4:4.2.1-1
Severity: normal
*** Please type your report below this line ***
kopete can't connect to XMPP google talk servers. It hangs with the
status "connecting". Sometimes (not always.. !?) it displays "login
failed for an unknown reason".
>From terminal, I can see these last lines :
JingleSessionManager::JingleSessionManager created.
Creating the PushJingleSession task....
Object::connect: No such signal
XMPP::JingleSessionManager::incomingSession()
May it be bound to jingle support ?
My "connection" config in kopete (though I suppose this is not the
problem...) :
[x] ssl
[x] plain text auth
[x] override default server :
talk.google.com 5223
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.28-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages kopete depends on:
ii kdebase-runtime 4:4.2.1-2 runtime components from the offici
ii kdelibs5 4:4.2.1-2 core libraries for all KDE 4 appli
ii kdepimlibs5 4:4.2.1-2 core libraries for KDE PIM 4 appli
ii libasound2 1.0.19-1 shared library for ALSA applicatio
ii libc6 2.9-6 GNU C Library: Shared libraries
ii libglib2.0-0 2.20.0-1 The GLib library of C routines
ii libidn11 1.12-1 GNU Libidn library, implementation
ii libkopete4 4:4.2.1-1 main Kopete library
ii libmeanwhile1 1.0.2-3 open implementation of the Lotus S
ii libmsn0.1 4.0~beta3-1 high-level C++ library for MSN Mes
ii libortp7 2.1.1-1+b1 Real-time Transport Protocol stack
ii libotr2 3.2.0-1 Off-the-Record Messaging library
ii libqca2 2.0.1-1 libraries for the Qt Cryptographic
ii libqimageblitz4 1:0.0.4-4 QImageBlitz image effects library
ii libqt4-dbus 4.4.3-2 Qt 4 D-Bus module
ii libqt4-network 4.4.3-2 Qt 4 network module
ii libqt4-qt3support 4.4.3-2 Qt 3 compatibility library for Qt
ii libqt4-sql 4.4.3-2 Qt 4 SQL module
ii libqt4-xml 4.4.3-2 Qt 4 XML module
ii libqtcore4 4.4.3-2 Qt 4 core module
ii libqtgui4 4.4.3-2 Qt 4 GUI module
ii libspeex1 1.2~rc1-1 The Speex codec runtime library
ii libstdc++6 4.3.3-5 The GNU Standard C++ Library v3
ii libxml2 2.7.3.dfsg-1 GNOME XML library
ii libxslt1.1 1.1.24-2 XSLT processing library - runtime
ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime
Versions of packages kopete recommends:
ii libqca2-plugin-ossl 0.1~20070904-3 QCA OSSL plugin for libqca2
Versions of packages kopete suggests:
pn kdeartwork-emoticons <none> (no description available)
pn khelpcenter <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
2009/3/18 Lisandro Damián Nicanor Pérez Meyer <perezmeyer@gmail.com>:
> I have the same version of kopete, and have no problem connecting to Google's
> Jabber. I do see the same as you in a console.
>
but there's surely something appearing just after, isn't it ? (see below)
> Checked with mine, no problem here. Perhaps a firewall is blocking you?
>
No firewall at all for the moment.
I've tried with some other accounts, and there's something very
strange : I can connect to my personal domain gmail account !
I can affirm the accounts have the exactly same configuration (except
the identifiers, obviously) !
I can affirm too that my identifiers for the not-working account are
right because i can login with them for accessing my mailbox
Here is the log with only the "personal-domain" gmail account
Object::connect: No such signal XMPP::JingleSessionManager::incomingSession()
Create JingleCallsManager
Created Media Manager.
kopete(5840) JingleCallsManager::JingleCallsManager: **********
JingleCallsManager::JingleCallsManager created. *************
but with the other account, it still hangs on :
Object::connect: No such signal XMPP::JingleSessionManager::incomingSession()
...and then I can wait... and nothing changes.
-----------
As I was writing and testing since many minutes, it has worked for
some seconds ! I have been able to connect to the account.
But after some seconds it has broken down again :(
It seems it's only related to that account, so i'll wait...
And so I suppose the bug can be closed, then.
But a question remains: why is the account working with other clients
like gajim, but not with kopete ?
I'll reopen the bug if I can find a obvious relation with kopete...
Sorry for the derangement, anyway... and thanks for the reply.
--- End Message ---
Reply to: