Troubleshooting

Digital Design Studio: Troubleshooting. Check the requirements and troubleshooting steps for Windows 2.1.2.3, Linux 2.1.2.3 or Cloud 2.1.2.10.

Overview

Start with the exact product, version, operating system, architecture, command and error text. Keep signature verification enabled.

First compare the machine with System Requirements and Network. Record any difference in the operating system, architecture, desktop environment, or browser.

Download Does Not Start

Public installers do not require sign-in. Use the current download page. HTTP 429 means the request limit was reached; wait for the indicated retry interval. HTTP 503 means the approved artifact or its verification material is unavailable. Report a persistent failure with the exact URL and message.

For Windows 2.1.2.3, use the signed download offered on the official page and follow Windows installation. Record the download channel, package version and exact error.

Package Will Not Install

Confirm all of the following:

  • the machine is Ubuntu 24.04 LTS on amd64/x86_64, matching the verified Linux 2.1.2.3 environment;

  • the filename and checksum match Downloads;

  • debsig-verify accepts the package with the published policy and keyring;

  • the command uses sudo apt install ./FILE.deb, including ./;

  • the package manager reports no unresolved dependency or disk-space problem.

Keep the full apt error. A generic screenshot without the failing package and dependency names is usually not enough to diagnose installation.

Application Is Missing from Search

Package installation and desktop launcher discovery are separate checks. First try the installed command:

Bash
altifigence-ide

If application search has not refreshed, sign out of the Linux desktop session and sign in again. Use dpkg -l | grep altifigence to inspect the installed package and compare it with the verified .deb.

Browser Sign-In Does Not Return to the App

During desktop browser sign-in, keep the application open while the browser returns to the local 127.0.0.1 callback. Record the exact error and the time if the callback fails.

Sign-in succeeds but a feature is unavailable

For Windows 2.1.2.3, open a My PC project to use local editing, saving and GDS viewing. Install the optional OSS simulators for the Testbench flow. Record the selected host and the exact message when another action is unavailable.

CLI Command Is Unavailable

After verified installation, use the installed executable:

Bash
alti version
alti capabilities
alti commands

The release install bootstrap installs the signed layout used by capabilities and protected local runners. For an installation or capability error, record the exact executable path, release catalog and diagnostics, then follow Install on Linux.

Use alti commands for local command discovery and alti capabilities for the installed capability catalog. Keep the exact command, diagnostics and exit status with your support request.

For an offline validation error, use the CLI First Success example with a non-sensitive source. Keep stdout, stderr and the exit status separate, together with the exact command and workspace path.

Collect a Minimal Diagnostic Report

Run read-only checks one at a time. Do not run the application as an administrator and do not collect an entire home directory or application-data directory.

Useful facts are:

  • the output of uname -s and uname -m;

  • NAME, VERSION_ID, and VERSION_CODENAME from /etc/os-release;

  • the exact package name, version, and architecture reported by dpkg-query for an installed desktop product;

  • whether command -v altifigence-ide finds the Digital Design Studio launcher;

  • the downloaded filename and locally calculated SHA-256;

  • the exact screen title or CLI error code, exit status, and approximate local time of the failure.

Before sharing a log or screenshot, review every line. Remove source text, absolute project paths when sensitive, email addresses not needed for the case, tokens, cookies, authorization codes, private download links, private keys, and third-party tool licence data. Prefer the smallest excerpt that still contains the failing action and complete error.

Contact

Send support questions to contact@altifigence.com. Include only:

  • product, version, operating system, and architecture;

  • the exact command or screen where the failure occurred;

  • the complete error text and approximate time;

  • the artifact filename and calculated SHA-256 when relevant.

Also state what you expected, what happened instead, and whether the problem is reproducible with a new non-sensitive project or the CLI offline preflight.

Remove project source, proprietary logs, access tokens, cookies, private keys, and personal data before attaching diagnostics.

Find the right recovery guide

Symptom

Check first

Guide

Windows update waits

Open DDS windows and package-in-use message

Windows install

WSL project disconnects

Distribution, Linux user and original folder identity

Windows / WSL

Cloud project does not open

Selected organization, account access and project

Runtime controls

Save reports a conflict

Latest saved revision and unsaved editor text

Local workspaces

MCP connects but tools are missing

Connection scope and the tool catalog shown for that connection

MCP errors

2.0.2 feature checks

  • For projects from Digital Design Studio 2.0.2, on Windows 2.1.2.3 use Local → Projects on this PC → Open example. The app checks first-run eligibility before opening the example automatically for a new user.

  • For Windows Testbench compilation or include errors, read Simulator log and the Verilog settings guide.

  • For a file error in the built-in GDS view of a Windows My PC project, choose a non-empty .gds or .gdsii file saved in the project, up to 4 MiB.

  • For Agent, record the displayed reason and read the Agent guide.

  • For storage or QUOTA limits, preserve work and read Cloud storage or weekly QUOTA.

  • For an update or rollback, follow Update, move and roll back and retain the exact installer/error.

Using Digital Design Studio 2.0.2

For projects from Digital Design Studio 2.0.2, use these checks with the current host: Windows 2.1.2.3, Linux 2.1.2.3 or Cloud 2.1.2.10. A fatal error or failed save can offer a private error report. Review the report, then choose Send report. Support retains the report for 30 days. Automatic data includes predefined error codes, components and stages, the desktop or Cloud surface, product/platform/version information, occurrence counts and times, project-protection state and a random report ID. If an optional comment is offered, review its full text and confirm it before sending. Do not include source text, NDA material, credentials or personal data. Highlighted lines can be removed before confirmation. Protected or unconfirmed projects use predefined automatic data. The report stores the comment confirmation time and version. Review all information before sharing it; Community posts are public.

Keep the selected host, input files, tool version, diagnostics and saved output with each result.

2.0.2 support reference

The app is still running after X

On Windows 2.1.2.3, the default Hide to tray setting lets X hide the window while work continues. Use the tray icon → Open Digital Design Studio to return, or Quit to exit after checking unsaved work. Change the setting in Settings → Desktop → When the window closes. Close the remaining DDS windows before retrying an update that reports the package is in use.