Bug 93749 - History plugin should save immediately
Summary: History plugin should save immediately
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 0.40.0
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 178040 223993 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-11-22 22:22 UTC by Nicolas Girard
Modified: 2024-09-18 18:27 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Girard 2004-11-22 22:22:41 UTC
Version:           0.9.1 (using KDE 3.3.1 (CVS >= 20041110), Mandrake Linux Cooker i586 - Cooker)
Compiler:          gcc version 3.4.1 (Mandrakelinux 10.1 3.4.1-4mdk)
OS:                Linux (i686) release 2.6.8.1-20mdk

Due to bug #93539, Kopete crashes when receiving pending messages ; these messages get completely lost.

This is simply unacceptable to loose messages because of crashes ; kopete *must* be able to save them in case of crash, and recover them at the next start.
Comment 1 Jason Keirstead 2004-11-23 01:08:41 UTC
If you had the History plugin enabled, the message as described in bug #93539 would have been logged to it, since messages are processed by plugins before the View button is even shown.

Or do you want something else? I don't see any other method to "revover" messages in case of a crash other than writing them to disk, which is what History does.
Comment 2 Richard Smith 2004-11-23 01:31:12 UTC
On Tuesday 23 November 2004 00:08, Jason Keirstead wrote:
> If you had the History plugin enabled, the message as described in
> bug #93539 would have been logged to it, since messages are processed by
> plugins before the View button is even shown.

Not quite. The history plugin doesn't save messages to disk immediately.
Comment 3 Jason Keirstead 2004-11-23 02:28:23 UTC
You seem to be right. 

That plugin is a total mess :/
Comment 4 Bram Schoenmakers 2007-08-11 14:35:13 UTC
It's impossible to quickly do something when Kopete crashes, at that point it is already too late. I'll turn this in a request to let the Kopete History save immediately.

I looked into the code, but couldn't understand why there are timers on the saving part.
Comment 5 Will Stephenson 2007-11-14 15:00:06 UTC
Logging to Akonadi should fix this
Comment 6 garbage.angel 2009-01-30 02:43:30 UTC
*** Bug 178040 has been marked as a duplicate of this bug. ***
Comment 7 André Neves 2010-03-18 21:35:53 UTC
Until the present day this bug continues unsolved.

It is terrible that an entire session of conversation is lost if Kopete is closed uncleanly.

There should be an option to flush history instantaneously to disk.
Comment 8 Nick Shaforostoff 2010-05-28 11:55:17 UTC
*** Bug 223993 has been marked as a duplicate of this bug. ***
Comment 9 Christoph Cullmann 2024-09-18 18:27:33 UTC
Dear user, unfortunately Kopete is no longer maintained.

Please migrate to another solution, e.g. for Jabber a possibility is Kaidan, for Matrix a candidate is NeoChat.