Bus Connection Errors When Installing LabVIEW 2026 Q1 Offline Manual

Issue Details

I see "Failed to connect to the bus.." errors, similar to the ones shown below, when installing the LabVIEW 2026 Q1 offline manual on Ubuntu 22.04, and Red Hat 9.6, using the ISO (offline) installer:

Setting up ni-labview-offline-manual (26.1.0.214-0+214) ...

[5543:1223/042823.677461:ERROR:bus.cc(407)]
Failed to connect to the bus: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply,
the reply timeout expired, or the network connection was broken.

[5543:1223/042823.677881:ERROR:bus.cc(407)]
Failed to connect to the bus: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply,
the reply timeout expired, or the network connection was broken.

[5543:1223/042823.678182:ERROR:bus.cc(407)]
Failed to connect to the bus: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply,
the reply timeout expired, or the network connection was broken.

[Ubuntu Software 3.076845:ERROR:bus.cc(407)]
Failed to connect to the bus: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply,
the reply timeout expired, or the network connection was broken.

and as shown in the screenshots below:

Ubuntu 22.04:

Red Hat 9.6:

Solution

This issue occurs when installing the LabVIEW 2026 Q1 Offline Manual from the ISO on Ubuntu 22.04 or Red Hat 9.6. The installer reports repeated “Failed to connect to the bus” messages, but these do not affect installation.

Summary:

1. This behavior is a known issue specific to LabVIEW 2026 Q1 when installed from the ISO-based offline installer on Ubuntu 22.04 and Red Hat 9.6.
2. The “Failed to connect to the bus” messages are benign and can be safely ignored; the manual installs successfully despite the warnings.
3. This issue does not occur when installing on Ubuntu 24.04.