After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 541286 - File atachments cannot be viewed or saved.
File atachments cannot be viewed or saved.
Status: RESOLVED DUPLICATE of bug 534080
Product: evolution
Classification: Applications
Component: Mailer
2.24.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-07-02 17:49 UTC by Paul Wagland
Modified: 2013-09-13 00:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Paul Wagland 2008-07-02 17:49:31 UTC 
Please describe the problem:
Ubuntu intrepid, GNOME evolution 2.23.4
when trying to save or view an attachment, evolution says "Error while Saving attachment." with a subtext of "Could not write data: Success"

In target directory, there is saved a 3030 bytes size file,just a file head

I try to downgrade to hardy, evolution version 2.22.2 ,this bug disappeared

Steps to reproduce:
1.click on a mail with attachments
2.in preview window, find the attachment,and save as the attachment in evolution left-dow side

Actual results:
"Error while Saving attachment." with a subtext of "Could not write data: Success"

Expected results:
The attachment is saved.

Does this happen every time?
yes.

Other information:
See https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/242299 for the original bug report.
Comment 1 Paul Wagland 2008-07-02 17:55:45 UTC 
Also want to say, that for me, this seems to happen with any file type, so it does not appear to be a specific file that is causing issues. I am using the exchange connector, and the rest of the mails appear normally.
Comment 2 C de-Avillez 2008-07-03 01:06:34 UTC 
This was indeed present on 2.34.4, and -- as far as I understand -- fixed somewhere in the road to 2.23.5. I will try to find out more.
Comment 3 Matthew Barnes 2008-07-03 02:06:20 UTC 
Correct, this was fixed in Subversion post 2.23.4 release.  See the later comments in bug #534080 for details.

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