Bug 278837 - kmail2 usually saves or copies attachments with target size 0 (zero) using list view as source
Summary: kmail2 usually saves or copies attachments with target size 0 (zero) using l...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 1.99.0
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-30 08:04 UTC by Ferdinand Gassauer
Modified: 2017-01-07 22:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ferdinand Gassauer 2011-07-30 08:04:47 UTC 
Version:           1.99.0 (using KDE 4.7.0) 
OS:                Linux

trying to save or to attach attachments to other mails using list view as source very often the result is a file with size 0

workaround - open mail in separate window

classified as major, because deleting the original mail after saving the attachment (with size 0) causes data loss 

Reproducible: Sometimes

Steps to Reproduce:
drag attachment from preview window to new mail or save the attachment with RMB

Actual Results:  
file size is very often 0

Expected Results:  
copy the full size attachment

OS: Linux (x86_64) release 2.6.37.6-0.5-desktop
Compiler: gcc
Comment 1 Laurent Montel 2011-07-30 12:34:12 UTC 
known bug.
This function is not implemented in viewer will reimplement it soon.
Regards
Comment 2 Denis Kurz 2016-09-24 17:53:54 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:18:25 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.