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 700028 - Drag-n-drop export of a file produces a 0 sized PDF file
Drag-n-drop export of a file produces a 0 sized PDF file
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Plugins
3.8.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-plugin-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-05-09 16:56 UTC by awilliam
Modified: 2013-05-10 17:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description awilliam 2013-05-09 16:56:52 UTC
If a message is dragged out of the message list to nautilus is produces a 0 sized file with a .pdf extension.
Comment 1 awilliam 2013-05-09 16:58:05 UTC
Changed mbox format to PDF using -
gsettings set org.gnome.evolution.mail drag-and-drop-save-file-format 'pdf'
Comment 2 awilliam 2013-05-09 17:10:18 UTC
As suggested on the list dragging a message out twice causes a zero sized file the first time, a 'replace' the second time which leaves behind a valid PDF file.  So it is something timing related.
Comment 3 Matthew Barnes 2013-05-10 17:33:49 UTC
Fixed for 3.9.2 and 3.8.2:

https://git.gnome.org/browse/evolution/commit/?id=72f465b17342831163422cad05eaa6e648fffa19

https://git.gnome.org/browse/evolution/commit/?h=gnome-3-8&id=e68fa9016b55ff27cef322c488958876074000e1

Details in the commit message.

This entailed a fairly major mail printing rewrite in the commits just prior, since the PDF is actually generated by a print-to-file operation.  Hopefully I haven't broken printing.

Also, drag-and-drop of multiple messages in PDF mode is broken at the moment.  It generates "part_list != NULL" warnings on the console and you end up with PDF files having only a page number.  Single message drag-and-drop works fine.  I'm treating it as a separate issue since I've seen that warning in other contexts.