Hi, unfortunately I cannot give you a good bt because I am on a mixed system of Debian Sid and Experimental and the -dbp oackages are conflicting at the moment. But let me explain my problem. In the KDE 4 version of KMail, deleting attachments sometimes failed. I just right-clicked, selected "Delete Attachment" from the context menu and nothing happened. To make it work again, I had to first select another email in the message list and then select the original email again. Then I could resume deleting attachments. Sometimes I had to delete one at a time and do the selection game in between, sometimes I was able to delete 2 to 5 attachments before it was stuck again but that's how it was in KDE 4 for me. Now I installed the KF5 version of KMail (5.2.1) and the behaviour changed a bit. I can delete way more attachments before the deletion process gets stuck and I have to select and re-select as described above. But now, KMail crashes sometimes when deleting an attachment. The getting stuck and sometimes crash behaviour seems to get worse the more attachments I delete. And once I wait for 5 minutes, I can continue without problems ... until it gets worse again. My Mail Server is posteo.de (in case that's helping) and I am connected via IMAP. To test this, just send yourself an email with e.g. 50 attachments and start deleting. Maybe this will also count as a wishlist for a "Delete all attachments" action. :D Reproducible: Always
Minor addition: After the crash, the email I was deleting attachments from, exists twice. Once with the attachments which deletion was in progress and once without it.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
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!
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!
Part of the problem still exists ... but well, if after over two years, the devs did not feel the need to at least comment or ask something here, closing it is fine with me.
Please report those "parts" separately. You were reporting a crash without a backtrace, which just vanished from our radar.