Lem-x86_64.AppImage Nightly Build not self-contained

Aperta
  • Qualcosa non va?
#1,982 4 commenti 2 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
linux
Ambito
build-system, desktop

Direzione di ricerca

Start by inspecting the nightly AppImage build and packaging configuration, then trace how its WebKit and GTK dependencies are collected and launched. Reproduce the reported failures on a Linux system using the nightly build and compare the bundled libraries with the host dependencies. Done means the AppImage launches without requiring missing WebKit paths or incompatible host GTK modules.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

help wanted
PROBLEM DESCRIPTION

Latest Nightly AppImage build as of 2025-10-30 from https://github.com/lem-project/lem/releases/tag/nightly-latest does not work (on my openSUSE Tumbleweed). It seems the AppImage is not self-contained and still needs external local resources:

1) WebKit* libraries (with full paths) expected (see section CODE 1)

  • /usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/WebKitNetworkProcess
  • /usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/WebKitWebProcess

2) canberra-gtk-module library symbols not found.

Once above is solved (perhaps via symlinks to kludge), AppImage still gets errors with undefined symbols in canberra-gtk-module, again apparently expecting local OS support. Even when these files exist and may be found on host system, certain symbols cannot be found. (See section CODE 2)

Environment information

Lem-x86_64.AppImage // Nightly Build - 20251030-0145
On: openSUSE Tumbleweed v. 20251024
Kernel: Linux 6.17.4-1-default
Terminal: kitty (or any) with bash

CODE 1
$ ./Lem-x86_64.AppImage 
 ==> Performing warm boot.
   -> Build time was: 2025-10-30 01:44:49 UTC
   -> Source checksum: 8EFED5B991844F8C7CE3EB6351ED4014E2DFCE6EEADAE0789C98F68F
   -> Runtime directory is /tmp/.mount_Lem-x8IiPhDL/usr/libexec/
   -> Resource directory is /tmp/.mount_Lem-x8IiPhDL/usr/libexec/
 ==> Running boot hooks.
   -> Running BOOT/DEPLOY:FOREIGN-LIBRARIES
 ==> Reloading foreign libraries.
   -> Loading foreign library #<LIBRARY CL-CHARMS/LOW-LEVEL::LIBCURSES>.
   -> Loading foreign library #<LIBRARY LEM-TERMINAL/FFI::TERMINAL>.
   -> Loading foreign library #<LIBRARY ASYNC-PROCESS::ASYNC-PROCESS>.
   -> Loading foreign library #<LIBRARY CL+SSL/CONFIG::LIBSSL>.
   -> Loading foreign library #<LIBRARY CL+SSL/CONFIG::LIBCRYPTO>.
   -> Loading foreign library #<LIBRARY WEBVIEW::LIBWEBVIEW>.
   -> Running BOOT/DEPLOY::UIOP
 ==> Launching application.
Gtk-Message: 12:54:15.480: Failed to load module "canberra-gtk-module"
/usr/lib64/gvfs/libgvfscommon.so: undefined symbol: g_task_set_static_name
Failed to load module: /usr/lib64/gio/modules/libgvfsdbus.so
Gtk-Message: 12:54:15.514: Failed to load module "colorreload-gtk-module"
Gtk-Message: 12:54:15.514: Failed to load module "window-decorations-gtk-module"

** (lem.real:14095): ERROR **: 12:54:15.651: Unable to spawn a new child process: Failed to spawn child process “/usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/WebKitNetworkProcess” (No such file or directory)
 ==> Encountered unhandled error: The value
                                    :INVALID-CODE-OBJECT-AT-PC
                                  is not of type
                                    (SIMPLE-ARRAY (UNSIGNED-BYTE 63) (*))
 ==> Running quit hooks.
$ _
CODE 2
$ ./Lem-x86_64.AppImage 
 ==> Performing warm boot.
   -> Build time was: 2025-10-30 01:44:49 UTC
   -> Source checksum: 8EFED5B991844F8C7CE3EB6351ED4014E2DFCE6EEADAE0789C98F68F
   -> Runtime directory is /tmp/.mount_Lem-x8PoMhdk/usr/libexec/
   -> Resource directory is /tmp/.mount_Lem-x8PoMhdk/usr/libexec/
 ==> Running boot hooks.
   -> Running BOOT/DEPLOY:FOREIGN-LIBRARIES
 ==> Reloading foreign libraries.
   -> Loading foreign library #<LIBRARY CL-CHARMS/LOW-LEVEL::LIBCURSES>.
   -> Loading foreign library #<LIBRARY LEM-TERMINAL/FFI::TERMINAL>.
   -> Loading foreign library #<LIBRARY ASYNC-PROCESS::ASYNC-PROCESS>.
   -> Loading foreign library #<LIBRARY CL+SSL/CONFIG::LIBSSL>.
   -> Loading foreign library #<LIBRARY CL+SSL/CONFIG::LIBCRYPTO>.
   -> Loading foreign library #<LIBRARY WEBVIEW::LIBWEBVIEW>.
   -> Running BOOT/DEPLOY::UIOP
 ==> Launching application.
Gtk-Message: 16:32:15.370: Failed to load module "canberra-gtk-module"
/usr/lib64/gvfs/libgvfscommon.so: undefined symbol: g_task_set_static_name
Failed to load module: /usr/lib64/gio/modules/libgvfsdbus.so
Gtk-Message: 16:32:15.391: Failed to load module "colorreload-gtk-module"
/usr/lib64/gvfs/libgvfscommon.so: undefined symbol: g_task_set_static_name
Failed to load module: /usr/lib64/gio/modules/libgvfsdbus.so
/tmp/.mount_Lem-x8PoMhdk/usr/lib/libssl.so.3: version `OPENSSL_3.2.0' not found (required by /lib64/libcurl.so.4)
Failed to load module: /usr/lib64/gio/modules/libgiolibproxy.so
/usr/lib64/gio/modules/libdconfsettings.so: undefined symbol: g_assertion_message_cmpint
Failed to load module: /usr/lib64/gio/modules/libdconfsettings.so
Gtk-Message: 16:32:15.552: Failed to load module "canberra-gtk-module"

** (WebKitWebProcess:21124): WARNING **: 16:32:15.565: Error loading the injected bundle (/usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/injected-bundle/libwebkit2gtkinjectedbundle.so): /usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/injected-bundle/libwebkit2gtkinjectedbundle.so: cannot open shared object file: No such file or directory
/usr/lib64/gio/modules/libgiognutls.so: undefined symbol: g_once_init_leave_pointer
Failed to load module: /usr/lib64/gio/modules/libgiognutls.so

** (lem.real:21092): WARNING **: 16:32:40.544: atk-bridge: get_device_events_reply: unknown signature
$ _
Lingua principale
Common Lisp
Stelle
3.1k
Fork
261
Merge medio
4g 3h
PR unite (30g)
13

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di lem-project/lem

Tutte le issue di lem-project/lem

Issue simili

Altre issue su Build System

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.