Version: 1.0.0 (using KDE 4.5.1) OS: Linux After dragging a chat tab over several spots (5, I believe) the name on the chat did not match the name of the contact with whom I was chatting. Also there were sufficient tabs open that the tabs extended beyond the width of the window, requiring left-right scrolling of the tabs. The dragged tab was an AIM chat, the chat whose name was taken was a jabber chat. I noticed that the tab icon (indicating the account type, that is AIM, jabber, etc) did change when dragged. Once the contact's status changed, the tab name was updated to match the contact name. I also noticed that not only did the dragged tab name mismatch, so did all those between the dropped location and the location from which the tab was dragged. Reproducible: Didn't try Steps to Reproduce: - Open a number of chat tabs (sufficient to have some scrolled off screen) - Scroll tabs all the way to the right - Select the second from last tab and drag it to the left, far enough to cause the tabs to scroll to the left - Drop the dragged tab Actual Results: Tab names between the dropped index and the index from which the tab was dragged are not updated to reflect the chat to which they correspond. Expected Results: Tabs names should match the chats to which they correspond
I can confirm this. I'm using 4.5.3 and the problem is happening to me too. I think that it is caused by reordering of tabs in the chat window. I do not know how to exactly reproduce this. I can confirm, that the tab is renamed. All other things, like typing notification, message notification, chat itself is ok.
kde 4.5.4 kopete v1.0.80 Steps to Reproduce: - Open 2 chat tabs - Shrink chat window horizontally so that the text in tab header didn't fir entirely - Select second tab and drag it to the left, far enough to cause first tab to scroll to the right - Drop the dragged tab
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!
Unfortunately, 12 years after reporting this bug I am not in a position to reproduce it.
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!