unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: 宋文武 <iyzsong@envs.net>
Cc: 59579@debbugs.gnu.org, glv@posteo.net,
	"Clément Lassieur" <clement@lassieur.org>
Subject: bug#59579: installing zbar prevents gdm to start on Ubuntu 22.04 foreign distro
Date: Tue, 31 Jan 2023 10:52:51 +0100	[thread overview]
Message-ID: <86k013vxn0.fsf@gmail.com> (raw)
In-Reply-To: <875ycnz0he.fsf@envs.net>

Hi,

On Tue, 31 Jan 2023 at 14:23, 宋文武 via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:

> Hello, I don't think XDG_DATA_DIRS should be the problems, but other
> environment variables with "lib", since the xdg data should be
> portable...

I had the issue yesterday on Ubuntu. :-)

> I think GUIX_GTK3_PATH, QT_PLUGIN_PATH, GDK_PIXBUF_MODULE_FILE should be
> the problems.

None of these environment variables were in my profile, IIRC.  From my
small experiment, the only common one is XDG_DATA_DIRS.  For instance, I
had the issue and I just removed the package ’fontconfig’ which fixed
the issue;  the environment variables reads,

--8<---------------cut here---------------start------------->8---
$ guix shell fontconfig --search-paths
export PATH="/gnu/store/i5rdrrdq4zi98yzcw7rza169ir1zkj6n-profile/bin${PATH:+:}$PATH"
export XDG_DATA_DIRS="/gnu/store/i5rdrrdq4zi98yzcw7rza169ir1zkj6n-profile/share${XDG_DATA_DIRS:+:}$XDG_DATA_DIRS"
--8<---------------cut here---------------end--------------->8---

The package ’zbar’ also provides XDG_DATA_DIRS.  Maybe, I am missing
something.


Cheers,
simon







      reply	other threads:[~2023-01-31 12:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 17:45 bug#59579: installing zbar prevents gdm to start on Ubuntu 22.04 foreign distro Clément Lassieur
2023-01-26 17:10 ` Simon Tournier
2023-01-31  6:23   ` 宋文武 via Bug reports for GNU Guix
2023-01-31  9:52     ` zimoun [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=86k013vxn0.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=59579@debbugs.gnu.org \
    --cc=clement@lassieur.org \
    --cc=glv@posteo.net \
    --cc=iyzsong@envs.net \
    /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).