Bug 128141 - When using connectAll() function jabber protocol can't connect. Then Kopete hangs upon disconnection.
Summary: When using connectAll() function jabber protocol can't connect. Then Kopete h...
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-27 19:39 UTC by MoonWolf
Modified: 2006-06-16 23:44 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MoonWolf 2006-05-27 19:39:43 UTC
Version:            (using KDE KDE 3.5.2)
Installed from:    Fedora RPMs

I use Jabber and Gadu. Recently i bounded some actions to my multimedia keys. For setting online i'm doing the following:
dcop kopete KopeteIface 'connectAll()'
sleep 3 # i hoped it will help - it didn't
dcop kopete KopeteIface 'setAway(QString,bool)' "$STATUS" "0"

Unfortunately Jabber doesn't go online (Gadu works OK) - icon just flashes. When i'm trying to disconnect, kopete hungs up.
Comment 1 Olivier Goffart 2006-06-07 21:11:12 UTC
Works fine here.
Maybe your jabber account is in the "exlude" list (exclude from global conneciton in the account preference)
If not,  what say the debug output ?
Comment 2 Olivier Goffart 2006-06-13 11:39:09 UTC
Please attach the debug output.
Comment 3 MoonWolf 2006-06-16 23:36:57 UTC
Olivier Goffart denied rebel lies:

> http://bugs.kde.org/show_bug.cgi?id=128141
> ------- Additional Comments From ogoffart kde org  2006-06-07 21:11
> ------- Works fine here.
> Maybe your jabber account is in the "exlude" list (exclude from
> global conneciton in the account preference) If not,  what say the
> debug output ?


Hmm... Now it works almost fine - sometimes it hungs though. But for now 
i don't see any regularity, so i can't provide debug output. So i think 
it may be something with my configuration if it really works fine 
elsewhere.
I think that means it's not really a bug and we should shut this down 
(:) - sorry for inconvenience...
Comment 4 Olivier Goffart 2006-06-16 23:44:22 UTC
*** this bug has been marked as RESOLVED ***