First of all I was very excited to see OTR support in telepathy, thank you! However at the moment there is a big issue with the conversation flow (at least for my typical use case). Because the OTR session is closed when the chat window is closed, new messages which arrive are unreadable, and I have to ask my correspondent to send them again after the OTR session is refreshed. Actually I don't know if the issue lies with telepathy or with the other clients. Anyhow, the OTR session should be closed properly, so that the other end knows new messages cannot be encrypted within the same session anymore. Alternatively (maybe as a configurable option) the OTR session should be kept open when closing the chat window. This is how most other clients work at the moment, I guess. Reproducible: Always Steps to Reproduce: (tested with Adium or kopete on the other end): 1. initiate an otr session, exchange some messages 2. close the chat window 3. your correspondent sends you a new message Actual Results: The messages belong to the old OTR session and are unreadable because they cannot be decrypted on my end. Expected Results: Messages are decrypted within the previos OTR session, which would have to be kept open for this purpose. Alternatively, properly close the old OTR session, so that a new one has to be established by the sender.
Ha, just found stumbled upon this problem when trying out if encrypted messages are now visible in the history (thanks for already opening a bug report). As I close the chat window when I am not actively chatting, keeping the OTR session open when closing the window is clearly the better/only sensible solution for my usecases.
An option to automatically refresh otr sessoins if there comes in an undecryptable message would be nice too. eg pidgin-otr even automatically resents a unreadable message in this case.
Situation hasn't changed.
Thank you for reporting this bug 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 "CONFIRMED" 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!