Package Details: jameica 2.10.3-1

Git Clone URL: (read-only, click to copy)
Package Base: jameica
Description: free runtime environment for java applications
Upstream URL:
Licenses: GPL2
Submitter: jakob
Maintainer: fordprefect
Last Packager: fordprefect
Votes: 85
Popularity: 0.62
First Submitted: 2006-10-21 16:11 (UTC)
Last Updated: 2023-01-25 19:46 (UTC)

Dependencies (4)

Sources (9)

Pinned Comments

fordprefect commented on 2020-03-06 08:28 (UTC) (edited on 2022-05-10 09:33 (UTC) by fordprefect)

In case of unknown PGP key run gpg --receive-keys 5A8ED9CFC0DB6C70

Due to widespread keyserver rot the use of is encouraged, e.g. by adding keyserver to your ~/.gnupg/gpg.conf.

Latest Comments

1 2 3 4 5 6 .. 14 Next › Last »

fordprefect commented on 2022-05-10 09:24 (UTC)

Thanks for taking care of this. The question remains what to do in other cases where the developer might not be compliant, but this is not this pkgbases problem. I'll amend the pinned comment with the configured keyserver hint.

fumasu commented on 2022-05-10 08:47 (UTC) (edited on 2022-05-10 08:48 (UTC) by fumasu)

I've contacted the developer and owner of the PGP key. He instructed to also disclose user ID information, so gpg --receive-keys 5A8ED9CFC0DB6C70 once again resolves this issue. As long as the correct keyserver is set in ~/.gnupg/gpg.conf that is.

fordprefect commented on 2022-05-08 18:27 (UTC)

@fumasu: This issue is indeed long open, and no sign of resolution in sight. One could either drop the signatures from the packages entirely, or use the skippgpcheck flag you mention. I'd like to see a discussion on this on aur-general, but don't have the time to initiate and lead it. Feel free to discuss there, and if a general consensus emerges I'll happliy implement it.

fumasu commented on 2022-05-07 13:22 (UTC) (edited on 2022-05-10 08:50 (UTC) by fumasu)

Install fails at PGP check because no key can be obtained. gpg --receive-keys 5A8ED9CFC0DB6C70 fails with no user ID as the de-facto new default keyserver strips user IDs for privacy reasons if not instructed otherwise. Unfortunately that's the case for this key and I also could not find it on any other keyserver. This is a known problem with no solution in sight.

Only workaround for now: makepkg -s --skippgpcheck or yay -Sy jameica --mflags "--skippgpcheck"

Preferred solution: Instruct to distribute user IDs with this key.

Edit: Issue resolved.

fordprefect commented on 2022-04-24 09:23 (UTC) (edited on 2022-05-03 11:58 (UTC) by fordprefect)

The preferred solution to the SecurityManager deprecation is not to circumvent it, but to stay with Java version 17 (see arch wiki on how to manage java versions). A version without SecurityManager is in preparation and for the very urgent is already available in the nightly build. See forum thread for more info.

EDIT: As of v2.10.2 java18 is now supported without workaround, it is safe to update java for jameica now.

Mad_One commented on 2022-04-23 15:33 (UTC)

Can confirm strubbisch's solution works.

strubbisch commented on 2022-04-22 09:13 (UTC)


# Linux Start-Script fuer regulaeren Standalone-Betrieb.
# Jameica wird hierbei mit GUI gestartet.

cd /opt/jameica


if uname -m |grep -q aarch64; then
    _JLP=" -Djava.library.path=lib/swt/linux-arm64"
elif uname -m |grep -q 64; then

# Zur Anpassung der Skalierung auf HiDPI-Displays kann der Parameter "-Dswt.autoScale" verwendet werden.
# Siehe
LIBOVERLAY_SCROLLBAR=0 GDK_NATIVE_WINDOWS=1 SWT_GTK3=1 exec java $_JLP -Xmx512m -Xss64m $_JCONSOLE -jar jameica-linux${archsuffix}.jar $@

Icecube63 commented on 2022-04-22 08:18 (UTC) (edited on 2022-04-22 08:27 (UTC) by Icecube63)

"I added the option "" in "/usr/bin/jameica" in the _JLP-String, then jameica starts."

This don't work for me, can you please post your changed /usr/bin/jameica?

strubbisch commented on 2022-04-20 10:55 (UTC)

The error message is the same as Icecube63 posted.

I added the option "" in "/usr/bin/jameica" in the _JLP-String, then jameica starts.

Icecube63 commented on 2022-04-20 09:58 (UTC) (edited on 2022-04-20 10:01 (UTC) by Icecube63)

With Java 18 there is the following error at startup:

[de.willuhn.jameica.system.Application.startupError] FATAL ERROR WHILE JAMEICA STARTUP java.lang.UnsupportedOperationException: The Security Manager is deprecated and will be removed in a future release at java.base/java.lang.System.setSecurityManager( at at de.willuhn.boot.BootLoader.resolve( at de.willuhn.boot.BootLoader.resolve( at de.willuhn.boot.BootLoader.getBootable( at de.willuhn.jameica.system.Application.init( at de.willuhn.jameica.system.Application.newInstance( at de.willuhn.jameica.Main.main(

The Option "" don't work