Bug 144569

Summary: kopete 100% busy on startup when statistics plugin is activated
Product: [Unmaintained] kopete Reporter: Andreas Pietzowski <andreas>
Component: generalAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Andreas Pietzowski 2007-04-23 16:41:44 UTC 
Version:           0.12.4 (using KDE 3.5.6 "release 64.1" , openSUSE )
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.18.2-34-default

Hello,

I know this is a duplicate of bug #125024 but it is marked as resolved but it seems that many users really have problems with that plugin. I read that it takes longer to start up when you have many contacts stored in kopete. But what do you think kopete is good for? In my opinion a good IM as kopete should handle tons of contacts without a problem and all plugins activated if someone wants to.

I also don't know the reason why the stored statistics data is loaded on startup. I think this should only be necessary when you ask the statistics for something. If you use a database in an application you also don't have to wait until all data is loaded before you can use the application ;) This is the reason why databaseses have been invented.

In my opinion there should really be done some improvements in that plugin - otherwise it is a useless plugin for many users after a bunch of data has been collected...

What do you think?
Andreas
Comment 1 Matt Rogers 2007-06-09 07:55:39 UTC 
125024 is a duplicate of another bug, that's why it's marked as resolved.

*** This bug has been marked as a duplicate of 125024 ***
Comment 2 Andreas Pietzowski 2007-06-09 12:41:01 UTC 
Hey this bug is everywhere just a duplicate or marked as resolved. But in deed it is NOT resolved in any way. Kopete really has a big problem with handling the statictics plugin. If you close this bug or mark it again as resolved, what is the number of the current open bug now that everyone can follow it?

Thanks
Andreas