Dear Andreas.
I put here the results of the commands. Home that helps...
$ sudo update-binfmts --display jarwrapper
update-binfmts: warning: jarwrapper not in database of installed binary
formats.
update-binfmts: exiting due to previous errors
$ sudo update-binfmts --display jar
update-binfmts: warning: jar not in database of installed binary formats.
update-binfmts: exiting due to previous errors
Thanks !
Regards
Le 06/05/2017 à 00:16, Andreas Tille a écrit :
Control: severity -1 important
Control: tags -1 moreinfo
Hi Tony,
On Fri, Apr 28, 2017 at 08:11:52AM -0700, tony mancill wrote:
This does sound like an issue we had in the past with jarwrapper and
binfmt-support. IIRC, Colin Watson was able to track down the source of
this, but at the moment I cannot locate the details of that exchange. It
was something along the lines of there being multiple interpreters
registered for the given binfmt.
Thanks for ths info.
If we know that the user's kernel supports binfmt_misc, then we should be
able to figure out what's happening. The output of "sudo update-binfmts
--display jarwrapper" (should point to jarwrapper) and "sudo update-binfmts
--display jar" (should point to jexec) might be informative. I'll try to
reproduce locally and report back.
I've reduced the severity of this bug from grave to important and have
added the tag moreinfo. Jerome, could you please provide the said info?
Kind regards
Andreas.
--
-- Jérôme
L'oisiveté est, dit-on, la mère de tous les vices,
mais l'excès de travail est le père de toutes les soumissions.
(Albert Jacquard)