Bug 176629 - freeze when tagging email
Summary: freeze when tagging email
Status: RESOLVED DUPLICATE of bug 174429
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.10.3
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-01 15:06 UTC by Christoph Paasch
Modified: 2009-03-19 00:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Paasch 2008-12-01 15:06:34 UTC 
Version:           1.10.3 (using 4.1.3 (KDE 4.1.3), Kubuntu packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.27-10-generic

Hi,

when trying to tag a message, kmail freezes. Nothing is shown in the console, when launching from the command line. I just can kill kmail, and then restart it, to continue working. After restarting the tag is still NOT set. So, there is no way to tag e-mails
Comment 1 George Kiagiadakis 2008-12-02 13:19:33 UTC 
I cannot reproduce this with kmail trunk r890719 and with a pop3 account folder. Are you trying to tag a message in a pop3 or an imap account and do you have any other special setup (groupware, etc...)?
Comment 2 Christoph Paasch 2008-12-02 14:05:47 UTC 
I have pop3. No groupware or any special things...

After clicking on "tag" the nepomuk process jumps to 100% for a few seconds. I tried it with nepomuk disabled in the "System Settings", and it worked fine. So, this may be a problem with nepomuk.
Comment 3 Christoph Paasch 2008-12-15 18:10:15 UTC 
Well, I have discovered another thing about that:

While kmail is blocked... If I click on the systemtray icon of kmail, (this will close the kmail GUI) and then click again on the systemtray, the message got successfully tagged, and everything is working fine again (of course the bug with the e-mail taggin persists).
Comment 4 George Kiagiadakis 2009-01-18 16:01:45 UTC 

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