Bug 102217 - [liboscar/icq] "A unknown error occured and the connection has been reset"
Summary: [liboscar/icq] "A unknown error occured and the connection has been reset"
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Unmaintained
Component: ICQ and AIM Plugins (show other bugs)
Version: 0.10
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 107023 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-03-22 23:49 UTC by Ian Hubbertz
Modified: 2005-07-22 01:51 UTC (History)
1 user (show)

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 Ian Hubbertz 2005-03-22 23:49:09 UTC
Version:           0.10 (using KDE KDE 3.4.0)
Installed from:    Gentoo Packages
Compiler:          gcc-3.4.3 CFLAGS="-march=athlon-xp -m3dnow -msse -mfpmath=sse -mmmx -O3 -pipe -fforce-addr -fomit-frame-pointer -funroll-loops -falign-functions=4 -maccumulate-outgoing-args -ffast-math -fprefetch-loop-arrays"
OS:                Linux

Kopete is no longer able to connect to the ICQ network. (Other modules for other networks NOT tested).

The icon shows connected, but after a while (about 1 minute) the message
"Es ist ein unbekannter Fehler aufgetreten und die Verbindung wurde getrennt."
(in english something like "A unknown error occured and the connection has been reset")

The icon still shows "connected" - and if the error is "clicked away" it is shown again after a while.

Other users are never shown online and I dont get any message. But at least one test message sent to another user was sent successfully - other tries to sent messages to the same user or other users failed.

Immediatly after startup the message

QObject::connect: Cannot connect (null)::isConnectedChanged() to Kopete::Contact::slotAccountIsConnectedChanged()

is sent to StdOut ; later status changes (try to disconnect/reconnect) results in

QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()

at StdOut.


I installed kopete 0.10 some days ago (as part of KDE 3.4) - it worked fine for one or two days - then the problem appeared.
The only things changed in the meantime was:
- switched kernel to 2.6.11 and back to 2.6.10
- i "prelinked" my whole system

I also recompiled kopete and deleted some of its ICQ-specific configuration (account settings) - no change!
Comment 1 Matt Rogers 2005-03-25 18:18:37 UTC
would need a kopete with debug enabled to see what's going on, the following line should do that for you:
'CFLAGS="" CXXFLAGS="" USE="debug" FEATURES="nostrip" emerge <name_of_package>'
Comment 2 Todor Todorov 2005-04-02 16:54:54 UTC
I can confirm this. I am using Kopete 0.10 on KDE 3.4 (Kubuntu Hoary Preview). Kopete has worked fine for 18 days, and today it stopped. The same errors, the same messages in .xsession-errors
Comment 3 Todor Todorov 2005-04-04 18:30:20 UTC
I've found the problem. My DNS server contained wrong IP address for login.icq.com.
Comment 4 Matt Rogers 2005-05-08 07:26:06 UTC
i'm tempted to tell you that your CFLAGS and CXXFLAGS are too excessive and that you need to rebuild with sensible flags and see if the problem disappears. I also need more info. can you provide debug output ('USE="debug" FEATURES="nostrip" emerge ...') so i can see what's really going on?
Comment 5 Ian Hubbertz 2005-05-10 18:49:54 UTC
The logs I sent you via private mail one month ago, contained the output of a kopete version compiled with default CFLAGS/CXXFLAGS.

BTW: The problem seems to have disappeared now, maybe after updating some KDE libraries? Unfortunately, I've no overview what libs have been updated..
kopete was not recompiled since I sent you the logs.

I'll give further feedback in some days...
Comment 6 Matt Rogers 2005-06-26 06:57:55 UTC
*** Bug 107023 has been marked as a duplicate of this bug. ***
Comment 7 Ian Hubbertz 2005-06-29 17:19:06 UTC
The error disappeared as suddenly as it appeared?!

Maybe it had something to do with some bug in one of the depending libs - maybe due to some special CFLAGS/CXXFLAGS.

For me, you can close this bug.

Comment 8 Kevin Boergens 2005-07-03 21:46:06 UTC
no, it still exists for me and is really a problem

Maybe the things I wrote here are helpful for you:
http://bugs.kde.org/show_bug.cgi?id=107023
If you have more questions about the problem, just ask.

Greetings,

  Kevin
Comment 9 Matt Rogers 2005-07-09 00:16:24 UTC
This is gone in trunk. The error handling has been greatly improved and this error message (if you get it) should show up as a passive popup (and automatically reconnect you) rather than a message box. Please test trunk if you can and report back with comments. Thanks.
Comment 10 Kevin Boergens 2005-07-21 17:37:16 UTC
I think the bug should be reopened.

a) I have the newest trunk and can't see your changes. The popup looks alike and there is no automatic reconnect.

b) far more important, the change you made was only a workaround. icq in kopete keeps disconnecting while other connections in kopete (msn) and gaim and icq2go work reliable.
Comment 11 Matt Rogers 2005-07-22 01:51:49 UTC
svn is still a work in progress. start complaining again if it's bad when kde 3.5 is released. i can't fix what i can't reproduce.