Skip to main content
MGieb.1
Associate
August 17, 2022
Solved

STM32CubeMonitor v1.4.0 not acquiring on Ubuntu 20.04

  • August 17, 2022
  • 5 replies
  • 2488 views

I was using STM32CubeMonitor v1.30 on Ubuntu 20.04 without any problems.

After upgrading to v1.4.0 my previously working flows no longer capture any data.

My ST-Link V3 probe shows green on the "acq in" and "aqc out" nodes..

When I click on Start Acquisition, my variable names show in the charts and gauges, but no data.

I downgraded back to v1.3.0 and the Exact same flow works in v1.3.0.

If I launch v1.4.0 from the command line, I see some warnings and an error.

Is this a hint as to why acquiring data doesn't work?

BEGIN ---- CLI log -----

$ stm32cubemonitor 

(stm32cubemonitor:788869): dbind-WARNING **: 09:29:27.658: Couldn't register with accessibility 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.

[788902:0817/092927.832573:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.

17 Aug 09:29:27 - [info] 

[redacted to make ST forum bot happy]

END ---- CLI log -----

This topic has been closed for replies.
Best answer by Richard.Chvr

Hi,

Root cause of the issue have been found, will be corrected in next official release 1.5.0.

5 replies

Richard.Chvr
Technical Moderator
August 26, 2022

Hello @MGieb.1​ 

Could not reproduce your issue on my Ubuntu 20.04, I get the same sandbox_linux.cc error but no dbind-WARNING. May be this post : https://unix.stackexchange.com/questions/532585/getting-dbind-warnings-about-registering-with-the-accessibility-bus may help?

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
Richard.Chvr
Technical Moderator
August 26, 2022

If possible, can you share your flow in private , in order I try it on my machine.

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
MGieb.1
MGieb.1Author
Associate
August 29, 2022
Hello Richard,
Thanks for reaching out.
Yes, I can share the flow with you.
Not sure if replying to this email thread is private or will it end up in the forum?
MGieb.1
MGieb.1Author
Associate
August 29, 2022

LOL

MGieb.1
MGieb.1Author
Associate
August 30, 2022

Hello @Richard.Chvr

I tried the suggestion for the dbind-WARNING of setting:

export NO_AT_BRIDGE=1 

The warning went away in v1.4.0 but it did not fix the problem of no data acquiring.

Richard.Chvr
Richard.ChvrBest answer
Technical Moderator
September 22, 2022

Hi,

Root cause of the issue have been found, will be corrected in next official release 1.5.0.

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
MGieb.1
MGieb.1Author
Associate
September 22, 2022

Sounds great! I'll definitely try it out when it's available.