[Bug]: RENDERER_ERROR (fp: 37ae37fa)

[apradoc]

Description

Only install

Could not load your designs
Error invoking remote method 'snapshots:v1:list-designs': CodesignError: Snapshots database failed to initialize. Check Settings → Storage for diagnostics. (/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /tmp/.mount_open-cgvz1z9/resources/app.asar.unpacked/node_modules/better-sqlite3/build/Release/better

Steps to reproduce

1- download appimage
2- set permission
3- Open the UI
4- Show me a warning

Expected behavior

Normal operations in the gui

Actual behavior

Error invoking remote method 'snapshots:v1:create-design': CodesignError: Snapshots database failed to initialize. Check Settings → Storage for diagnostics. (/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /tmp/.mount_open-crAcUS4/resources/app.asar.unpacked/node_modules/better-sqlite3/build/Release/better_sqlite3.node-electron-x64.node))

open-codesign version

0.1.4

Platform

Linux

OS version

5.10.0-38-amd64

Model provider (if relevant)

None

Error code

RENDERER_ERROR

Diagnostics bundle

Bundle saved locally at ~/Descargas/open-codesign-diagnostics-2026-05-04T06-23-39.zip. Attach it to this issue after submitting.

Logs

tion 'self'; img-src 'self' data:; script-src 'self'; style-src 'unsafe-inline'",\n` +
    '  "content-type": "text/plain; charset=utf-8",\n' +
    '  "date": "Mon, 04 May 2026 06:20:56 GMT",\n' +
    '  "referrer-policy": "no-referrer-when-downgrade",\n' +
    '  "server": "github.com",\n' +
    '  "strict-transport-security": "max-age=31536000; includeSubdomains; preload",\n' +
    '  "vary": "X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, X-Requested-With, Sec-Fetch-Site,Accept-Encoding, Accept, X-Requested-With",\n' +
    '  "x-content-type-options": "nosniff",\n' +
    '  "x-frame-options": "deny",\n' +
    '  "x-github-request-id": "E6C4:25CAE5:2528FE:307276:69F83AC8",\n' +
    '  "x-xss-protection": "0"\n' +
    '}\n' +
    '    at createHttpError (file:///tmp/.mount_open-crAcUS4/resources/app.asar/out/main/index.js:40757:12)\n' +
    '    at ElectronHttpExecutor.handleResponse (file:///tmp/.mount_open-crAcUS4/resources/app.asar/out/main/index.js:40850:16)\n' +
    '    at ClientRequest.<anonymous> (file:///tmp/.mount_open-crAcUS4/resources/app.asar/out/main/index.js:40820:18)\n' +
    '    at ClientRequest.emit (node:events:519:28)\n' +
    '    at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:2:130549)\n' +
    '    at SimpleURLLoaderWrapper.emit (node:events:519:28)\n' +
    '    at newError (file:///tmp/.mount_open-crAcUS4/resources/app.asar/out/main/index.js:39896:20)\n' +
    '    at fetchData (file:///tmp/.mount_open-crAcUS4/resources/app.asar/out/main/index.js:49492:55)\n' +
    '    at async GitHubProvider.getLatestVersion (file:///tmp/.mount_open-crAcUS4/resources/app.asar/out/main/index.js:49502:19)\n' +
    '    at async AppImageUpdater.getUpdateInfoAndProvider (file:///tmp/.mount_open-crAcUS4/resources/app.asar/out/main/index.js:51181:15)\n' +
    '    at async AppImageUpdater.doCheckForUpdates (file:///tmp/.mount_open-crAcUS4/resources/app.asar/out/main/index.js:51194:22)'
}
[2026-05-04 02:20:56.842] [error]  (main:updates) startup.checkForUpdates.fail {
  message: 'Cannot find latest-linux.yml in the latest release artifacts (https://github.com/OpenCoworkAI/open-codesign/releases/download/v0.1.4/latest-linux.yml): HttpError: 404 \n' +
    '"method: GET url: https://github.com/OpenCoworkAI/open-codesign/releases/download/v0.1.4/latest-linux.yml\\n\\nPlease double check that your authentication token is correct. Due to security reasons, actual status maybe not reported, but 404.\\n"\n' +
    'Headers: {\n' +
    '  "cache-control": "no-cache",\n' +
    '  "content-length": "9",\n' +
    `  "content-security-policy": "default-src 'none'; base-uri 'self'; connect-src 'self'; form-action 'self'; img-src 'self' data:; script-src 'self'; style-src 'unsafe-inline'",\n` +
    '  "content-type": "text/plain; charset=utf-8",\n' +
    '  "date": "Mon, 04 May 2026 06:20:56 GMT",\n' +
    '  "referrer-policy": "no-referrer-when-downgrade",\n' +
    '  "server": "github.com",\n' +
    '  "strict-transport-security": "max-age=31536000; includeSubdomains; preload",\n' +
    '  "vary": "X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, X-Requested-With, Sec-Fetch-Site,Accept-Encoding, Accept, X-Requested-With",\n' +
    '  "x-content-type-options": "nosniff",\n' +
    '  "x-frame-options": "deny",\n' +
    '  "x-github-request-id": "E6C4:25CAE5:2528FE:307276:69F83AC8",\n' +
    '  "x-xss-protection": "0"\n' +
    '}\n' +
    '    at createHttpError (file:///tmp/.mount_open-crAcUS4/resources/app.asar/out/main/index.js:40757:12)\n' +
    '    at ElectronHttpExecutor.handleResponse (file:///tmp/.mount_open-crAcUS4/resources/app.asar/out/main/index.js:40850:16)\n' +
    '    at ClientRequest.<anonymous> (file:///tmp/.mount_open-crAcUS4/resources/app.asar/out/main/index.js:40820:18)\n' +
    '    at ClientRequest.emit (node:events:519:28)\n' +
    '    at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:2:130549)\n' +
    '    at SimpleURLLoaderWrapper.emit (node:events:519:28)'
}

