| Summary: | Jabber won't connect, no error, nothing happens | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Adam Porter <adam> |
| Component: | Jabber Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Adam Porter
2006-04-09 06:07:07 UTC
I spoke with mattr last night in #kopete. He couldn't find the problem. His last suggestion was to remove the account and readd it. I did that, and then it started working! But then after I logged out of KDE and back in, it's not working again. When I try to connect, *nothing* happens. No change in the status bar icon, no error messages, just nothing, except these messages on STDERR. I switched to the version of Kopete currently in Debian unstable (0.11.2 from the 3.5.2-1 packages), and had the same problem! So, after removing the Kopete config files (~/.kde/share/config/kopeterc and ../apps/kopete), and adding the account to a fresh config, it worked. Then I copied the old config files back, and now it still works. Next I'll reinstall the beta and see if it still works. I'm closing the bug for now, but I'll reopen it if I get the problem again. *sigh* Well, I came back to my computer after a few hours and found that Kopete had frozen. I SIGTERM'ed it, restarted it, and now that Jabber account doesn't work. At all. Nothing happens when I try to connect. But my other Jabber account is working fine at the same time. Side by side they sit, one alive, one dead. (This is with 0.11.2, by the way, but the same problem exists in 0.12 beta 2). First of all, ***this is also happening with 0.11.2 from Debian's 4:3.5.2-1 package.*** It's not just in the 0.12 beta. However, it did *not* happen with the version in Debian's 4:3.5.1-2 package. I've done some more investigating on this bug, and I think it might be related to Kopete's handling of passwords. Here's the relevant part of the debug log: kopete (jabber): [const XMPP::Resource& JabberResourcePool::bestResource(const XMPP::Jid&, bool)] Determining best resource for blujay@jabber.org kopete (jabber): [const XMPP::Resource& JabberResourcePool::lockedResource(const XMPP::Jid&)] Current lock for blujay@jabber.org is 'Kopete' kopete (jabber): [const XMPP::Resource& JabberResourcePool::bestResource(const XMPP::Jid&, bool)] We have a locked resource 'Kopete' for blujay@jabber.org kopete (jabber): [virtual void JabberAccount::connectWithPassword(const QString&)] called kopete (jabber): [void JabberAccount::disconnect(Kopete::Account::DisconnectReason)] disconnect() called kopete (jabber): [void JabberAccount::setPresence(const XMPP::Status&)] Status: , Reason: Here's the relevant part of the source (jabberaccount.cpp): /* Cancel connection process if no password has been supplied. */ if ( password.isEmpty () ) { disconnect ( Kopete::Account::Manual ); return; } After another nothing-happens connection attempt, I opened the account's properties and turned off "Remember password". Then I tried to connect, and Kopete popped up a box that said that the password was incorrect, and asked for the correct password. I entered it (pasted it) and hit enter, the box disappeared, and nothing else happened. I tried to connect again, and *nothing* happened: not even a password prompt. Then I opened the account's properties again, turned *on* "Remember password", and *typed* the password there. Then I hit OK, and tried to connect...and it worked. I'm currently connected on the account. Note that throughout all this, my other Jabber account has worked fine. The troublesome account's password has a comma in it. I don't know why that should make any difference, but it's the only thing I can think of. Please let me know if I can do anything else to help debug this. I finally found a way to set the configure flags for dpkg-buildpackage/dpkg-deb/apt-src/etc, so I can compile and install debug versions of packages The Debian Way so it will fit in with the rest of the system. By the way, even after restarting Kopete, the account is still working. Finally (last post this time), may I suggest that: 1. A debug message be added in the code there 2. An error dialog be popped up as well, that prompts the user for the password Also, just below that code block, there's this: /* Don't do anything if we are already connected. */ if ( isConnected () ) return; This is another potential trouble spot. Shouldn't there at least be a debug message here? It seems you are not trying to go online, but to go offline.
kopete (jabber): [virtual void JabberAccount::setOnlineStatus(const Kopete::OnlineStatus&, const QString&)] CROSS YOUR FINGERS! THIS IS GONNA BE WILD
void JabberAccount::setOnlineStatus( const Kopete::OnlineStatus& status , const QString &reason)
{
XMPP::Status xmppStatus = m_protocol->kosToStatus( status, reason);
if( status.status() == Kopete::OnlineStatus::Offline )
{
xmppStatus.setIsAvailable( false );
kdDebug (JABBER_DEBUG_GLOBAL) << k_funcinfo << "CROSS YOUR FINGERS! THIS IS GONNA BE WILD" << endl;
disconnect (Manual, xmppStatus);
return;
}
How do you go online ? (what button)
please try to go away or go busy.
I click the Jabber icon in the status bar and click Online->No Message. I've tried entering other status modes as well, but none of them work when it's acting like this. Try disable the now listeing plugin. Does it works ? Or does this problem still persist with Kopete 0.12 ? I think this was related to a bug in the now listening plugin whioch is now fixed. I'm not using now listening and it doesn't work. Is 3.5.8, but I noticed the bug in 3.5.7. What's wrong with Kopete? I like so much! |