LabVIEW 2023 Q1 Bug Fixes

Overview

The following items are notable issues fixed between the release of LabVIEW 2022 Q3 and LabVIEW 2023 Q1, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of LabVIEW.

Bug Number

Legacy ID

Description

Details

2051887

LabVIEW Offline Help Is Unavailable on Windows Server 2016

Workaround:

Use the online help from ni.com.

Reported Version:

LabVIEW 2022 Q3 | Software Platform Bundle 2022 Q3

Resolved Version:

LabVIEW 2023 Q1

Added:

Jul 27, 2022

2104674

Unable to Install LabVIEW 2022 Q3 on Ubuntu 22.04

A default installation of Ubuntu 22.04 (Jammy Jellyfish) fails to install LabVIEW 2022 Q3 due to missing dependencies such as libncurses5, libldap-2.4-2, and libopenal1.

Beginning with version 22.04, these packages are no longer shipped in the Ubuntu distribution. They were included in previous versions of Ubuntu.

Workaround:

From NI Linux Device Drivers 2022 Q4 or later, install ni-hwcfg-utility. It will provide LabVIEW with updated versions of components that do not rely on the missing legacy components.

Reported Version:

LabVIEW 2022 Q3

Resolved Version:

LabVIEW 2023 Q1

Added:

Oct 24, 2022

317596

Cannot Scroll Array Indicator with Mouse Wheel in Running VI

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2017

Resolved Version:

LabVIEW 2023 Q1

Added:

N/A

1146643

LabVIEW Crashes When Playing Sound File Repeatedly without Calling Sound Output Clear

Playing sound files repeatedly without calling "Sound Output Clear" crashes LabVIEW.

Workaround:

Call "Sound Output Clear" after playing a sound file.

Reported Version:

LabVIEW 2020

Resolved Version:

LabVIEW 2023 Q1

Added:

N/A

1863309

Python Nodes May Incorrectly Execute Serially

Using multiple Python Nodes without dataflow dependencies causes LabVIEW to serialize their execution, causing the VI to run longer than it should.

Workaround:

Place Python Nodes inside single iteration loops.

Reported Version:

LabVIEW 2021

Resolved Version:

LabVIEW 2023 Q1

Added:

N/A

1993972

LabVIEW Incorrectly Reads WAV Data Saved in DBL Format

Workaround:

Convert DBL values to I16.

Reported Version:

LabVIEW 2021

Resolved Version:

LabVIEW 2023 Q1

Added:

N/A

2100578

Find Parallelizable Loops Does Not Open When Invoked from Tools Menu of a VI

Tools > Profile > Find Parallelizable Loops does not work when invoked from the menu of a VI.

Workaround:

Invoke the menu item from the Project Explorer window's menu.

Reported Version:

LabVIEW 2021 SP1 | LabVIEW 2022 Q3

Resolved Version:

LabVIEW 2023 Q1

Added:

N/A

2226492

LabVIEW Crashes When Changing the Tabbing Order of Front Panel Controls

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2022 Q3

Resolved Version:

LabVIEW 2023 Q1

Added:

N/A

2254316

LabVIEW Python Node Returns Error 1672 When Trying to Return an Array with NumPy Library Version 1.24

With the 1.24 release of NumPy, Python Nodes that return arrays are failing with the error code 1672.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW 2023 Q1

Resolved Version:

LabVIEW 2023 Q1

Added:

N/A

Additional Patch Information

Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.

These patches currently do not have any special instructions.

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).