ClaudeandOmar e3215157e6 fix(linux): don't ship libsqlite3.so as a dereferenced symlink ...

The Linux bundle installed lib/libsqlite3.so as a symlink to
libsqlite3_flutter_libs_plugin.so, which holds the sqlite3 amalgamation
compiled into the plugin. The release tarball dereferences that symlink,
so the extracted tree carries two byte-identical copies of the same
shared object with the same SONAME. Loading both maps sqlite twice and
sqlite3_initialize calls through a null mutex-init pointer, segfaulting
about a second after launch before any UI paints.

Drop the alias and open the plugin under its real name instead, falling
back to the system sqlite when it isn't there.

Verified on the v6.4.4 Linux release: restoring a real symlink launches
and paints, copying the file back over it reproduces the segfault.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BkQt8DaFfxs3FThEUaMPix

2026-09-15 16:32:43 +02:00

..

sqlite_debug.dart

Reformat the whole codebase with 100 line width (#3403)

2026-07-15 01:20:33 +03:00

sqlite.dart

fix(linux): don't ship libsqlite3.so as a dereferenced symlink

2026-09-15 16:32:43 +02:00