# About the Logic 1.x  (Legacy) Software category

**URL:** <https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33>\
**Category:** Logic 1.x  (Legacy) Software\
**Created:** [April 29, 2019, 9:45pm UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33 "2019-04-29T21:45:08Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![saleae-admin](https://avatars.discourse-cdn.com/v4/letter/s/e274bd/32.png) [@saleae-admin](https://discuss.saleae.com/u/saleae-admin)\
**Post date:** [April 29, 2019, 9:45pm UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/1 "2019-04-29T21:45:08Z")

</div>

This is the place to discuss the 1.x Software, in general. You can also contribute ideas and vote here: [https://ideas.saleae.com](https://ideas.saleae.com)

---

<div class="post-metadata">

**Author:** ![harin.nair](https://avatars.discourse-cdn.com/v4/letter/h/d07c76/32.png) [@harin.nair](https://discuss.saleae.com/u/harin.nair)\
**Post date:** [June 28, 2022, 10:28am UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/2 "2022-06-28T10:28:30Z")

</div>

segmentation fault on launching Saleae with 1.2.xx(tried 18 and 29)  
Platform details:  
Linux : Debian 11.3.0, Debian 11.2.0  
Dell :5090 mini pc.

Attached the crash dump  
[Errors.zip](https://discuss.saleae.com/uploads/short-url/7SVcN76PFTQFqu6yrZbMhXmVoj7.zip) (4.7 KB)

---

<div class="post-metadata">

**Author:** ![markgarrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/markgarrison/32/23_2.png) [@markgarrison](https://discuss.saleae.com/u/markgarrison)\
**Post date:** [June 28, 2022, 6:03pm UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/3 "2022-06-28T18:03:00Z")

</div>

Sorry for the trouble! You will need the latest 1.x release, 1.2.40, which you can get here:

> **[Logic 1.x Download](https://support.saleae.com/logic-software/legacy-software/older-software-releases)**

The error causing the crash is this one:  
Error: Invalid board revision found

For context, in the last year, due to the supply chain shortages, we needed to switch ADCs in the product. This required a board redesign, and modifications to the FPGA image and software.

This means these devices only work with more recent software releases.

Since we still have customers using the 1.x software to use the automation API, we created a release of the old 1.x software with support for these devices, which is 1.2.40.

Unfortunately, we’ll have to do this again soon, as for the same reason we have to switch FPGAs from Xilinx to Lattice.

Needless to say, we’ve been pretty busy trying to keep up with supply chain issues, which has really cut into our ability to work on improvements to the software, unfortunately.

---

<div class="post-metadata">

**Author:** ![harin.nair](https://avatars.discourse-cdn.com/v4/letter/h/d07c76/32.png) [@harin.nair](https://discuss.saleae.com/u/harin.nair)\
**Post date:** [June 29, 2022, 7:04am UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/4 "2022-06-29T07:04:59Z")

</div>

Thanks for the quick support. Appreciate it.

---

<div class="post-metadata">

**Author:** ![markgarrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/markgarrison/32/23_2.png) [@markgarrison](https://discuss.saleae.com/u/markgarrison)\
**Post date:** [June 29, 2022, 5:00pm UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/5 "2022-06-29T17:00:23Z")

</div>

Sure thing!

---

<div class="post-metadata">

**Author:** ![harin.nair](https://avatars.discourse-cdn.com/v4/letter/h/d07c76/32.png) [@harin.nair](https://discuss.saleae.com/u/harin.nair)\
**Post date:** [July 4, 2022, 9:11am UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/6 "2022-07-04T09:11:46Z")

</div>

on the same note. Can i get the .zip link for 1.2.40?

---

<div class="post-metadata">

**Author:** ![harin.nair](https://avatars.discourse-cdn.com/v4/letter/h/d07c76/32.png) [@harin.nair](https://discuss.saleae.com/u/harin.nair)\
**Post date:** [July 4, 2022, 9:15am UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/7 "2022-07-04T09:15:57Z")

</div>

we have a predefined settings.xml which we copy under /usr/bin/Logic/Settings. With .AppImage our automation is failing.

---

<div class="post-metadata">

**Author:** ![markgarrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/markgarrison/32/23_2.png) [@markgarrison](https://discuss.saleae.com/u/markgarrison)\
**Post date:** [July 5, 2022, 6:37pm UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/8 "2022-07-05T18:37:39Z")

</div>

> [@harin.nair](#):
>
> on the same note. Can i get the .zip link for 1.2.40?

I assume you mean a non-Appimage Linux zip release?

You can extract the appimage with `./Logic-1.2.40-Linux.AppImage --appimage-extract`, which will dump the contents to a new directory called squashfs. You can then run the Logic binary directly from there.  
If you have any trouble with it, please send me the details and I can switch over to Linux and help from there.

---

<div class="post-metadata">

**Author:** ![harin.nair](https://avatars.discourse-cdn.com/v4/letter/h/d07c76/32.png) [@harin.nair](https://discuss.saleae.com/u/harin.nair)\
**Post date:** [July 7, 2022, 11:13am UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/9 "2022-07-07T11:13:30Z")

</div>

where can I find the Settings.xml to preload the settings before the measurements?

---

<div class="post-metadata">

**Author:** ![markgarrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/markgarrison/32/23_2.png) [@markgarrison](https://discuss.saleae.com/u/markgarrison)\
**Post date:** [July 7, 2022, 5:22pm UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/10 "2022-07-07T17:22:42Z")

</div>

I’m on windows at the moment, but I believe on Linux it’s “~/.config/Logic”. Let me know if you can’t find it there.

---

<div class="post-metadata">

**Author:** ![harin.nair](https://avatars.discourse-cdn.com/v4/letter/h/d07c76/32.png) [@harin.nair](https://discuss.saleae.com/u/harin.nair)\
**Post date:** [July 8, 2022, 5:40am UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/11 "2022-07-08T05:40:52Z")

</div>

on 1.2.29 or older releases with zip package it is under Logic\ 1.2.29\ (64-bit)/Settings/Settings.xml  
After extracting the AppImage I do not see the Settings folder anywhere. If you could let me know how the settings are stored in case of AppImage.

---

<div class="post-metadata">

**Author:** ![markgarrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/markgarrison/32/23_2.png) [@markgarrison](https://discuss.saleae.com/u/markgarrison)\
**Post date:** [July 8, 2022, 5:54am UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/12 "2022-07-08T05:54:20Z")

</div>

Sure thing. Because the AppImage mounts a small, read-only file system, we could no longer store any files inside of the app file structure. This includes settings, calibration files, and error reports.

Instead, We updated the software to create these files and folders at the location ~/.config/Logic on first run.

More specifically, we’re using QT to get two different user directories:  
QStandardPaths::AppDataLocation and QStandardPaths::AppConfigLocation  
You can find the definitions for these in the QT documentation here:  
[https://doc.qt.io/qt-6/qstandardpaths.html](https://doc.qt.io/qt-6/qstandardpaths.html)  
We store the settings.xml file at the location returned from AppConfigLocation, and we store calibration, errors, and protocol database files at the location returned from AppDataLocation.  
Our app creates these files and folders at launch if they don’t exist. If you provide the settings.xml file at the expected location ahead of time, it should be loaded, rather than being created from defaults.

---

<div class="post-metadata">

**Author:** ![harin.nair](https://avatars.discourse-cdn.com/v4/letter/h/d07c76/32.png) [@harin.nair](https://discuss.saleae.com/u/harin.nair)\
**Post date:** [July 8, 2022, 6:16am UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/13 "2022-07-08T06:16:28Z")

</div>

Is there any API changes in 1.2.40 compared to 1.2.29?

---

<div class="post-metadata">

**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\
**Post date:** [July 8, 2022, 6:33pm UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/14 "2022-07-08T18:33:07Z")

</div>

@harin.nair I assume you’re talking about our Logic 1.x Automation API?

> **[Socket API - Automation](https://support.saleae.com/saleae-api-and-sdk/socket-api)**

If so, there are no changes to the API from 1.2.29 to 1.2.40.

---

<div class="post-metadata">

**Author:** ![harin.nair](https://avatars.discourse-cdn.com/v4/letter/h/d07c76/32.png) [@harin.nair](https://discuss.saleae.com/u/harin.nair)\
**Post date:** [July 13, 2022, 10:24am UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/15 "2022-07-13T10:24:09Z")

</div>

Thanks.

I am getting this error while running from docker. But if i just run it outside the docker no issues.

jenkins@vayu:/usr/bin/Logic$ ./logic  
QStandardPaths: XDG\_RUNTIME\_DIR not set, defaulting to ‘/tmp/runtime-jenkins’  
QCommandLineParser: option not defined: “websource”  
QCommandLineParser: option not defined: “port”  
Root Path: /tmp/.mount\_logiczycqmJ/usr/bin [/home/build/Software/Logic/Source/LogicBase/src/Environment.cpp; Environment; 184]  
Release Mode; analyzer path is /tmp/.mount\_logiczycqmJ/usr/bin/Analyzers [/home/build/Software/Logic/Source/LogicBase/src/Environment.cpp; Environment; 198]  
Logic Assert Information  
Version: 1.2.40  
System: Linux; 5.10.0-13-amd64; #1 SMP Debian 5.10.106-1 (2022-03-17); x86\_64  
Crash Id:  
File: /home/build/Software/Logic/Source/LogicBase/src/Environment.cpp  
Function: Environment, Line: 249  
Error: failed to create data directory  
Most recent messages:

Root Path: /tmp/.mount\_logiczycqmJ/usr/bin [/home/build/Software/Logic/Source/LogicBase/src/Environment.cpp; Environment; 184]

Release Mode; analyzer path is /tmp/.mount\_logiczycqmJ/usr/bin/Analyzers [/home/build/Software/Logic/Source/LogicBase/src/Environment.cpp; Environment; 198]

Segmentation fault (core dumped)

---

<div class="post-metadata">

**Author:** ![markgarrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/markgarrison/32/23_2.png) [@markgarrison](https://discuss.saleae.com/u/markgarrison)\
**Post date:** [July 19, 2022, 9:47pm UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/16 "2022-07-19T21:47:02Z")

</div>

The crash here is from this line:

> Error: failed to create data directory

The software is crashing because it failed to create the app data directory.  
Unfortunately, it won’t print out the path it tried to create.  
It’s probably trying to create one of the following directories, but you might be able to use strace to check.  
“~/.local/share/Logic”, “/usr/local/share/Logic”, “/usr/share/Logic”  
Is this something you could fix with docker?

---

<div class="post-metadata">

**Author:** ![kavya.s](https://avatars.discourse-cdn.com/v4/letter/k/76d3ee/32.png) [@kavya.s](https://discuss.saleae.com/u/kavya.s)\
**Post date:** [June 18, 2024, 10:06am UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/17 "2024-06-18T10:06:29Z")

</div>

Segmentation fault on launching Saleae with 1.2.40  
Platform details:  
Linux : Debian 11  
Saleae Hardware Revision: 1.0.0, model: Logic pro 16

No error message is thrown at the console. Tried deleting settings.xml file ,able to launch saleae but after sometime the error appears randomly .

**Sudo dmesg -T** :  
[Tue Jun 18 11:17:00 2024] Lockdown: systemd-logind: hibernation is restricted; see man kernel\_lockdown.7  
[Tue Jun 18 11:17:00 2024] Lockdown: systemd-logind: hibernation is restricted; see man kernel\_lockdown.7  
[Tue Jun 18 11:29:03 2024] Main[1076205]: segfault at 0 ip 00007f3128271ebb sp 00007ffdc4f013d0 error 6 in libanalyzer.so[7f312824b000+71000]  
[Tue Jun 18 11:29:03 2024] Code: 85 c0 0f 84 47 01 00 00 4c 89 ee 48 89 ef e8 ec c9 fd ff 48 89 ef e8 74 da fd ff 48 8b 7c 24 70 4c 39 f7 74 05 e8 85 ce fd ff 04 25 00 00 00 00 00 00 00 00 0f 0b 0f 1f 84 00 00 00 00 00 b9

**Terminal errror**  
jenkins@krishna:/usr/bin/Logic$ ./logic  
QStandardPaths: XDG\_RUNTIME\_DIR not set, defaulting to ‘/tmp/runtime-jenkins’  
QCommandLineParser: option not defined: “websource”  
QCommandLineParser: option not defined: “port”  
Root Path: /usr/bin/Logic/usr/bin [/home/build/Software/Logic/Source/LogicBase/src/Environment.cpp; Environment; 184]  
Release Mode; analyzer path is /usr/bin/Logic/usr/bin/Analyzers [/home/build/Software/Logic/Source/LogicBase/src/Environment.cpp; Environment; 198]  
Settings path is /home/jenkins/.config/Logic [/home/build/Software/Logic/Source/LogicBase/src/Environment.cpp; Environment; 456]  
Errors path is /home/jenkins/.local/share/Logic/Errors [/home/build/Software/Logic/Source/LogicBase/src/Environment.cpp; Environment; 457]  
Analyzers path is /usr/bin/Logic/usr/bin/Analyzers [/home/build/Software/Logic/Source/LogicBase/src/Environment.cpp; Environment; 458]  
Databases path is /home/jenkins/.local/share/Logic/Databases [/home/build/Software/Logic/Source/LogicBase/src/Environment.cpp; Environment; 459]  
Calibration path is /home/jenkins/.local/share/Logic/Calibration [/home/build/Software/Logic/Source/LogicBase/src/Environment.cpp; Environment; 460]  
libpng warning: iCCP: known incorrect sRGB profile  
libpng warning: iCCP: known incorrect sRGB profile  
libpng warning: iCCP: known incorrect sRGB profile  
libpng warning: iCCP: known incorrect sRGB profile  
libpng warning: iCCP: known incorrect sRGB profile  
Build date used by AutoSunset: Mar 10 2022 [/home/build/Software/Logic/Source/Logic/src/AutoSunset.cpp; AutoSunset; 13]  
libpng warning: iCCP: known incorrect sRGB profile  
Hardware Information took 0 milliseconds to generate [/home/build/Software/Logic/Source/Logic/src/HardwareInformation.cpp; HardwareInformation; 272]  
Hardware Information took 0 milliseconds to generate [/home/build/Software/Logic/Source/Logic/src/HardwareInformation.cpp; HardwareInformation; 272]  
Segmentation fault (core dumped)

---

<div class="post-metadata">

**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\
**Post date:** [June 18, 2024, 6:19pm UTC](https://discuss.saleae.com/t/about-the-logic-1-x-legacy-software-category/33/18 "2024-06-18T18:19:28Z")

</div>

@kavya.s Sorry to hear about that issue. I wanted to let you know that we unfortunately no longer provide official support for our older Logic 1.x software, and legacy Socket API automation utility for Logic 1.x.

We highly recommend updating to our newer [Logic 2 software](https://www.saleae.com/pages/downloads) and porting your automation script to use our [Automation API](https://www.saleae.com/pages/automation) supported in Logic 2.

We would love to help with the transition as well. I saw that you wrote an email to our support team directly about this, and I’ll be happy to continue chatting about this there!
