Arch Linux User Repository

Very nice. I can also confirm that v26.2.114 works as expected. Login works with cachy-os (kernel 7.1.3-2) with KDE Plasma 6 via Wayland. I'm now also able to change the closing behaviour to minimize instead of quit.

Just a small thing left, but there's a very simple/easy workaround for that (just in case that someone else encounters the same "issue"). In my case I cannot re-open the UI from system tray. In this case, just try to run a second instance of LRZ and choose quit on startup to get the UI but avoid running a second LRZ-process.

Thanks a lot @chgreu for all your effort!

Best regards, Deph

Thank you @chgreu. v26.2.114 seems to contain already the fix.

To repair/restore full functionality on KDE, please add the following line to /usr/share/LRZ_Sync_Share/LRZ_Sync_Share-Client.sh (in the corresponding stanza):

JAVA_ADD="$JAVA_ADD -Djdk.lang.Process.launchMechanism=fork"

(Will be added in future versions by the manufacturer PowerFolder)

Hello chgreu,

thanks for the hint. I wrote to the LRZ-support. The problem seems to be a specific problem with the current KDE-Plasma6 and browser-forwarding of the LDAP-Login request. However, they are already working on a fix.

Nevertheless, there is a workaround for that problem opening the LDAP-site due to another desktop. I used gnome. Here are my steps, assuming KDE Plasma 6 on wayland and LRZ-syncshare is installed.

1.) Change your SDDM in kde system settings to something allowing to choose the desktop-session type (e.g. CachyOS Simply Black)
2.) Install gnome-shell (needed to start gnome desktop) and gnome-session to get the gnome*.desktop files for the SDDM (/usr/share/wayland-session)
3.) Logout to SDDM (not lock-screen!)
4.) Choose gnome as desktop and re-login.
5.) Start LRZ and try to login by choosing your institute. Maybe the screen-share window will appear. I got rid of it by allowing my main-screen once. Afterwards I was able to choose a institute from the list.
-> Your browser should now open to get the LDAP-token.
6.) Use your institutes site to log in and wait until LRZ confirms the login. The Token is now stored by LRZ and can be used by the KDE-session.
7.) You're done. Logout, and set everything back to normal (KDE). Optionally you can uninstall the installed gnome-packages for shell and session.

Note, I found that gnome-desktop was a pre-installed package, even as I choosed KDE only during cachy-os installation. Moreover, LRZ still behaves a bit buggy (cannot open from tray without trying to start LRZ a second time) but at least it does its sync-job now.

Best regards, Deph

