Bug 174123

Summary: Kopete statistics plugin doesn't work
Product: [Unmaintained] kopete Reporter: Ricardo Correia <bugs.kde.org>
Component: Statistics pluginAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Ricardo Correia 2008-11-02 21:53:48 UTC 
Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    Ubuntu Packages

Since I've upgraded from kde 3.5.x to 4.1.2, the kopete statistics plugin stopped working.

I've made sure that it is enabled in the plugins configuration dialog and I've also checked that the ~/.kde/share/config/kopeterc file has the string "kopete_statisticsEnabled=true" in the "[Plugins]" section, but it still doesn't work.

I've also tried to remove the ~/.kde/share/apps/kopete/kopete_statistics-0.1.db file, but even after disabling the plugin, reenabling it and restarting kopete, it still doesn't work..
Comment 1 Ricardo Correia 2008-11-02 22:00:19 UTC 
Sorry, I should have been more clear:

When I say it doesn't work, I mean that the statistics dialog doesn't show any statistical information, i.e., it shows everything as zeros or empty fields, as if the database is empty (which it is, because the database file isn't being created for some reason):

Total visible time : 00:00:00 hour(s)
Total online time : 00:00:00 hour(s)
Total busy time : 00:00:00 hour(s)
Total offline time : 00:00:00 hour(s)
Average message length : 0 characters
Time between two messages :  0 second(s)
Last talk : 1970-01-01 01:00
Last time present : 1970-01-01 01:00
Is Unknown since 2008-11-02 21:56

The only exception is that the "Last time present" and the "Is ... since .." fields do seem to work, but only for as long as kopete is open.

If I restart kopete, those fields return to the default values, as shown above.
Comment 2 Pino Toscano 2008-11-05 00:52:24 UTC 

*** This bug has been marked as a duplicate of bug 172940 ***