Logic2 (2.4.49) stopped working on Ubuntu 24.04

Hello,

I am trying to setup Logic2 (2.4.49) on Ubuntu 24.04, but it stops automatically after the collected data exceeds 40M around even I set the data buffer as more than 1G. I tried it on Windows, it’s working fine.

Do you have any suggestion to configure it?

Thanks

@xiaofeng.lei.bj Sorry for the trouble with that! I have some follow up questions for you below to try and get to the bottom of this.

  1. Which Saleae Logic model is showing the issue out of the ones pictured below?
    How to Identify Each Saleae Device | Saleae Support
  2. Can you double check the software version you are using again? The latest version of our software is v2.4.29.
  3. What mode of capture are you using? Timer Mode, Trigger Mode, or Looping Mode?
  4. Can you describe the behavior of the software when you reach the limit?
  5. Can you share your Machine ID with us?
    Getting your Machine ID | Saleae Support
  1. I believe it’s Logic Pro 16.
  2. The SW version is 2.4.29
  3. Trigger Mode and Timer mode both have such issue, while the looping mode is working fine.
  4. I just started the capture, and the bottom-right corner shows the label “40.0MB” with a small progress bar, then it stopped capture automatically in couple seconds.
  5. Machine ID: MachineID: 67b2b763-10ca-4d57-b252-235633b23d1b

@xiaofeng.lei.bj Strange! 40 MB is quite small.

The Trigger and Timer modes are designed to automatically stop the capture when certain conditions are met.

  • Trigger Mode will stop the capture when the trigger condition is met. When using Trigger Mode, can you confirm your trigger settings, and if the trigger conditions are perhaps being met when your capture automatically ends?
  • Timer Mode will stop the capture after the configured time has passed. When using Timer Mode, can you confirm your settings for that, and if your configured length of capture is being met when your capture automatically ends?
  • When your capture automatically ends via both modes above, can you send us the resulting capture file (.sal file format) for both cases?

For quick reference, both modes of capture are explained in more detail in the support article below.

Hi tim,

You’re definitely giving the reason! I double checked the settings of both modes, the duration times in both mode are set as 1s by default. After updating it to longer, it’s working fine!

Sorry for missing this, I didn’t use trigger mode before, but it’s a great feature!

@xiaofeng.lei.bj Thanks for the update, and I’m glad to hear that solved it!