Bug 504518 - Kmail crashes when reorganizing (moving) emails
Summary: Kmail crashes when reorganizing (moving) emails
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: 10
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-07 19:50 UTC by Arthur Pemberton
Modified: 2009-09-08 02:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-08 02:41:30 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Kmail KCrash (4.53 KB, text/plain)
2009-06-07 19:50 UTC, Arthur Pemberton 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 163071 0 None None None Never
KDE Software Compilation 195598 0 None None None Never

Description Arthur Pemberton 2009-06-07 19:50:05 UTC 
Created attachment 346792 [details]
Kmail KCrash

All I was doing, is moving email from the inbox of one IMAP account, to
sub-folders of another account I use for archival. And then Kmail goes poof. It
does this fairly frequently.
Comment 1 Steven M. Parrish 2009-06-10 13:20:25 UTC 
Thank you for taking the time to report this issue.

This is an issue that needs to be addressed by the upstream developers. Please report this at http://bugs.kde.org and then add the upstream report information to this report.  We will monitor the upstream report for a resolution to this issue.
Comment 2 Arthur Pemberton 2009-06-22 04:20:38 UTC 
Upstream tracking this at http://bugs.kde.org/show_bug.cgi?id=163071
Comment 3 Steven M. Parrish 2009-09-08 02:41:30 UTC 
Thanks for reporting this upstream.  Going to close this report and will monitor upstream for resolution.

-- 
Steven M. Parrish - KDE Triage Master
                  - PackageKit Triager
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Note You need to log in before you can comment on or make changes to this bug.