On Fedora 29, D-Bus clients connect to dbus-daemon, whereas on Fedora 30, D-Bus clients connect to dbus-broker. Hope the helps.Īs the Transport class realizes low level access via UnixSockets, I compared the two Fedora VMs with ss -a | grep dbus and that lead to the root cause of the issue. Please note: this is not the script mentioned by above but the current build process in manual steps. appimage-build.sh 1.5.0 <- Version from pom files above
CRYPTOMATOR LOGO INSTALL
Mvn -f main/pom.xml clean install -Prelease -DskipTests=trueĬp main/buildkit/target/buildkit-linux.zip.
# In all pom.xml files: change from 1.5.0-SNAPSHOT to 1.5.0, otherwise AppImage does not start tools/appimagekit/appimagetool.AppImageĬd. tools/appimagekit/appimagetool.AppImageĬhmod +x. I suspect that running Cryptomator as an AppImage causes the trouble here.ĭownloading Fedora 29 now to install another virtual machine and to see if this makes any difference.Ĭurl -L -o. The Exception is also thrown from running the AppImage on a clean install of Fedora 30 with GNOME desktop environment.īut building and running Cryptomator on the same platform within IntelliJ does work flawlessly. At .nnect(Transport.java:150)Īt .Transport.(Transport.java:70)Īt .AbstractConnection.(AbstractConnection.java:149)Īt .impl.DBusConnection.(DBusConnection.java:284)Īt .(DBusConnection.java:122)Īt .(DBusConnection.java:142)Īt .(DBusConnection.java:200)Īt .(DBusConnection.java:157)Īt .(TransportEncryption.java:36)Īt .SimpleCollection.init(SimpleCollection.java:112)
0 kommentar(er)
