Arch Linux User Repository

80.4-2 adds OAuth authorization and thus the possibility to create a portfolio account for obtaining historic data.

Bevan implemented this crucial feature in the current PKGBUILD – and I'm very happy to welcome him as co-maintainer. :)

Thanks to Bevan, we now have a simple and elegant (compared to my attempt) workaround that lets the PKGBUILD download and use the most recent version of maven (currently 3.9.4). Should not need any intervention from you. :)

80.4-2 adds OAuth authorization and thus the possibility to create a portfolio account for obtaining historic data.

Bevan implemented this crucial feature in the current PKGBUILD – and I'm very happy to welcome him as co-maintainer. :)

Hi @MajorMayer,

80.4-2 fixes this issue by downloading the new version of maven (3.9.12).

The maven file is not found anymore:

Erstelle portfolio... ==> Erstelle Paket: portfolio 0.80.4-1 (Do 18 Dez 2025 12:24:51 CET) ==> Prüfe Laufzeit-Abhängigkeiten... ==> Prüfe Buildtime-Abhängigkeiten... ==> Empfange Quellen... -> 0.80.4.tar.gz gefunden -> Lade apache-maven-3.9.11-bin.tar.gz herunter... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 ==> FEHLER: Fehler beim Download von https://dlcdn.apache.org/maven/maven-3/3.9.11/binaries/apache-maven-3.9.11-bin.tar.gz Breche ab...

Hi @poetter,

we need help from upstream to get this feature working. Bevan wanted to contact the developer to agree on how to include OAUth authorization, but I haven't heard back from him yet. I hope that we will be able to support this feature soon.

Hi @Cobra,

I got a problem with portfolios new historic data feature, that requires to open your browser and login to the website. Instead of the browser opening, I get this error message:

Wed Nov 19 21:05:20 CET 2025 Unable to authenticate (application is not configured correctly).

name.abuchen.portfolio.oauth.AuthenticationException: Unable to authenticate (application is not configured correctly). at name.abuchen.portfolio.oauth.OAuthClient.getAPIAccessToken(OAuthClient.java:94) at name.abuchen.portfolio.ui.jobs.priceupdate.UpdatePricesJob.run(UpdatePricesJob.java:103) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

Running portfolio from the x86 package, the website provides, the error does not happen. Any idea how to fix this?

Thank you very much, Bevan. Works like a charm. :)

Hi @Cobra. You're right: That solution was indeed overcomplicated. PortfolioPerformance just uses the java executable found via $PATH, so it is sufficient to set PATH=$JAVA_HOME/bin:$PATH with $JAVA_HOME being set using archlinux-java-run. No need for bubblewrap as an additional dependency.

Still, a run script and a runtime dependency on archlinux-java-run is required. I prepared a git patch that can be applied to this repository via:

curl https://pastebin.com/raw/40HRFNb5 | git am

PortfolioPerformance 0.80.0 just came out. I hope you don't mind that I sneaked that update right into that patch 😉

Regarding the option to just set Java 21 as default: That's a valid solution if you just want to get PortfolioPerformance working. However, other Java software packages might require different versions. So, making sure that a valid version is used via a run script seems to me to be the best option.

@Bevan: Thanks for identifying this issue and proposing a solution. Frankly, it looks like an overcomplication to me, but then, I'm content to run Java 21 by default and at all time. For a Java developer, this is certainly way too restrictive.

I'm willing to implement your solution, but I would appreciate help with implementing the shellscript into the PKGBUILD.

PortfolioPerformance does not work if java-25-openjdk (or any other Java 25) is selected as default Java environment via archlinux-java. Java 25 was pushed about an hour ago to the repositories, so this is a fairly new issue.

I found a workaround. Feel free to adopt this here:

1. Promote archlinux-java-run from makedepends to depends
2. Add bubblewrap as dependency
3. Replace the symlink from /usr/bin/portfolio to /usr/share/portfolio/PortfolioPerformance by a shell script with the following contents:

#!/bin/bash

export JAVA_HOME=$(archlinux-java-run --min 21 --max 24 -j)

bwrap --bind / / --bind $JAVA_HOME /usr/lib/jvm/default-runtime /usr/share/portfolio/PortfolioPerformance

Explanation: For most applications, setting $JAVA_HOME accordingly is sufficient. Unfortunately, the PortfolioPerformance binary just executes /usr/bin/java which then again uses the symlink under /usr/lib/jvm/default-runtime to run the Java implementation selected via archlinux-java. Using bubblewrap, we can fake /usr/lib/jvm/default-runtime to point to the location of a suitable Java environment identified via archlinux-java-run. The dependency on java-environment=21 guarantees that at least one such environment is installed.

The package no longer builds for me due to a unit test failing

The issue has been resolved upstream. It was caused by mixed locale settings.