Description of problem: If I am chatting with somebody using Kopete through jabber protocol (GTalk) and if he/she changes resource (switch from gmail to orkut or google talk application or Pidgin), the new messages from him/her are shown in new tab (or window). This behaviour is very annoying. Version-Release number of selected component (if applicable): kdenetwork-4.2.4-4.fc11.x86_64 How reproducible: Always Steps to Reproduce: 1.Chat with a Jabber/Gtalk contact 2.Let him change resource 3. Actual results: New chats arrive in new tab or window Expected results: The new chats should continue in same tab/window. Additional info: This bug has been discussed on kopete-devel at http://www.mail-archive.com/kopete-devel@kde.org/msg15006.html There are patches mentioned in the thread too. These are the relevant bug reports on KDE Bugzilla. https://bugs.kde.org/show_bug.cgi?id=111537 https://bugs.kde.org/show_bug.cgi?id=142650 https://bugs.kde.org/show_bug.cgi?id=175078 https://bugs.kde.org/show_bug.cgi?id=194808 Its has been mentioned that the patches will make it to KDE 4.4. I request the package maintainers at fedora to please integrate these patches in current kdenetwork versions for fedora 10 and 11. It will enhance Kopete user experience very much as a lot of KDE users have complained about this bug and even for me , I have moved to Pidgin only due to this behaviour in Kopete , which is otherwise a very good messenger client.
I have strong trepidations usurping upstream opinion here, if that is the case. I'd venture this is due at least to string freeze, since this adds a new ui option.
Yes, you are right there, but otherwise is it possible to incorporate the patches with slight modifications? , so that the patches which change the UI (ie give user option to enable/disable this grouping) are not incorporated and apply the other patches to force the messages from same contact into same window/tab ( like Pidgin's behaviour). I know its not correct to force an option on users, but from the bug reports, its really clear that most users see this as a bug or undesired behaviour.
Be that as it may, this is a conversation best had with upstream developers, not downstream distributors.
Good luck, given upstream's draconian freeze policy. I don't see why we couldn't backport this in our packages. In fact I'd like to see more backports, to bring features which are already ready for consumption to our users faster.
Well exactly my thoughts. KDE 4.4 is like atleast 4 months from now. Its very unfortunate if we have to hold back this useful patch from our users. And taking the middle path I suggested (without modifying the UI) seems to be a good way to achieve what I am proposing while still retaining the UI string freeze.
The patch introduces only one new string and if this feature is really important we should backport it to our package. Of course, it's optimal if we could make a patch without modifying the UI.
i backported the patch without modifying the UI to our kde-4.3.0. The fix is included in kdenetwork-4_3_0-2_fc12. It will be included in next KDE update for F11/F10.
I will test it as soon as the package is built for F11 in Koji. Right now I can only see F12 package.
you can download from http://koji.fedoraproject.org/koji/buildinfo?buildID=129122
kdenetwork-4.3.0-2.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/kdenetwork-4.3.0-2.fc11
kdenetwork-4.3.0-2.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/kdenetwork-4.3.0-2.fc10
Thanks a lot Ngo for working on this bug. I tested it today and it works very well.
Can we close this bug now? Please excuse me for my ignorance but I am not familiar with the whole process and when to close a bug and who should close it.
It will be closed automatically when the updates go stable.
kdenetwork-4.3.0-2.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update kdenetwork'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-9017
kdenetwork-4.3.0-2.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update kdenetwork'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-9034
kdenetwork-4.3.0-2.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
kdenetwork-4.3.0-2.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.