all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Martin <secure@alm.website>
To: 60235@debbugs.gnu.org
Subject: bug#60235: gajim: dlopen()s non-Guix libc
Date: Tue, 20 Dec 2022 20:09:17 -0500	[thread overview]
Message-ID: <20221220200917.122378e0@spock.hosts.alm.website> (raw)

[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]

I run Guix on an Alpine Linux host system. Alpine uses the musl C
library. This seems to be what exposes an issue in the gajim Guix
package for me.

I believe what is happening is the following: Gajim dlopen()s libc via
Python's ctypes library, and ends up finding the system libc, not the
Guix-provided libc it is supposed to be linked against.

The result is the following crash:

Traceback (most recent call last):
  File "/gnu/store/n2f3pi9cciaxgbvc4nhqzswslv4wycj2-gajim-1.4.6/bin/.gajim-real", line 33, in <module>
    sys.exit(load_entry_point('gajim==1.4.6', 'gui_scripts', 'gajim')())
  File "/gnu/store/n2f3pi9cciaxgbvc4nhqzswslv4wycj2-gajim-1.4.6/lib/python3.9/site-packages/gajim/gajim.py", line 159, in main
    _set_proc_title()
  File "/gnu/store/n2f3pi9cciaxgbvc4nhqzswslv4wycj2-gajim-1.4.6/lib/python3.9/site-packages/gajim/gajim.py", line 138, in _set_proc_title
    libc = CDLL(find_library('c'))
  File "/gnu/store/lvip6h5pamjwmvnkwg60sjb63ph8698k-python-3.9.9/lib/python3.9/ctypes/__init__.py", line 374, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: libc.musl-x86_64.so.1: cannot open shared object file: No such file or directory

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2022-12-21 16:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221220200917.122378e0@spock.hosts.alm.website \
    --to=secure@alm.website \
    --cc=60235@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.