Hello, xfce-base/exo-0.10.2-r1 xfce-base/thunar-1.6.3 Description: Trying to troubleshoot opening a pdf from the command line (reproducing a problem with firefox opening pdfs): /usr/lib64/xfce4/exo-1/exo-helper-1 --launch FileManager /home/robin/test.pdf Steps to reproduce: Using Preferred Applications File Manager set to Thunar. "/usr/lib64/xfce4/exo-1/exo-helper-1 --launch FileManager /home/robin/test.pdf" pdf pops up in Okular. Try with preferred file manager to: Caja - get stuck with recycling exo-helper process at 100% CPU. Nautilus - opens the containing folder but not the actual pdf Reproducible: Always. ~/.local/share/applications/mimeapps.list contains: application/pdf=kde4-okularApplication_pdf.desktop x-scheme-handler/file=exo-file-manager.desktop Thanks
By attempting to open a PDF with the file manager, what is the expected outcome?
Firefox at least expects the pdf to be opened in the preferred application if opened with the filemanager. Somehow this just works for Thunar, but not for the others - they just hang and consume cpu until killed. so expected outcome: pdf opens in okular.
I'll take a look at the issue with Caja. With Nautilus and Nemo, the file manager just opens at the file. This is an implementation decision with the file manager, and nothing can be done with exo except ignore the FileManager parameter and launch the file normally.
I think Nautilus and Nemo have it right in this case (that is: opening at the file, instead of opening the file). There are many instances where this is a useful feature, for example the "open containing folder" feature in gnome-search-tool and the similar "open parent folder" in recoll. These should open the file manager with the proper file selected; but that does not work in Thunar, and that's a crying shame.
Reassigning to Thunar, since this functionality is specific to the file manager.
> I think Nautilus and Nemo have it right in this case (that is: opening at the file, instead of opening the file). What makes you think that ? If some other application wants to open just the containing folder, why than the full file path is passed as argument, instead of the containing folder path ? To just hang and consume 100% CPU does not look very "right" for me. So IMO thunar does it right. . If other file-managers cannot handle a path up to the file, they should either throw an error, or just open the parent folder. But that's not a thunar prolem and not an exo problem. You dont have to use exo for that purpose. You as well can use the API of org.freedesktop.FileManager1: https://wiki.xfce.org/thunar/dev/test_dbus_calls ( thunar just got support for it in master )
(In reply to alexxcons from comment #6) > > I think Nautilus and Nemo have it right in this case (that is: opening at the file, instead of opening the file). > What makes you think that ? > If some other application wants to open just the containing folder, why than > the full file path is passed as argument, instead of the containing folder > path The idea is that if a folder path is passed, the file manager simply opens at that folder. But if a full file path is passed, the file manager opens at that folder, and then highlights the proper file. It's a thing of beauty, I tell you :-) Anyway I've long since written my own script to do that (and using another filemanager nowadays) so feel free to ignore.
Ok, agreed. Sorry, I did not read your comment properly last time. There is already an open bug for it: Bug #8349