From: Thorsten Wilms <t_w_@freenet.de>
To: help-guix@gnu.org
Subject: Re: Foreign distro Unity desktop broken after guix update
Date: Mon, 27 Dec 2021 22:17:22 +0100 [thread overview]
Message-ID: <20211227221722.62d779d6c9f9de6a1f98a7bf@freenet.de> (raw)
In-Reply-To: <875yr97sbg.fsf@posteo.net>
On Mon, 27 Dec 2021 19:37:07 +0000
Fredrik Salomonsson <plattfot@posteo.net> wrote:
> printenv LD_LIBRARY_PATH
Empty
> env | grep /gnu/store
Empty
> Another reason why the runtime linker would pick up that library would
> be if its path is added to the /etc/ld.so.conf configs. But I highly
> doubt it's the issue.
Via include, that makes for the following list:
/usr/lib/x86_64-linux-gnu/libfakeroot
/usr/local/lib
/usr/local/lib/x86_64-linux-gnu
/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu
> If you want to go down the rabbit hole you can use the LD_DEBUG
> environment variable to get some debug output. The libs option is
> probably the most useful to you as that will print where it's looking
> for stuff and why. Use:
>
> env LD_DEBUG=libs LD_DEBUG_OUTPUT=/tmp/trace <executable>
Interesting, but I’m puzzled about how to use that with compiz/unity.
> I hope that helps a bit.
A good start. Thank you!
--
Thorsten Wilms <t_w_@freenet.de>
next prev parent reply other threads:[~2021-12-27 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 15:18 Foreign distro Unity desktop broken after guix update Thorsten Wilms
2021-12-27 19:37 ` Fredrik Salomonsson
2021-12-27 21:17 ` Thorsten Wilms [this message]
2021-12-28 10:16 ` Thorsten Wilms
2021-12-28 21:45 ` Fredrik Salomonsson
2021-12-29 8:59 ` Thorsten Wilms
2021-12-30 1:11 ` Fredrik Salomonsson
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=20211227221722.62d779d6c9f9de6a1f98a7bf@freenet.de \
--to=t_w_@freenet.de \
--cc=help-guix@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.
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).