Bug 168415 - When I select the status of an article as unread or new, the kontact become very slow or freeze and take 2-3 minutes to select the correct data. Application not crashed.
Summary: When I select the status of an article as unread or new, the kontact become v...
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2008-08-05 14:15 UTC by Diego Collaziol
Modified: 2018-10-21 04:49 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Diego Collaziol 2008-08-05 14:15:48 UTC
Version:           1.2.50 (using 4.1.00 (KDE 4.1.0), Kubuntu packages)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-20-generic

Actually I have only 18000 feeds in separated accounts. When I select all feeds and check the status with unread or new, and when I back to all articles, the system freeze for about 2-3 minutes to select the data. Maybe the problem is with database. I'm not a developer, but I can do some tests if needed.
Diego, direct from Brasil.
Comment 1 Frank Osterfeld 2008-10-27 22:53:22 UTC
Please retry with >= 4.1.2.
Comment 2 FiNeX 2008-11-19 20:25:29 UTC
Changed severity to "crash". I hope to have selected only the right bugs (>100) :-)
Comment 3 Christophe Marin 2009-03-08 21:37:20 UTC
Changing the status of this bug until we get some feedback. (with KDE 4.2.1 at least)
Comment 4 Andrew Crouthamel 2018-09-19 04:38:42 UTC
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!
Comment 5 Andrew Crouthamel 2018-10-21 04:49:58 UTC
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!