Node HandbookNODE HANDBOOK中文
v2rayN · Ubuntu

v2rayN on Ubuntu 22.04: e_sqlite3 and GLIBC_ABI_DT_RELR

The window never appears and the core log is empty, which places the failure in application startup, before any subscription or node is involved. Changing nodes cannot test a program that has not finished initialising.

Node Handbook editorial team ·

Separate the failure stages

EvidenceWhat it establishesNext step
No window appears; the terminal shows TypeInitializationException, SQLiteConnection and GLIBC_ABI_DT_RELR; the core log is emptyApplication initialisation failed; no core start or node request has been attemptedRecord OS, package architecture and the full first error; compare with the public issue
v2rayN opens; after starting, the core log shows address already in useThe core reached the listening stageUse the core-start path and check ports
The core log reports a missing geosite.dat or an EOFThe core cannot read its Geo dataUse the Geo-file path
The core runs but the browser cannot load pagesPast both app and core startupUse the connected-but-no-internet path

DllNotFoundException messages list several attempted paths. Reading only one “file not found” line and concluding the archive was incomplete skips the more specific error in the same stack — in the public case, a libc symbol version that the system does not provide.

The public report

v2rayN issue #10565 documents one Ubuntu 22.04 machine where the application crashed at startup. The stack breaks inside SQLitePCL.Batteries_V2.Init(), SQLiteHelper and AppManager.InitApp(), with the reporter recording the kernel log as none. The log also lists failed lookups for e_sqlite3.so and the more specific libc.so.6: version 'GLIBC_ABI_DT_RELR' not found. A maintainer closed the issue on 16 November and suggested Ubuntu 24 or newer.

An earlier issue, #9895, records almost the same SQLite and GLIBC output on Ubuntu 22.04.1 with v2rayN 7.24.4, and was answered with “no plans”. The project's installer notes still list Ubuntu 22.04+. Those two facts together do not prove that the minimum supported version has formally changed, so check your own package, your own error and the current release notes.

Preserve evidence, then recover

  1. Record the environment. Distribution and version from /etc/os-release, architecture from uname -m, v2rayN version and download source. “Latest Linux build” is not a version. Mask usernames, home paths, subscription addresses and node credentials before sharing.
  2. Start the same binary from a terminal and keep the first exception together with its inner exception. Confirm whether SQLiteConnection, libe_sqlite3.so, GLIBC_ABI_DT_RELR not found and an empty core log all appear. If the app opened and produced a core log, you are on a different page.
  3. Check package architecture against the system and whether the archive came from the official releases. Do not download replacement libraries from a file-sharing link. If the extraction was incomplete, obtain the same official archive again, verify it in a fresh directory, and keep the old directory and configuration for rollback.
  4. If the system is genuinely Ubuntu 22.04 and the error matches, evaluate a distribution upgrade. That is the maintainer's suggested path. A system upgrade affects other software: back up data, check hardware and dependency compatibility, follow the distribution's own procedure, and keep a rollback. On a managed device, hand it to the administrator.
  5. Verify in three steps after any change: the application opens, the core starts with a readable log, and one real HTTPS request through the proxy succeeds. An app that opens does not mean a node works.

About replacing the library

A reporter in that thread proposed substituting an older libe_sqlite3.so as a temporary measure. It is not a maintainer fix. Mixing library versions can introduce new compatibility and update problems, and this site has not reproduced or verified the approach, so it is not a recommended step.

Scope and limits

This page covers only the pre-start SQLite native library failure on Ubuntu 22.04 that matches the report. There is no device testing showing that every Ubuntu 22.04 installation fails, and no evidence attributing it to a provider, a subscription or the network. If the log shows only “failed to run core” while the app opens, use the core-start path; if failure comes after configuration loads, triage from the first core error. A distribution upgrade carries backup, downtime and rollback costs that belong in the decision.

What to record

  • Distribution, version, kernel and architecture.
  • v2rayN version, package name and download source.
  • The complete first exception, including the inner exception and every library path listed.
  • Whether any core log was produced.
  • Whether the same archive runs on another machine or distribution version.
  • Any library substitution you attempted, recorded as an experiment rather than a fix.