08-14-2023 10:16 AM - edited 08-15-2023 01:21 AM
for me this is a bug, the VI from vi.lib '/usr/local/natinst/LabVIEW-2020-64/vi.lib/Platform/browser.llb/Open URL in Default Browser (string).vi'
Wait untill completion being true, this VI will complete it's operation only after the browser is closed
to fix the bug, simply change the constant to true false.
I'm using LabVIEW 2020 SP1 for Linux, maybe it's been fixed in more recent version, can anyone check please?
fun fact : the sub-VI is password protected on Windows but not on Linux
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
Solved! Go to Solution.
08-15-2023 04:31 PM - edited 08-15-2023 04:32 PM
This bug is fixed in LabVIEW 2023 Q1, but the fix is not what you described.
The xdg-open program is supposed to launch an app to handle the given argument (in this case, a browser) asynchronously, and then return immediately. LabVIEW should properly wait on the process to finish to avoid zombie subprocesses hanging around.
The issue is that xdg-open isn't disassociating and running in the background because it's sharing the stdio file descriptors with the parent LabVIEW process. Adding explicit redirects (">/dev/null 2>&1") to the command will allow xdg-open to return immediately without waiting on the browser to complete.
To fix the bug in earlier releases, instead of changing the Boolean to False, change the string passed to System Exec as follows:
08-16-2023 02:13 AM
Thank you for your reply, I'll do that.
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus