Bug 1201871

Thank you for the report!

Unfortunately, there isn't much we can do about this. How often users run 32bit Java on 64bit machines? Don't you need to install 32bit Java version manually?

But perhaps we could add a run time check to javapackages-tools.

Mikolaj, I need your expertise, what do you think about this?

Java is exempt from multilib - installing 32-bit Java on 64-bit system is not supported. This was approved by FESCo, see https://fedorahosted.org/fesco/ticket/961

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Mikolaj, is there anything I can do to fix the issue in abrt-java-connector?

As noted in comment #2, the whole Java environment in Fedora (including JVM and Java libraries) does not support multilib. This is a result of a long discussion within Java SIG, which was approved by Fedora Engineering Steering Committee. You shouldn't expect 32-bit JVM to work with system applications on 64-bit system. Also, as a result of this, Java generally doesn't use lib64 directory - all architecture-specific libraries are installed in /usr/lib/.

Users shouldn't be installing 32-bit Java on 64-bit systems. The fact that 32-bit Java is even available in 64-bit repos is a bug in release engineering process - Java was supposed to be multilib-excluded per maintainer request: https://fedorahosted.org/rel-eng/ticket/5762

Moreover, in most cases there should be no reason to run 32-bit JVM on 64-bit systems. If for some reason it's necessary, then virtualization technology can be used.

Due to above reasons I think that this bug should be closed as WONTFIX.

(In reply to Jakub Filak from comment #5)
> Mikolaj, is there anything I can do to fix the issue in abrt-java-connector?

If you *really* want this, you sohuld restart discussion about Java multilib status.

This bug is currently reported against a Fedora version which is already unsuported.
I am changing the version to '27', the latest supported release.

Please check whether this bug is still an issue on the '27' release.
If you find this bug not being applicable on this release, please close it.

I assume that this issue is completely moot by now as on F28 x86_64, `dnf install java-1.8.0-openjdk-headless.i686` fails with "No match for argument: java-1.8.0-openjdk-headless.i686" for me, and I was told on #fedora IRC that that's probably intentional.

...so lets close it