Report

[cross-post]
I'm starting to use LabVIEW 2020 Sp1 on OpenSuse 15 and the event structure editor - I mean the dialog to add / edit handled event - seems to have localization issues.
Also, a difference from Windows LV, if a constant is connected to the timeout terminal, LV requires that you handle the timeout event... weird.
Is it normal / known to have these "issues"?

I have installed Labview 2020 on Dedian Buster using the rpm to deb conversion method via alien. Due to Architecture mismatch i deleted the *i386.rpm files before conversion.
My Problem is that after creating a project at "Build Specification"-> "rigth click" i am only able to select "Source Distribution". Application does not show up as an option. 
I will be grateful for any suggestions.
Thank you in advance.

I wanted to cross post metux's discovery here asap, and have a separate discussion.
Metux's original post:
The recent Linux driver package introduces a CRITICAL security vulnerability:
 
http://www.ni.com/download/ni-linux-device-drivers-2018/7664/en/
 
It adds additional yum/zypper repos, but explicitly disabling package signing and using unencrypted HTTP transport. That way, it's pretty trivial to completely takeover the affected systems, by injecting malicious packages.
 
 
DO NOT INSTALL THIS BROKEN SOFTWARE - IT IS DANGEROUS !
 
CERT and BSI are already notified.
 
 
 
 
 

More out of curiosity than of hope: has anybody any idea why SVs are almost unsupported on linux? By almost I mean that controls and indicators cannot be bound to shared variables, and that shared variables cannot be programmatically created and looked up. I know that SVs hosted on windows can be accessed in linux LV using datasocket nodes, but that is all it gets. And it has been said that datasocket is despicable. What are the missing pieces that make SV windows-only?
I didn't find much in the canonical places, so I posted a dumb zero-kudos attracting idea.

Hi everybody,
Currently working on VeriStand custom devices, I'm facing a 'huge' problem when debugging the code I make for the Linux RT Target. The console is not availbale on such targets, and I do not want to fall back to the serial port and Hyperterminal-like programs (damn we are in the 21st century !! )...
Several years ago (2014 if I remember well) I posted an request on the Idea Exchange forum on NI's website to get back the console on Linux targets. NI agreed with the idea and it is 'in development' since then. Seems to be so hard to do that it takes years to have this simple feature back to life.
On my side I developped a web-based console : HTML page displaying strings received through a WebSocket link. Pretty easy and fast, but the integration effort (start server, close server, handle push requests, ...)must be done for each single code I create for such targets.
Do you have any good tricks to debug your code running on a Linux target ?