[github-actions]

Thank you for the detailed report, Adrián. This is a known type of issue caused by a glibc version mismatch between the built native module (better-sqlite3) and your system's C library.

Root cause:
The error shows that better-sqlite3 (the SQLite engine used for the local design database) was compiled against glibc 2.33, but your system (Linux 5.10.0-38-amd64) provides an older glibc (likely 2.31, as shipped with Debian 11 Bullseye).

Immediate workaround:

• Upgrade your Linux distribution to one with glibc ≥ 2.33 (e.g., Debian 12 Bookworm, Ubuntu 22.04+, Fedora 35+).
• You can verify your glibc version with: ldd --version.

For the maintainers:

• The Linux AppImage should ideally be built in a container with an older glibc (e.g., manylinux2014 or manylinux_2_28) to maximize compatibility.
• Alternatively, provide a portable .zip or .tar.gz release so users can install their own better-sqlite3 matching their system libs.

Note on the secondary error:
The 404 for latest-linux.yml is a separate auto-update issue — the v0.1.4 release may not include that file. It does not affect the database error.

Could you please confirm:

• Output of ldd --version on your machine?
• Did you attach the diagnostics bundle? If not, you can upload it here after checking it for sensitive data.

Thanks again for the report — this is a packaging fix we should address for broader Linux support.

---

Open-CoDesign Bot

[hqhq1025]

I checked this against the release tag and current main. Confirmed root cause: the v0.1.4 Linux AppImage still ships the Electron better-sqlite3 native binding staged by apps/desktop/scripts/install-sqlite-bindings.cjs. The failure path in the report is exactly that packaged file: resources/app.asar.unpacked/node_modules/better-sqlite3/build/Release/better_sqlite3.node-electron-x64.node, and that binary requires GLIBC_2.33, so older Debian/Ubuntu systems with an older glibc fail before the snapshots DB can initialize.\n\nCurrent main has already removed this runtime dependency in c0d7e9cd fix: remove sqlite runtime storage (merged via the v0.2 promotion):\n- removed better-sqlite3, @types/better-sqlite3, and the sqlite binding postinstall script from package manifests/lockfile\n- replaced the snapshots store with a JSON design store\n- deleted apps/desktop/scripts/install-sqlite-bindings.cjs\n\nI also ran the focused regression check on current main:\n\npnpm --filter @open-codesign/desktop exec vitest run src/main/snapshots-db.test.ts scripts/after-pack-prune.test.mjs\n\nResult: 2 files passed, 4 tests passed.\n\nRecommendation: keep this issue open until the next Linux release artifact is built from current main and smoke-tested on an older glibc distro. I would not close it as fixed for v0.1.4, because the published v0.1.4 AppImage is still affected. The updater 404 in the log is separate and should be covered by the newer update-channel handling; it is not the DB initialization failure.