http://bugs.winehq.org/show_bug.cgi?id=12464
Erik van Pienbroek erik-wine@vanpienbroek.nl changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |erik-wine@vanpienbroek.nl
--- Comment #11 from Erik van Pienbroek erik-wine@vanpienbroek.nl 2012-05-30 08:11:35 CDT --- With wine 1.5.4 it still isn't possible to have ShellExecute call xdg-open (or use another centralized native file association database) as a fallback path when no file association in the windows registry could be found for the requested extension.
Take for example the .pdf extension. On my Linux environment I've got evince installed which can open .pdf files. In my wine environment there's no pdf reader installed and therefore no file association mentioned in the wine windows registry.
If I try to open some random .pdf file using wine start.exe then the following error is returned:
Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: Success.
The expected behaviour is that ShellExecute also tries to search a centralized native file association database (like the one from xdg-open) when no direct file association could be found in the windows registry