https://bugs.winehq.org/show_bug.cgi?id=56454
--- Comment #3 from sldev sldev@free.fr ---
I can't seem to reproduce this? Although I also can't seem to get binfmt to trigger from dolphin.
You do need to start it via binfmt_misc, or the bug won't trigger... Try another file manager ?
if I run the executable directly from the terminal using its path it still installs fine.
Yes, this is also what I did report...
Is it possible for you to get a log from the failing case?
Sure, but how do I get such a log ?
When started with binfmt_misc (i.e. for the failing case), there is nothing printed anywhere. This said, I am not a Wine guru, so maybe there is another way ?
I have zero idea why binfmt_misc would even affect this, unless it's picking up wine from the wrong path somehow.
FYI, I also tried various binfmt_misc flags, (P, C, F), including the one dealing with the executable path, to no avail.
Wild guess: maybe the fact the installer is a TlcKit one (i.e. a Tcl/Tk interpreter executing a Tcl/Tk program) is the reason; the privileges would not be propagated properly when started with binfmt_misc ?....