Saleae Support
HomeDownloadUser ForumContact Us
Search…
Saleae Support
Orders & Shipping
Getting Started
Software
User Guide
Extensions
Automation & SDK
Protocol Analyzers
Datasheets & Specifications
Troubleshooting
The Software Will Not Install or Run Properly
The Logic Software Fails to Launch on Windows
The Logic Software Crashes
Getting the Console Output
The Device Is Not Connecting
Troubleshooting the Software Connection to the Device
Error Message: ReadTimeout
The Captured Data Looks Incorrect
The Captured Data is Corrupted
A Protocol Analyzer Produces Unexpected Results
The 'Waiting for Trigger' Window Never Closes
Device USB VID and PID Information
Error Message: Out of Memory Exception Was Thrown
PC Performance Issues with Logic
Data Export Is Not Working
Error Message: A Logic Device Was Found, but There Was a Problem Connecting to It
Trouble Downloading the Latest Software
Logic Does Not Connect over USB 3.0
Why Am I Seeing Spikes in the Digital Capture?
Logic Interferes with My Circuit Operation
The Add Analyzer Menu Is Not Displaying
Other Drivers Interfere with Logic's Operation
The Maximum Sample Rate is Not Selectable
The Digital and Analog Recording on the Same Channel Appear Different
Advanced USB Debugging for USB 3.0 Users with Linux Kernels 3.3 and Older
Driver Install Fails on Windows XP
Saving or Loading Anything Crashes the Software
Error Message: The application was unable to start correctly (0xc0000005)
Memory Usage with Triggered Captures
The Cabinet File disk1.cab has an Invalid Digital Signature
Software Crashes with Virtual Desktops
Pre-Trigger Buffer is Incomplete
Linux Shared Memory Crash
The Software Fails to Launch on Fedora
Missing Files: api-ms-win-crt-runtime-l1-1-0.dll or msvcp140.dll
The Decoded Protocols Window Shows Incorrect Results
Known Issues on OS X
A Measurement Appears Incorrect
All Known Issues
USB 3.0 Cable Customer Notice
Warning Message: Logic Pro is running as a USB 2.0 device
Software Issues with Encryption Products
Linux Permission Requirements for Logic Software
My Rise Time and Fall Time Measurements Seem Incorrect
The Analog Waveform Loads Very Slowly after Capture Is Complete
Input Channels are Missing
Exported MATLAB File Does Not Open
Saleae Logic LED Blinks Red
Crashes Caused by macOS Mojave (10.14)
Troubleshooting Signal Crosstalk
Error Message: DeviceSetupFailure
Error Message: Unable to detect WebGL
Sharing your Machine ID
Warning Message: Unsupported Version
Error Function: Device2::SetupDevice
Warning Message: Possible USB Host Controller Problem Detected
Error Message: StartCommandError
Logic 2 Error Messages
PC Detection Test
Apple M1 Support
Logic 2 Fails to Launch
CentOS Compatibility Issues
Failed to Load Custom Analyzer: libmidi_analyzer.so
Error Message: Failed to Load Extension
CSV Export is Slow
Set an Analyzer Starting Point in your Capture
Logic 2 is Consuming Disk Space
Connection Conflicts with USB Debuggers
PC Restart Causes Logic to Disconnect
HLA Fails to Display Special Characters
FAQ
Returns & Warranty
Ideas & Feedback
Tutorials
Oscilloscope Tutorial
Logic Analyzer Tutorial
Learning Portal
Example Projects
Powered By GitBook
Linux Permission Requirements for Logic Software

Running Logic 2

The Logic 2 software is provided in an AppImage format, which contains all the files needed for the software to run.
For information on how to run this file properly, please see the support article below and navigate to the Linux section.

Running Logic 1.2.18 and Prior Versions

The information below only applies to versions 1.2.18 and prior. We highly suggest updating your software to Logic 2 to avoid the Linux permission issues described below. A udev rules file (or equivalent) is still required to access Saleae devices.
The Logic 1.2.18 (and prior) software on Linux requires write permissions to several directories in order to run. These directories are relative to the Logic binary and need to exist for the software to run. They are not automatically generated by the software.
These directories are:
    Directory containing the Logic binary
    .\Databases
    .\Errors
    .\Settings
    .\Calibration (this directory is generated by the software and may not be present before the software is run for the first time)
The software also requires read access to all files and folders that are in the same directory as the binary, including:
    .\Analyzers
    .\libAnalyzer.so
The Drivers folder is not used by the software and not required. It contains a udev rules file and an installer script.
Previous
Software Issues with Encryption Products
Next
My Rise Time and Fall Time Measurements Seem Incorrect
Last modified 8mo ago
Copy link
Contents
Running Logic 2
Running Logic 1.2.18 and Prior Versions