From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Tobias Kortkamp <tobias.kortkamp@gmail.com>, 58221@debbugs.gnu.org
Subject: bug#58221: nautilus: Crashes loading KgxNautilus plugin twice (problems with NAUTILUS_EXTENSION_PATH)
Date: Wed, 09 Nov 2022 20:37:57 +0100 [thread overview]
Message-ID: <6a3df82e8c2720bc7d3e792afa1fce5b7be874dc.camel@gmail.com> (raw)
In-Reply-To: <YzgknxgNeYBPf2/8@anubis>
Am Samstag, dem 01.10.2022 um 13:29 +0200 schrieb Tobias Kortkamp:
> Hi,
>
> The problem seems to be that NAUTILUS_EXTENSION_PATH contains the
> same path twice and that it tries to load KgxNautilus from each of
> the paths:
>
> $ echo $NAUTILUS_EXTENSION_PATH
> /run/current-system/profile/lib/nautilus/site-
> extensions:/run/current-system/profile/lib/nautilus/site-extensions
>
> Running Nautilus like this works fine:
>
> $ NAUTILUS_EXTENSION_PATH=/run/current-
> system/profile/lib/nautilus/site-extensions nautilus
I only know of one thing setting this variable, that being nautilus'
search-path. Do you by chance source some profile multiple times?
Cheers
next prev parent reply other threads:[~2022-11-09 19:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 11:29 bug#58221: nautilus: Crashes loading KgxNautilus plugin twice (problems with NAUTILUS_EXTENSION_PATH) Tobias Kortkamp
2022-10-01 12:32 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-10-01 14:40 ` Tobias Kortkamp
2022-10-01 18:14 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-10-06 7:50 ` Jascha Geerds
2022-10-03 7:46 ` bug#58221: confirmation Attila Lendvai
2022-10-28 13:32 ` bug#58221: (no subject) Alexandre Hannud Abdo
2022-11-09 12:54 ` bug#58221: nautilus: Crashes loading KgxNautilus plugin twice (problems with NAUTILUS_EXTENSION_PATH) Christopher Baines
2022-11-09 19:37 ` Liliana Marie Prikler [this message]
2022-11-10 10:42 ` Christopher Baines
2022-11-20 17:48 ` Ludovic Courtès
2022-11-20 18:02 ` Christopher Baines
2022-11-20 22:23 ` Ludovic Courtès
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=6a3df82e8c2720bc7d3e792afa1fce5b7be874dc.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=58221@debbugs.gnu.org \
--cc=tobias.kortkamp@gmail.com \
/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.