https://bugs.winehq.org/show_bug.cgi?id=57229
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #1 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
(In reply to ezbie from comment #0)
I removed specific data for privacy. This URL should redirect to the originating app, but Wine doesn’t handle this correctly. Solving this involves modifying xdg MIME types, which is complex and imperfect. Associating a Wine app with the cron:// URL protocol means all such URLs are sent to a single app, which may not be the correct one.
No, that's not how custom schemes and protocol handlers are designed. Defining the WINE application as the default protocol handler for that custom URI scheme is the only way. Note that it's the same on Windows: If multiple applications are registered as protocol handlers for the same URI scheme, one of them will be the default, and it'll open all URI from that scheme in that app, unless an 'ask the user' mechanism is used.
WINE should generate a protocol handler desktop file when the application asks to register a custom URL scheme, but in my case, it didn't happen and I had to define a protocol handler manually.
Please, can you give the result of those commands ($ is the terminal prompt):
$ xdg-mime query default x-scheme-handler/cron
$ find ~/.local/share/applications/ -type f -exec grep -iH "x-scheme-handler/cron" '{}' ;
Regards.