Summary: | OTR is stopped without notifying the other end when conversation is closed | ||
---|---|---|---|
Product: | [Unmaintained] telepathy | Reporter: | Raimar Sandner <disp.reg.bugs.kde> |
Component: | OTR | Assignee: | Telepathy Bugs <kde-telepathy-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | dlbarchiesi, olaf.the.lost.viking, tom-kde.bugs, zieminn |
Priority: | NOR | ||
Version: | 0.9.0 | ||
Target Milestone: | Future | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Raimar Sandner
2015-02-25 14:14:22 UTC
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! |