Bug 32016 - Mutt cannot open attachments w. xdg-open
Summary: Mutt cannot open attachments w. xdg-open
Status: RESOLVED MOVED
Alias: None
Product: Portland
Classification: Unclassified
Component: xdg-utils (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Portland Bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-01 05:37 UTC by Rex Dieter
Modified: 2019-02-16 13:30 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rex Dieter 2010-12-01 05:37:57 UTC
I'm using Mutt as an example, but there are cases when applications create a tmpfile, and use xdg-open on them.  They assume that the helper application blocks until finished, then cleans up the tmpfile.

Problem being that assumption is false.  At least in the kde-open case, it returns immediately, and the application cleans up the file prior to it actually being opened.  kde-open does have a --tempfile option,

$ kde-open --help-kde-tempfile
...
KDE-tempfile options:
--tempfile  The files/URLs opened by the application will be deleted after use

Obviously, great care needs to be taken if using this, however.


See also downstream report,
https://bugzilla.redhat.com/show_bug.cgi?id=653249
Comment 1 PMouse 2011-07-22 14:16:26 UTC
Affects alpine, too.
Comment 2 Rex Dieter 2012-01-05 11:30:10 UTC
I can no longer reproduce this with kde-open on kde-4.6.5 at least.

gvfs-1.6.6 seems to (still) have issues however, see
http://bugzilla.gnome.org/show_bug.cgi?id=652262
Comment 3 GitLab Migration User 2019-02-16 13:30:14 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xdg/xdg-utils/issues/39.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.