unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: 53344@debbugs.gnu.org
Subject: bug#53344: Inconsistency detected by ld.so: dl-call-libc-early-init.c: 37: _dl_call_libc_early_init: Assertion `sym != NULL' failed!
Date: Wed, 19 Jan 2022 11:31:24 +0100	[thread overview]
Message-ID: <87tue0auf7.fsf@gnu.org> (raw)
In-Reply-To: <87sftkind1.fsf@web.de> (Arne Babenhauserheide's message of "Wed,  19 Jan 2022 01:20:18 +0100")

Hi,

"Dr. Arne Babenhauserheide" <arne_bab@web.de> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> "Dr. Arne Babenhauserheide" <arne_bab@web.de> skribis:
>>
>>> when I call guix, I get the error
>>>
>>> Inconsistency detected by ld.so: dl-call-libc-early-init.c: 37:
>>> _dl_call_libc_early_init: Assertion `sym != NULL' failed!
>>>
>>> `which guix` gives
>>>
>>> /home/USER/.config/guix/current/bin/guix
>>
>> When did it start happening?
>
> It started happening a few weeks ago.
>
> I found the cause now, though: I had
>
> LD_LIBRARY_PATH=$HOME/.guix-profile/lib:$LD_LIBRARY_PATH
>
> in my .profile, because that was once needed to get some non-guix-builds
> working. Removing that and updating the core system (guix system
> reconfigure …) and rebooting resolved the issue.

OK (though I wouldn’t expect it to cause an assertion failure in ld.so).

> I still have some breakage left, though: On starting icecat, I see
> /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6: version `GLIBC_2.33' not found (required by /gnu/store/qw4dm41ik5krj0s2af9fbcccjga2bfg8-gvfs-1.48.1/lib/gvfs/libgvfscommon.so)
> Failed to load module: /run/current-system/profile/lib/gio/modules/libgioremote-volume-monitor.so
> /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6: version `GLIBC_2.33' not found (required by /run/current-system/profile/lib/gio/modules/libgvfsdbus.so)
> Failed to load module: /run/current-system/profile/lib/gio/modules/libgvfsdbus.so
> /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6: version `GLIBC_2.33' not found (required by /gnu/store/lxcz3h4klzg041f6rhi9lfyfqba3zizy-libproxy-0.4.17/lib/libproxy.so.1)
> Failed to load module: /run/current-system/profile/lib/gio/modules/libgiolibproxy.so

IceCat is trying to load libg*.so from /run/current-system/profile/lib,
but those are linked against the old libc (2.31).

The solution is to reconfigure your system to the new libc (2.33), as
provided by current Guix:

  sudo guix system reconfigure …

HTH!

Ludo’.




      reply	other threads:[~2022-01-19 10:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 11:49 bug#53344: Inconsistency detected by ld.so: dl-call-libc-early-init.c: 37: _dl_call_libc_early_init: Assertion `sym != NULL' failed! Dr. Arne Babenhauserheide
2022-01-18 17:52 ` Ludovic Courtès
2022-01-19  0:20   ` Dr. Arne Babenhauserheide
2022-01-19 10:31     ` Ludovic Courtès [this message]

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87tue0auf7.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=53344@debbugs.gnu.org \
    --cc=arne_bab@web.de \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).