Version: 1.13.5 (using KDE 4.4.5) OS: Linux Kmail becomes unresponsive when virtuoso-t is running and taking 100% of the CPU. Reproducible: Didn't try Steps to Reproduce: Just work be working and when it stops functioning, go kill virtuoso-t and it becomes immediately responsive again. Expected Results: not freeze, but it does not appear to have anything to do with kmail but it has the appearance of being a Kmail problem OS: Linux (i686) release 2.6.32-5-686-bigmem Compiler: cc I am running KDE 4.4.5-1 and I am having trouble with kmail freezing and it appears to be because virtuoso-t is running, taking up 100% of the CPU. When I kill it, I can work again immediately in whatever I was doing (usually composer) prior to the freeze. The size of the log file - ./.kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-virtuoso.log was mentioned in one thread and that is only 1.3 M in my system. I am using Debian Unstable (not usual for me but I am hoping to get some bug fixes for Kontact ASAP) on a laptop with an AMD dual core processor. Fortunately use of the terminal is not affected so I can get to top and kill the process. However, users who are not aware of how to do this will be very frustrated with kmail. I am reporting this both for nepomuk and kmail. By the way, Konqueror keeps crashing when I am using the bug reporter so I had to cut and paste this report in before konqueror closes abruptly. I think it is happening when I click to move the cursor in the report I am writing but I am not sure yet. I will try to report that as well.
I can tell you now that to reproduce this, all I have to do is reboot my computer. Soon kmail will become close to 100% unresposive and in top, virtuoso-t will be taking close to if not more than 100% of the processor and killing it will fix kmail's problem. By the way, the bug reporter keeps crashing so the only way to get this to you is to paste this into the comment field and submit it immediatel
I think this is a duplicate of Bug https://bugs.kde.org/show_bug.cgi?id=241081
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.