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 319297 - Path to evolution attachments when opened in other applications are unuseable
Path to evolution attachments when opened in other applications are unuseable
Status: RESOLVED DUPLICATE of bug 322160
Product: evolution
Classification: Applications
Component: Mailer
2.4.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-10-20 10:12 UTC by Daniel Holbach
Modified: 2006-05-25 22:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel Holbach 2005-10-20 10:12:20 UTC
Version details: 2.4.1
Distribution/Version: Ubuntu Breezy

Forwarded from http://bugzilla.ubuntu.com/18160

Open any attachment up in another application.  When you are done, save the
document using just the save method.  The document is saved to
/home/user/.evolution/cache/tmp/evolution-tmp-garbage/ ...

This is completely unuseable by a novice user.  When they are done, they simply
click save, or click save-as and then change the file name.

Somehow, evolution and/or the other applications should cooperate such that the
default place to save the new file is /home/user/Documents/ or at least /home/user/
Comment 1 parthasarathi susarla 2005-10-20 10:26:47 UTC
I think this is an issue with the other applications, since Saving the
attachment using another app, is what evolution cannot control. Although I
really understand what you are saying.
Comment 2 André Klapper 2005-10-20 11:15:33 UTC
i'd also say that this is not an evolution bug. where should evolution pass that
information?!
Comment 3 Lakin Wecker 2005-10-20 15:07:58 UTC
Perhaps evolution could warn the user that they are opening the document in a
tmp directory and that they should be careful to save the Document to their
desktop/Document folder when they are finished?

I was the original reporter from Ubuntu.  I spent an hour on the phone with my
dad trying to find his 'edited' document until I finally stumbled across the
fact that he was saving it in such a wierd place.  

I contemplated filing a bug against openoffice and then decided not to for the
following reasons:

Openoffice and the other applications can't possibly check for all the
directories where evolution and other applications might store temp data.  They
can't check for .hidden directories because the user may actually _want_ to save
the file there.  On the other hand, evolution _knows_ that this is a cache
location and that the user will most likely _not_ want to keep their document
there.  Somehow evolution should deal with that.  When A user specifically asks
for a document to be shown in evolution, there is a good chance they might be
editing it.  So there is an argument for copying the file automatically to
/home/user/Documents and then opening it.   On the other hand, they may not want
to edit it, and may want to only view it, in which case there is an argument to
leave it in the cache/temp directory.

This isn't completely evolution's fault, but it is one of the main applications
where it is noticeable within gnome.  The problem can be solved within the gnome
 community, possibly by providing a method for applications to put expiring
Documents in the Documents folder, where if the user never saves the Document,
eventually the Document dissappears.  Otherwise, the Document stays in their folder.
Comment 4 Lakin Wecker 2005-10-20 15:12:15 UTC
Perhaps adding a menu option to the attachment with the concept of 'Edit
Document'  is appropriate?  ( I haven't completely thought this through, it's
just a brainstorm ). 

This menu item would copy the file to their Documents and then open it in the
appropriate program?
Comment 5 Jeffrey Stedfast 2005-10-20 15:42:14 UTC
well, 1 easy fix would be to make the viewer open the file in some read-only
mode. this might require changes the mime-info db's on how to launch apps
read-only, but would solve the confusion.
Comment 6 Lakin Wecker 2005-10-21 23:14:32 UTC
It would solve the confusion.  But it reduces a users ability to collaborate on
a document.  The ideal solution would be something which facilitates:

User A makes document and sends it to User B.
User B opens from their mail client, edits it.
User B then sends it back to User A.
User A opens it from their mail client, edits it.
 ...  repeat

I'm not sure what that solution is yet, but I'm willing to let this bug report
be turned into a wish, and let the discussion take place here. 
Comment 7 André Klapper 2006-05-25 22:06:10 UTC
this is fixed in evolution 2.6, see bug 322160

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