Version: unspecified (using KDE 4.5.95) OS: Linux Klipper only saves history when the program is exited correctly. All session history would be lost if klipper was crashed, killed or system was powered off ubnormally (eg with alt+sysrq+b). My usecase when this situation makes sense - I had problems with KML - the system could get freezed at any random moment. Typing long message in some web for in web browser was just dangerous - all typed text could be lost if system would freeze before the reboot. As soon as web form does not have ctrl+s option to quickly save text while typing before submitting the form, I wanted to use klipper as a good and quick workaround alternative for that - just ctrl+a, ctrl+c and the whole text goes to clipboard history, which theoretically should be available even when the system reboots. But on practice this was not so. The system freezes, reboot it with alt+sysrq+b (or just poweroff), login again and see that klipper did not save copied history for the previous session and all typed text was lost along with browser window, and klipper failed to save me from such situation, though I naturally assumed it could do it. I know, that klipper history is not a good place to store important text data, but this is small use-case for the improvement, which could make it better, if it saved history more often - not only when exit correctly. Reproducible: Always Steps to Reproduce: 1. Copy some text to klipper 2. Make sure the text is in klipper history 3. killall klipper 4. Start klipper again Actual Results: copied text would not appear in the history Expected Results: it could be better, if copied text would not appear in the history even when the program ended ubnormally
sorry, did not check for typos before submitting >problems with KML problems with KMS >freeze before the reboot freeze before the form is submitted
This sounds similar to or related with bug 269931. And the history is also saved when klipper is closed through 'killall klipper'(at least for me).
kde 4.7.2. - "killall klipper" would still make klipper lose recent items (the whole history is not lost - only the new items which appeared during latest klipper session).
(In reply to comment #3) Ahh, you are right. So, to solve your problem, klipper needs to save the history ASAP. I think that is basically the same as bug 152039.
>So, to solve your problem, klipper needs to save the history ASAP. yes, exactly >I think that is basically the same as bug 152039. yes, this is the same bug
*** This bug has been marked as a duplicate of bug 152039 ***