(v6.24) VictronConnect - Linux AppImage crashes in Linux. Checked in 2 versions: openSUSE TW and Ubuntu 25.10. However in Ubuntu it works longer: crashed on 1st start, now works ok, however not fully tested it yet.
Crush dump on openSUSE TW:
PID: 13208 (VictronConnect)
Signal: 11 (SEGV)
Timestamp: Wed 2026-01-28 08:27:40 EET (5s ago)
Command Line: /tmp/.mount_VictrogM3z0u//bin/VictronConnect
Executable: /tmp/.mount_VictrogM3z0u/bin/VictronConnect
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-VictronConnect@10f52cbb26b3463096f89b8cb4c284db.service
Unit: user@1000.service
User Unit: app-VictronConnect@10f52cbb26b3463096f89b8cb4c284db.service
Slice: user-1000.slice
Boot ID: 331d3c8caee64b1b8e6c616ed381b24e
Machine ID: be84cb828aa54e328e175d658b765064
Storage: /var/lib/systemd/coredump/core.VictronConnect.1000.331d3c8caee64b1b8e6c616ed381b24e.13208.1769581660000000.zst (present)
Size on Disk: 8.7M
Message: Process 13208 (VictronConnect) of user 1000 dumped core.
Stack trace of thread 13208:
#0 0x00007fcb777991ba n/a (/tmp/.mount_VictrogM3z0u/lib/libQt6Core.so.6 + 0x1991ba)
ELF object binary architecture: AMD x86-64
Based on the stack trace, the fault is occurring within libQt6Core.so.6. Since AppImages bundle their own libraries in /tmp/.mount_…, this is often due to a conflict between the bundled Qt libraries and your system’s graphics drivers or Wayland/X11 environment.
Yes, run successfully only once, now crashes on every start in openSUSE TW. Ubuntu version can’t connect to the device and even do not ask for a PIN which I had changed in mobile app BTW.
qt.core.qobject.connect: QObject::connect(QObject, Unknown): invalid nullptr parameter
qt.core.qobject.connect: QObject::connect(QObject, Unknown): invalid nullptr parameter
[VREGHP] static void* VeRegsHelper::init() | :/ext/shared-definitions/json/vregs.json | :/ext/shared-definitions/json/item_list.json
[VREGHP] loadVeRegDataDefinition :/ext/shared-definitions/json/vregs.json
[VREGHP] loadVeRegItemsDefinition :/ext/shared-definitions/json/item_list.json
WARN 2026-02-06T17:45:06.157 [VRGTLR] init translation function defined for vreg "VE_REG_LINK_BINARY_SWITCH_BANK_STATUS" but no translation function found!!
WARN 2026-02-06T17:45:06.157 [VRGTLR] init translation function defined for vreg "VE_REG_LINK_BINARY_SWITCH_BANK_MASK" but no translation function found!!
WARN 2026-02-06T17:45:06.165 [VRGTLR] init path "/Mgmt/ProcessName" has no vreg defined
WARN 2026-02-06T17:45:06.165 [VRGTLR] init path "/Mgmt/ProcessVersion" has no vreg defined
WARN 2026-02-06T17:45:06.166 [VRGTLR] init path "/Mgmt/Connection" has no vreg defined
WARN 2026-02-06T17:45:06.166 [VRGTLR] init path "/Connected" has no vreg defined
WARN 2026-02-06T17:45:06.166 [VRGTLR] init path "/N2KUniqueNumber" has no vreg defined
WARN 2026-02-06T17:45:06.166 [VRGTLR] init path "/Alarms/LowBattery" has no vreg defined
WARN 2026-02-06T17:45:06.167 [VRGTLR] init path "/Alarms/FuseBlown" has no vreg defined
WARN 2026-02-06T17:45:06.173 [VRGTLR] init path "/Update/StartResult" has no vreg defined
WARN 2026-02-06T17:45:06.173 [VRGTLR] init path "/PinCodeResult" has no vreg defined
WARN 2026-02-06T17:45:06.173 [VRGTLR] init path "/PukCodeResult" has no vreg defined
WARN 2026-02-06T17:45:06.585 [VRMPIN] START SYNC DATABASE TO MAP 0
WARN 2026-02-06T17:45:06.592 qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "stateChanged"
WARN 2026-02-06T17:45:06.592 qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "connectivityChanged"
WARN 2026-02-06T17:45:06.595 qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "deviceTypeChanged"
WARN 2026-02-06T17:45:06.595 qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "meteredChanged"
WARN 2026-02-06T17:45:07.133 qt.accessibility.atspi: Error in contacting registry: "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus server"
coredumpctl is not available on my Arch (Manjaro) Install. I am running my device with Manjaro including latest updates and KDE under Wayland as GUI
Extracting the AppImage and get it running from sqash-fs system is throwing the same memory error as running the image directly.
Apart from that i do not have issues with other bluetooth devices connected to my device, but looks like pretty much the same error as for @AlekseyK
Edit: This is how it look in my Bluetooth settings.
Shunt and two Solar charger are discovered as V 5.x is working. But everything above with 6.x not.
The linux appimage is completely unsupported.
Experience will unfortunately vary based on version, distribution and hardware.
Sorry, there is no easy answer but this is clear from the docs.
Like veconfigure some tools just don’t fully support all platforms.
Moving along with the thread of the topic, now that the installer ran, run the VictronConnect command from terminal.
Give us the output when it crashes.
Ive updated the script to disable all the warns, so that we can more easily see where the segfault happens
# Filter out noisy developer logs (VREG warnings, legacy serial port scanning, D-Bus errors) while keeping real errors visible.
exec "\$BASE_DIR/bin/VictronConnect" "\$@" 2> >(grep -v -E "VeRegsHelper|VRGTLR|VREGHP|invalid nullptr parameter|QTVEDS|Opening.*failed|qt.dbus.integration" >&2)
END_OF_LAUNCHER
Heres the full script again:
#!/bin/bash
# VictronConnect Installer Script (Updated with Udev rules and Wayland fix)
set -e
# VictronConnect Installer Script
# Installs extracted AppImage to /opt/victronconnect
if [ "$EUID" -ne 0 ]; then
echo "Please run as root (sudo ./install_victronconnect.sh)"
exit 1
fi
# Detect OS
if [ -f /etc/os-release ]; then
. /etc/os-release
OS=$NAME
echo "Detected system: $OS"
else
echo "Warning: Could not detect OS version, proceeding anyway..."
fi
APP_DIR="/opt/victronconnect"
SOURCE_DIR="./squashfs-root"
if [ ! -d "$SOURCE_DIR" ]; then
echo "Error: Directory $SOURCE_DIR not found. Please run this script from the folder containing the extracted AppImage."
exit 1
fi
echo "Installing VictronConnect to $APP_DIR..."
# 1. Clean previous install
rm -rf "$APP_DIR"
mkdir -p "$APP_DIR"
# 2. Copy files
echo "Copying files..."
cp -r "$SOURCE_DIR"/* "$APP_DIR/"
# Cleanup unnecessary files
rm -f "$APP_DIR/AppRun"
rm -f "$APP_DIR/VictronConnect.desktop"
rm -f "$APP_DIR/.DirIcon"
# Determine which serial group exists: dialout (Debian/Ubuntu) or uucp (Arch/Fedora)
TARGET_GROUP="dialout" # Fallback default
for g in dialout uucp; do
if getent group "$g" >/dev/null; then
TARGET_GROUP="$g"
break
fi
done
echo "Using group '$TARGET_GROUP' for serial access permissions."
# 3. Setup Udev Rules (USB Access)
echo "Setting up USB permissions (udev rules)..."
cat > /etc/udev/rules.d/50-victron-usb.rules <<END_OF_UDEV
# Victron Energy products (FTDI chips mostly)
SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", MODE="0666", GROUP="$TARGET_GROUP"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6015", MODE="0666", GROUP="$TARGET_GROUP"
END_OF_UDEV
# Reload udev to apply changes
if command -v udevadm >/dev/null; then
echo "Reloading udev rules..."
udevadm control --reload-rules && udevadm trigger
fi
# 3b. Group Membership Check
# Ensure the real user (who invoked sudo) is in the serial group
REAL_USER=${SUDO_USER:-$USER}
if [ -n "$REAL_USER" ]; then
if ! groups "$REAL_USER" | grep -q "\b$TARGET_GROUP\b"; then
echo "Adding user '$REAL_USER' to '$TARGET_GROUP' group for serial access..."
usermod -aG "$TARGET_GROUP" "$REAL_USER"
echo "Note: You will need to log out and log back in for this group change to take effect."
fi
fi
# 4. Create Launcher
echo "Creating launcher..."
cat > /usr/bin/victronconnect <<END_OF_LAUNCHER
#!/bin/sh
# Force X11 for Qt compatibility on Wayland (prevents display issues on modern GNOME/KDE)
export QT_QPA_PLATFORM=xcb
export BASE_DIR="$APP_DIR"
export LD_LIBRARY_PATH="\$BASE_DIR/lib:\$LD_LIBRARY_PATH"
export QML_IMPORT_PATH="\$BASE_DIR/qml:\$QML_IMPORT_PATH"
export QML2_IMPORT_PATH="\$BASE_DIR/qml:\$QML2_IMPORT_PATH"
export QT_PLUGIN_PATH="\$BASE_DIR/plugins:\$QT_PLUGIN_PATH"
export QTDIR="\$BASE_DIR"
export QT_QPA_PLATFORM_PLUGIN_PATH="\$BASE_DIR/plugins/platforms:\$QT_QPA_PLATFORM_PLUGIN_PATH"
# Filter out noisy developer logs (VREG warnings, legacy serial port scanning, D-Bus errors) while keeping real errors visible.
exec "\$BASE_DIR/bin/VictronConnect" "\$@" 2> >(grep -v -E "VeRegsHelper|VRGTLR|VREGHP|invalid nullptr parameter|QTVEDS|Opening.*failed|qt.dbus.integration" >&2)
END_OF_LAUNCHER
chmod 755 /usr/bin/victronconnect
# 5. Install Desktop File
echo "Installing desktop entry..."
cat > /usr/share/applications/victronconnect.desktop <<END_OF_DESKTOP
[Desktop Entry]
Type=Application
Name=VictronConnect
Exec=victronconnect
Icon=victronconnect
Comment=Monitor, configure and update firmware of all Victron products.
Terminal=false
Categories=Electronics;
END_OF_DESKTOP
# Refresh desktop database if available
if command -v update-desktop-database >/dev/null; then
update-desktop-database /usr/share/applications
fi
# 6. Install Icon
echo "Installing icon..."
mkdir -p /usr/share/icons/hicolor/128x128/apps
cp "$SOURCE_DIR/VictronConnect.png" /usr/share/icons/hicolor/128x128/apps/victronconnect.png
echo "Installation Complete!"
echo "You can now launch VictronConnect from your application menu or by typing 'victronconnect'."
echo "Note: If you have issues connecting to devices, try unplugging and replugging them."
echo "Remember to log out and log back in for the group changes to take effect if you were added to the serial group."
I know that it’s unsupported. But as many have it running successfully (even under Arch Linux) i would expect that someone in the community can enlighten the issue a bit.
qt.core.qobject.connect: QObject::connect(QObject, Unknown): invalid nullptr parameter
qt.core.qobject.connect: QObject::connect(QObject, Unknown): invalid nullptr parameter
[VREGHP] static void* VeRegsHelper::init() | :/ext/shared-definitions/json/vregs.json | :/ext/shared-definitions/json/item_list.json
[VREGHP] loadVeRegDataDefinition :/ext/shared-definitions/json/vregs.json
[VREGHP] loadVeRegItemsDefinition :/ext/shared-definitions/json/item_list.json
WARN 2026-02-08T12:57:41.708 [VRGTLR] init translation function defined for vreg "VE_REG_LINK_BINARY_SWITCH_BANK_STATUS" but no translation function found!!
WARN 2026-02-08T12:57:41.708 [VRGTLR] init translation function defined for vreg "VE_REG_LINK_BINARY_SWITCH_BANK_MASK" but no translation function found!!
WARN 2026-02-08T12:57:41.714 [VRGTLR] init path "/Mgmt/ProcessName" has no vreg defined
WARN 2026-02-08T12:57:41.714 [VRGTLR] init path "/Mgmt/ProcessVersion" has no vreg defined
WARN 2026-02-08T12:57:41.714 [VRGTLR] init path "/Mgmt/Connection" has no vreg defined
WARN 2026-02-08T12:57:41.714 [VRGTLR] init path "/Connected" has no vreg defined
WARN 2026-02-08T12:57:41.714 [VRGTLR] init path "/N2KUniqueNumber" has no vreg defined
WARN 2026-02-08T12:57:41.715 [VRGTLR] init path "/Alarms/LowBattery" has no vreg defined
WARN 2026-02-08T12:57:41.715 [VRGTLR] init path "/Alarms/FuseBlown" has no vreg defined
WARN 2026-02-08T12:57:41.720 [VRGTLR] init path "/Update/StartResult" has no vreg defined
WARN 2026-02-08T12:57:41.720 [VRGTLR] init path "/PinCodeResult" has no vreg defined
WARN 2026-02-08T12:57:41.720 [VRGTLR] init path "/PukCodeResult" has no vreg defined
WARN 2026-02-08T12:57:42.092 [VRMPIN] START SYNC DATABASE TO MAP 0
WARN 2026-02-08T12:57:42.098 qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "stateChanged"
WARN 2026-02-08T12:57:42.098 qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "connectivityChanged"
WARN 2026-02-08T12:57:42.100 qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "deviceTypeChanged"
WARN 2026-02-08T12:57:42.100 qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "meteredChanged"
WARN 2026-02-08T12:57:42.570 qt.accessibility.atspi: Error in contacting registry: "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus server"
Thanks.
As said, many have it running successfully. Tried it now again on my laptop. The first launch is ok, the devices are shown. But every next launch the memory access error appears as documented here above.
Thanks. It isn’t really a life saving topic. More a “nice-to-have” because i have my notebook running pretty often and i do not need to open my smartphone each and every time for checking.
If it’s not working at all, i am good with it as well.
All versions below 6.x are working. It starts with any 6.x version. Will try the latest beta now
