> Does this happen on actual arm hardware? If not then i'm inclined to say it is a bug in whatever emulator you are using and not a bug in raspbian per-se.
Nope, it does not. On 'real HW', an RPi2, it's OK.
Several comments at the referenced bug(s) suggest it's an issue only in QEMU chroot ... but, with newer/current pkg'd jdk.
Supposedly -- untested here, yet, until I can find where to grab it -- older jdk has no such issues.
As Raspbian "in a chroot" is a pretty common/useful chroot env, this certainly "affects" it. In the "it takes two to tango" sense ...
Although it's most likely not Raspbian's "fault", but rather of the JDK &/or qemu, what version of jdk Raspbian pkgs _is_ under control here.
> Does this happen on actual arm hardware? If not then i'm inclined to say it is a bug in whatever emulator you are using and not a bug in raspbian per-se.
Nope, it does not. On 'real HW', an RPi2, it's OK.
Several comments at the referenced bug(s) suggest it's an issue only in QEMU chroot ... but, with newer/current pkg'd jdk.
Supposedly -- untested here, yet, until I can find where to grab it -- older jdk has no such issues.
As Raspbian "in a chroot" is a pretty common/useful chroot env, this certainly "affects" it. In the "it takes two to tango" sense ...
Although it's most likely not Raspbian's "fault", but rather of the JDK &/or qemu, what version of jdk Raspbian pkgs _is_ under control here.