Bug 108287 - unable to use aim/icq w/o restarting kopete when internet connection is lost
Summary: unable to use aim/icq w/o restarting kopete when internet connection is lost
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: ICQ and AIM Plugins (other bugs)
Version First Reported In: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-28 21:18 UTC by gmud
Modified: 2006-03-25 18:21 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 gmud 2005-06-28 21:18:54 UTC
Version:           0.10.2 (KDE 3.4.1-1.2.fc3.kde) (using KDE KDE 3.4.0)
Installed from:    RedHat RPMs
Compiler:          gcc (GCC) 3.4.3 20050227 (Red Hat 3.4.3-22.fc3) 
OS:                Linux

After selecting status n/a on ICQ networks and waiting a couple of hours without using kopete the application doesn't seem to actually react on any click (you click, menus appear, but after selecting something, e.g. status change, nothing happens).

The applications has to be restartet, then everything is normal again.

Always reproduceable.

Expected behaviour: stay connected to selected network, hold given status (e.g. "n/a"), when selecting new status (e.g. "online") go online again, update status of others in contactlist in the meantime. Just like expected :)
Comment 1 Matt Rogers 2005-06-29 02:13:13 UTC
*sigh* i thought i fixed this.

I need debug output. You'll need to recompile kopete with the following (very terse) instructions:
./configure --prefix=`kde-config --prefix` --enable-debug
make
su -c "make install"

capture the output while running kopete on the console with only ICQ connected and make sure that the output somehow reflects the fact that the status doesn't change.

thanks for your cooperation.
Comment 2 Thiago Macieira 2005-06-29 05:55:40 UTC
It has never happened to me again, at least.
Comment 3 Olivier Goffart 2005-06-29 09:32:58 UTC
I think i already had the same problem.
When my internet connection is lost,  ICQ and AIM doesn't disconnect, but dopesn't work anymore either.
Comment 4 gmud 2005-06-29 14:45:45 UTC
Matt, I did as you said, but there is nothing but this as output on the console:

QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0

Kopete (with ICQ) works normally until I disconnect my dsl-connection and connect again. Then kopete will not react on trying to change status (as described above).

I took the svn version 0.10.90.
Comment 5 Matt Rogers 2005-07-22 17:16:03 UTC
when you disconnect your DSL connection, do you set kopete to offline first?
Comment 6 gmud 2005-07-22 17:32:48 UTC
No, normally I am in n/a or away mode (at night, when I sleep). Then, if my DSL connection is disconnected (either by me or by my isp) kopete doesn't work anymore.
Comment 7 gmud 2005-09-09 17:27:28 UTC
Tested once again with svn 20050822 (0.10.91)

Unable to use kopete after network ip has changed.

Debug output:

$ kopete
QImage::smoothScale: Image is a null image
QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
KPopupMenu: title() called with non-title id 0.
QObject::connect: No such signal Kopete::ChatSession::typing(bool)
QObject::connect:  (sender name:   'editPart')
QObject::connect:  (receiver name: 'unnamed')
QObject::connect: No such signal Kopete::ChatSession::typing(bool)
QObject::connect:  (sender name:   'editPart')
QObject::connect:  (receiver name: 'unnamed')
Comment 8 Jan Ritzerfeld 2006-03-25 18:21:10 UTC
The problem should be fixed in recent SVN---I had the problem, too, and now it works for me (using icq): kopete reconnects automatically after some minutes when the connection was lost and re-established.
Feel free to re-open if the problem is not solved for you.