Created attachment 58098 [details] Kopete console output from a session with this issue Version: 1.0.80 (using KDE 4.6.1) OS: Linux i have six accounts in kopete: one AIM, three Jabber, one Skype, and one Bonjour. one of the Jabber accounts is a Google Talk account. that account rarely stays online for longer than a few seconds. not only does this make the account unusable, but it makes the rest of Kopete unusable too because the whole UI freezes while the Google Talk account is disconnecting or reconnecting. the only workaround i have found is to disable or remove the Google Talk account in Settings -> Configure... -> Accounts. Reproducible: Always Steps to Reproduce: 1. launch kopete. 2. connect to a Google Talk account (or wait for it to auto-connect if it is set to do so). 3. wait ~7 s. the Google Talk account freezes the UI for ~2.5 s as it disconnects. 4. wait ~10 s. the Google Talk account freezes the UI for ~2.5 s as it reconnects. 5. repeat steps 3-4 ad nauseum. Actual Results: see steps 3-4. kopete's console output is silent during the disconnects, but it prints the following during each reconnect: Unknown signature value: 795 QProcess::start: Process is already running Expected Results: the account should come online and stay online. if it must disconnect and reconnect due to external factors, then it should not freeze the UI as it does so. OS: Linux (x86_64) release 2.6.35-28-generic Compiler: cc the first time that some of the accounts connect (including the Google Talk one), kopete's console output displays this: Corrupt JPEG data: premature end of data segment Invalid JPEG file structure: two SOI markers
Same error, but with another server. Kopete writes to konsole "Unknown signature value: 795"
may be related to bug 263548.
i wasn't sure if this was the case before, but i'm pretty sure now: this issue appears consistently on some days but not at all on others. it appeared earlier this week, and i subsequently disabled my Google Talk account. i just re-enabled it and no longer see the issue. this suggests, to me, that this is a failure of Kopete in handling some transient network issue. i've never seen this happen in Pidgin, so it seems possible to handle this more gracefully.
Same problem here for the last month or so (also running kopete 1.0.80). The constant reconnecting also causes kopete to leak massive amounts of memory.
Same problem: Qt: 4.7.4 KDE Development Platform: 4.7.2 (4.7.2) "release 5" Kopete: 1.1.2 (OpenSUSE 12.1) > kopete kopete(11764)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/home/user/.kde4/share/apps/kabc" > kopete(11764)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '! Unknown signature value: 7 Unknown signature value: 7 Unknown signature value: 795 Unknown signature value: 7 Unknown signature value: 7 Unknown signature value: 795 QProcess::start: Process is already running Unknown signature value: 7 Unknown signature value: 7 Unknown signature value: 795 QProcess::start: Process is already running Unknown signature value: 7 Unknown signature value: 7 Unknown signature value: 795 QProcess::start: Process is already running Unknown signature value: 7 Unknown signature value: 7 Unknown signature value: 795 QProcess::start: Process is already running and these lines keep repeating themselves every reconnection: Unknown signature value: 7 Unknown signature value: 7 Unknown signature value: 795 QProcess::start: Process is already running
Same issue here with Kopete 1.0.0 and KDE 4.4.5 on Debian. It started to behave like that a couple of weeks ago.
I have found that in my case this happens in situation when 2 instances of kopete (on 2 different machines) are logged in place behind NAT. I did not try to change to debug it further. I am not sure if the NAT is required to reproduce it, it is just my setup. I did not even try change name of source in kopete to avoid possible conflicts. Closing one of these instances stopped the disconnection. I did it with KUbuntu 12.10 and kopete 4:4.9.5-0ubuntu0.1
Kopete in svn has updated libiris and libjingle libraries. Test if this problem is still there.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!