Hi Dephrilibrium, it looks like there is a certificate issue at the login server (IdP) of the Shibboleth institution that you have selected. At first glance, this does not appear to be a problem that is caused by the client software itself. You could report this problem to the institution (see https://doku.lrz.de/sync+share-servicedesks-11476018.html) or open a ticket at the LRZ (see https://servicedesk.lrz.de/ql/create/106).

Same problem as Arcalium. No user/password field when selecting my institute.

I tried to tweak around by:
1. selecting another institute which shows me login-fields,
2. entering my user and password
3. and switching back to my institute
=> Didn't worked.

I also installed different versions of jre- and jdk-packages without any success.

Afterwards also installed the latest test-package from https://aur.sasrepo.nas.lrz.de/ (LRZ_Sync_Share-v23.4.100-1-x86_64.pkg.tar.zst), but same error again.

The logs tell me:

[21:22:39] WARN   [PathUtils]: Unable to check, if path /home/<ArchUser>/LRZ Sync+Share is a network drive. java.io.IOException: Cannot run program "df": error=13, Keine Berechtigung
[21:22:40] WARN   [TrayIconManager]: Unable to whitelist application for system tray icon. java.io.IOException: Cannot run program "gsettings": error=13, Keine Berechtigung
[21:22:40] WARN   [TrayIconManager]: Unable to whitelist application for system tray icon. java.io.IOException: Cannot run program "gsettings": error=13, Keine Berechtigung
[21:22:44] WARN   [ServerClient]: Unable to login: de.dal33t.powerfolder.security.SecurityException: edu.kit.scc.dei.ecplean.ECPUnauthorizedException: User not authorized: HttpResponseProxy{HTTP/1.1 401 Unauthorized [Server: nginx/1.22.1, Date: Tue, 04 Nov 2025 20:22:42 GMT, Content-Type: text/html; charset=iso-8859-1, Content-Length: 452, Connection: keep-alive, WWW-Authenticate: Basic realm="Shibboleth Identity Provider - ECP profile"] ResponseEntityProxy{[Content-Type: text/html; charset=iso-8859-1,Content-Length: 452,Chunked: false]}}
[21:22:44] WARN   [ServerClient]: edu.kit.scc.dei.ecplean.ECPUnauthorizedException: User not authorized: HttpResponseProxy{HTTP/1.1 401 Unauthorized [Server: nginx/1.22.1, Date: Tue, 04 Nov 2025 20:22:42 GMT, Content-Type: text/html; charset=iso-8859-1, Content-Length: 452, Connection: keep-alive, WWW-Authenticate: Basic realm="Shibboleth Identity Provider - ECP profile"] ResponseEntityProxy{[Content-Type: text/html; charset=iso-8859-1,Content-Length: 452,Chunked: false]}}
de.dal33t.powerfolder.security.SecurityException: edu.kit.scc.dei.ecplean.ECPUnauthorizedException: User not authorized: HttpResponseProxy{HTTP/1.1 401 Unauthorized [Server: nginx/1.22.1, Date: Tue, 04 Nov 2025 20:22:42 GMT, Content-Type: text/html; charset=iso-8859-1, Content-Length: 452, Connection: keep-alive, WWW-Authenticate: Basic realm="Shibboleth Identity Provider - ECP profile"] ResponseEntityProxy{[Content-Type: text/html; charset=iso-8859-1,Content-Length: 452,Chunked: false]}}
    at de.dal33t.powerfolder.clientserver.ServerClient.prepareShibbolethLogin(Unknown Source)
    at de.dal33t.powerfolder.clientserver.ServerClient.login0(Unknown Source)
    at de.dal33t.powerfolder.clientserver.ServerClient.primaryServerConnected0(Unknown Source)
    at de.dal33t.powerfolder.clientserver.ServerClient.primaryServerConnected(Unknown Source)
    at de.dal33t.powerfolder.Member.completeHandshake(Unknown Source)
    at de.dal33t.powerfolder.Member.setPeer(Unknown Source)
    at de.dal33t.powerfolder.Member.reconnect(Unknown Source)
    at de.dal33t.powerfolder.net.ReconnectManager$Reconnector.run(Unknown Source)
Caused by: edu.kit.scc.dei.ecplean.ECPUnauthorizedException: User not authorized: HttpResponseProxy{HTTP/1.1 401 Unauthorized [Server: nginx/1.22.1, Date: Tue, 04 Nov 2025 20:22:42 GMT, Content-Type: text/html; charset=iso-8859-1, Content-Length: 452, Connection: keep-alive, WWW-Authenticate: Basic realm="Shibboleth Identity Provider - ECP profile"] ResponseEntityProxy{[Content-Type: text/html; charset=iso-8859-1,Content-Length: 452,Chunked: false]}}
    at edu.kit.scc.dei.ecplean.ECPAuthenticatorBase.authenticateIdP(Unknown Source)
    at edu.kit.scc.dei.ecplean.ECPAuthenticator.authenticate(Unknown Source)
    ... 8 more

Its just warnings, but I tested df and gsettings. I'm able to run them as the <ArchUser>.

I'm using cachy-os (kde plasma6, wayland)

Hi @chgreu, thanks for the tips, I did not know this repository. I updated the PKGBUILD accordingly.

Hi there, LRZ Sync+Share provides a repository site that can be used to download the *.tar.gz software package: * https://tgz.sasrepo.nas.lrz.de

Also checksums (SHA256) are provided: * https://sasrepo.nas.lrz.de/SHA256SUMS.txt

The following changes could be made to improve the PKGBUILD script: 1. branch=stable 2. source=("LRZ_Sync_Share_v${pkgver}_Linux.tar.gz::https://tgz.sasrepo.nas.lrz.de/${branch}/LRZ_Sync_Share_v$3{pkgver}_Linux.tar.gz") 3. sha256sums=("$(curl -s https://sasrepo.nas.lrz.de/SHA256SUMS.txt | grep LRZ_Sync_Share_v${pkgver}_Linux.tar.gz | head -n 1 | cut -d ' ' -f 1)")

Hi there, the GUI drop down menu for selecting institution does not work on KDE - it opens the system tray for screen sharing. Any ideas why and how to fix it ? Thank you in advance

Hi there,

thanks for your efforts, but it didn't work when I wanted to install the package using pamac on manjaro. I guess there is a new version of LRZ Sync and Share Client but the checksums aren't adjusted yet.

I made it work with makepkg -si --skipchecksums