Hi, I’m using Linux Mint 21.3, and starting with VictronConnect version 64-v6.15, the AppImage no longer launches. It doesn’t show any error — it simply doesn’t start. Previous versions, including 64-v6.15, work fine. Has anyone else experienced this issue or found a solution? Thanks!
I have just downloaded 6.17. It did not start. Also no error messages. OS is Linux Mint 22.1
Hi,
Thank you for reporting this.
It looks like v6.17 requires a newer libc, 2.38, and libstdc++, 3.4.32, and this was 2.29 and 3.4.26. This might be the problem for Linux Mint 21.3. We will investigate whether we can revert this change.
@Dirk_S
Can you please look in /tmp/VictronConnect.log whether that contains hints on what could be wrong?
With kind regards,
Thiemo van Engelen
Hi.
The contents of /tmp/VictronConnect.log are: /tmp/.mount_VictroL8gKJQ//bin/VictronConnect: /lib/x86_64-linux-gnu/libstdc++.so.6: version GLIBCXX_3.4.32' not found (required by /tmp/.mount_VictroL8gKJQ//bin/VictronConnect) /tmp/.mount_VictroL8gKJQ//bin/VictronConnect: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.38’ not found (required by /tmp/.mount_VictroL8gKJQ//bin/VictronConnect)
Thank you. Regards, Joan.
Hi @Juanht
So in Linux Mint 21.3, the libc and libstdc++ are indeed to old for VictronConnect v6.17. At this moment it is unknown whether the minimum version will change in future versions of VictronConnect. So for now you can either use VictronConnect v6.15 or perhaps upgrade to a newer Linux Mint.
Kind regards,
Thiemo van Engelen
@thiemovanengelen : this directory doesn’t exists unfortunately
Hi @Dirk_S
What directory does not exist, /tmp ?? If so, can you create the directory?
/tmp/VictronConnect.log should be a file in the /tmp directory after starting and closing the VictronConnect AppImage.
With kind regards,
Thiemo van Engelen
But 22.1 is the latest version ATM on their webpage…
And 21.3 has a Long term support release (LTS), supported until April 2027.
From what I was told, the applications should at least be compatible with the overlapping/current LTS, because LTS exist for a reason…
Hi @Dirk_S,
I just tested VictronConnect v6.17 on clean Mint 22.1 Cinnamon install (in a virtual). I need to do 2 things to get this working:
- Make the file executable. This can be done either via a terminal (chmod +x <..path to VictronConnect-x86_64-v6.17.AppImage…>) or via the file browser (open the properties of VictronConnect-x86_64-v6.17.AppImage, go to the permissions tab and enable “Allow executing file as program”)
- Install libxcb-cursor0 (execute ‘sudo apt install libxcb-cursor0’ in a terminal)
Then VictronConnect started (and a log file /tmp/VictronConnect.log was made).
With kind regards,
Thiemo van Engelen
Hi @alexpescaru ,
Update to a newer version was targeted at Juanht, as he is running Linux Min 21.3. And as mentioned, we will be investigating whether we can revert this libc and libstdc++ requirement as this was unintentional and we do would like to support older (LTS) versions of distributions. But to be fair, the Linux version of VictronConnect does not have our focus so there is no idea on if or when this will be fixed.
With kind regards,
Thiemo van Engelen
1 Like
Thank you for explaining it and finding a solution above. 
Sorry for misunderstanding… 
Hello,
I understand that this is an issue related to the libstdc++ library included in the Linux Mint 21.3 distribution, and that providing support for Linux is currently not a priority. Nevertheless, I appreciate your work and attention.
The problem persists even after following your instructions. Although the /tmp/VictronConnect.log file is generated, the application does not start properly. It’s also worth noting that updating libstdc++ on Linux Mint 21.3 is not advisable, as it may pose a serious risk to system stability.
I’m attaching a screenshot of the commands executed, in case it might be helpful.
Thank you again and best regards,
Joan
Hi @Juanht
There are 2 issues going on in this thread.
The first is your issue. This is due to an old libc / libstdc++ on Mint 21.3. As it is indeed not advised to update them as they are they are more or less tied to the Mint version, the only option for now is to upgrade to Mint 22.1 or downgrade VictronConnect. As said, we are seeing if we can improve this situation by not depending on such a new libc / libstdc++.
The second issue is the one of Dirk_S, who is running Mint 22.1. Here, the sudo apt install libxcb-cursor0 is needed to get it running.
With kind regards,
Thiemo van Engelen
1 Like
The AppImage doesn’t work on Ubuntu 24.04.2 LTS either. It creates /tmp/VictronConnect.log, but then just hangs:
qt.core.qobject.connect: QObject::connect(QObject, Unknown): invalid nullptr parameter
qt.core.qobject.connect: QObject::connect(QObject, Unknown): invalid nullptr parameter
WARN 2025-05-08T00:22:02.958 QApplication: invalid style override 'gtk' passed, ignoring it.
Available styles: Windows, Fusion
WARN 2025-05-08T00:22:03.011 [VRGTLR] init translation function defined for vreg "VE_REG_LINK_BINARY_SWITCH_BANK_STATUS" but no translation function found!!
WARN 2025-05-08T00:22:03.011 [VRGTLR] init translation function defined for vreg "VE_REG_LINK_BINARY_SWITCH_BANK_MASK" but no translation function found!!
WARN 2025-05-08T00:22:03.019 [VRGTLR] init path "/Mgmt/ProcessName" has no vreg defined
WARN 2025-05-08T00:22:03.019 [VRGTLR] init path "/Mgmt/ProcessVersion" has no vreg defined
WARN 2025-05-08T00:22:03.019 [VRGTLR] init path "/Mgmt/Connection" has no vreg defined
WARN 2025-05-08T00:22:03.019 [VRGTLR] init path "/Connected" has no vreg defined
WARN 2025-05-08T00:22:03.019 [VRGTLR] init path "/N2KUniqueNumber" has no vreg defined
WARN 2025-05-08T00:22:03.021 [VRGTLR] init path "/Alarms/LowBattery" has no vreg defined
WARN 2025-05-08T00:22:03.021 [VRGTLR] init path "/Alarms/FuseBlown" has no vreg defined
WARN 2025-05-08T00:22:03.029 [VRGTLR] init path "/Update/StartResult" has no vreg defined
WARN 2025-05-08T00:22:03.029 [VRGTLR] init path "/PinCodeResult" has no vreg defined
WARN 2025-05-08T00:22:03.029 [VRGTLR] init path "/PukCodeResult" has no vreg defined
WARN 2025-05-08T00:22:03.497 [VRMPIN] START SYNC DATABASE TO MAP 0
WARN 2025-05-08T00:22:03.505 qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "stateChanged"
WARN 2025-05-08T00:22:03.505 qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "connectivityChanged"
WARN 2025-05-08T00:22:03.508 qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "deviceTypeChanged"
WARN 2025-05-08T00:22:03.509 qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "meteredChanged"
WARN 2025-05-08T00:22:03.719 QQmlApplicationEngine failed to load component
WARN 2025-05-08T00:22:03.719 qrc:/qml/main.qml: module "gtk" is not installed
I have the package libxcb-cursor0 installed, but it appears that there are more dependencies. I thought the whole point of an AppImage is that is contains all dependencies so that it runs everywhere.
Hi @thiemovanengelen
thanks for your explanation. I don’t really need the Linux version. I only tried to check if i get the same error or malfunction like the thread opener.
I usually use the Windows version of Victron connect for a long time in a Windows 10 VM on my Proxmox server near the Victron and Pylontech ESS (the same like all the other software from Victron and Pylontech). Therefore I can work with all of them everywhere in my network via remote desktop session.
Nevertheless if I should need the Linux version in future I will be aware of the solution.
Thanks a lot
Dirk
Hi @Juanht,
The issue is now fixed with the version that you can download from our website: https://www.victronenergy.com/upload/software/VictronConnect-x86_64_v6.17.AppImage
Although the version is the same, the name is slightly different and the issue of not starting under Linux Min 21.3 should be resolved.
With kind regards,
Thiemo van Engelen
Hi @dick
There is probably some environment variable set that forces the program to use the gtk backend, which is not available in the AppImage. What environment variables are set that start with QT_?
With kind regards,
Thiemo van Engelen
Hi @thiemovanengelen
I have checked and it works correctly. VERY grateful.
Regards, Joan
You are right. I have the following QT_ environment variables that I was not aware of:
QT_ACCESSIBILITY=1
QT_QPA_PLATFORMTHEME=gtk2
QT_STYLE_OVERRIDE=gtk
QT_FONT_DPI=96
QT_SCALE_FACTOR=1
Some of them seem to be related to the mate desktop environment:
/home/dick $ grep -r QT_ /etc 2> /dev/null
/etc/environment.d/90qt-a11y.conf:QT_ACCESSIBILITY=1
/etc/profile.d/mate-qt.sh: export QT_QPA_PLATFORMTHEME=gtk2
/etc/profile.d/appmenu-qt5.sh:export QT_QPA_PLATFORMTHEME=appmenu-qt5
/etc/X11/Xsession.d/70im-config_launch: [ -z "$QT_IM_MODULE" ] && \
/etc/X11/Xsession.d/70im-config_launch: export QT_IM_MODULE
/etc/X11/Xsession.d/99mate-environment: export QT_STYLE_OVERRIDE=gtk
/etc/X11/Xsession.d/90qt-a11y:QT_ACCESSIBILITY=1
/etc/X11/Xsession.d/90qt-a11y:export QT_ACCESSIBILITY
/etc/X11/Xsession.d/90qt-a11y: dbus-update-activation-environment --verbose --systemd QT_ACCESSIBILITY
Starting VictronConnect-x86_64-v6.17.AppImage without the QT_ variables works. Thanks!