Description of problem: Well, I'm not sure this belongs here, so feel free to assign it to the proper component, if you think it is better. I'm using "mutt", in a "gnome-terminal", to read emails. When a message has an attachment, it is possible to view it (the attachment) directly from "mutt". For example, if there is a pdf attached, "evince" (or whatever is the selected application) is called with, as parameter, something like /tmp/filename.pdf, where "filename.pdf" is the attachment real name. Now, this is done via a chain of events. "mutt" checks "mailcap", which defines "xdg-open %s" for pdf, which calls "evince". Problem is that "xdg-open" returns immediately, after launching "evince" (in the pdf case, of course) and, I suppose, "mutt" deletes the file, so "evince" does not find it (probably sort of race condition, where "evince" loses always). Version-Release number of selected component (if applicable): xdg-utils-1.0.2-16.20091217cvs.fc12.noarch How reproducible: Always, it seems, but could be just 99.9%... Steps to Reproduce: 1. Get an email with attachment, pdf will do fine 2. Open with "mutt" 3. View attachment Actual results: The application called returns an error, usually "File not found" Expected results: The application should find the file. Additional info: Substituting "xdg-open", in "/etc/mailcap", with "evince" does work fine, since "evince" does not return until it is closed. Of course, this *might* be a "mutt" problem, which likely should not delete the file in /tmp, maybe, not sure. Or "xdg-open" should make a second copy, or it should not unconditionally return (maybe difficult). Or it should wait until the file is opened by the application and then return (this would be filesystem dependent, I guess). Anyhow, the current situation it is a bit frustrating, maybe some sort of fix/suggestion would be welcome. Thanks a lot in advance, bye, pg
This is entirely outside of the control of xdg-open. Depending on your environment, xdg-open uses gvfs-open (on gnome) kde-open (on kde) etc... to open files. and is dependent on the behavior of those utilities. For example, if you're on gnome and seeing this, and you're not happy with how gvfs-open behaves, I guess you'll have to take it up with the gvfs maintainers.
Tested and confirmed that gvfs-open indeed returns relatively quickly (and before the application finishes launch and opens anything). reassigning and adjusting summary.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Hi, I changed this issue to F-13, since it happens also there. I hope this is the "info" needed. If not, please let me know. Thanks, bye, pg
I see it in F14 as well.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This is still an issue with F14. Updated accordingly. bye, pg
*** Bug 472402 has been marked as a duplicate of this bug. ***
Upstream bugreport: https://bugzilla.gnome.org/show_bug.cgi?id=652262
confirmed still an issue on f16 with gvfs-1.10.1-2.fc16 small test case: echo 'text!' > foo.txt gvfs-open foo.txt rm -v foo.txt opens an empty text document
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Hi all, so, what's the situation here? Any light at the end of the tunnel? Thanks, bye, pg
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Updated version to keep it warm.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Changed to F-20 to keep it up to date. bye, pg
See https://bugzilla.gnome.org/show_bug.cgi?id=652262 for a workaround and a suggested fix.
marking rawhide/FutureFeature to avoid bug getting autoclosed too
Uhm, how is it going with this? Thanks, bye, pg
See the GNOME bug linked in Comment #19. The current state is that gvfs-open has gone away, but since I've not yet got a version of GNOME that uses its successor, I've not had a look at rewriting my patch yet. I will do so (in the absence of any other fix) when I next upgrade, in August 2018 or so.
gvfs-open has been replaced by "gio open" which resides in glib2, which has the same issue I suppose...
This is correct. The current issue is https://gitlab.gnome.org/GNOME/glib/issues/1208
Closing this since it is an upstream issue.