From: Christopher Baines <mail@cbaines.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: tobias.kortkamp@gmail.com, 58221@debbugs.gnu.org,
Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: bug#58221: nautilus: Crashes loading KgxNautilus plugin twice (problems with NAUTILUS_EXTENSION_PATH)
Date: Sun, 20 Nov 2022 18:02:56 +0000 [thread overview]
Message-ID: <874jutwljp.fsf@cbaines.net> (raw)
In-Reply-To: <87ilj95xft.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Agreed! I don’t use GNOME and I don’t even know what KgxNautilus is,
> but here’s a patch that may fix this by ensuring Nautilus doesn’t load
> the same extension twice.
>
> Could you give it a spin and lemme know if it solves this issue?\
>
> That’ll get us closer to a release. :-)
I've tried it out and it looks to fix the issue, please push!
Thanks,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2022-11-20 18:04 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
2022-11-10 10:42 ` Christopher Baines
2022-11-20 17:48 ` Ludovic Courtès
2022-11-20 18:02 ` Christopher Baines [this message]
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
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=874jutwljp.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=58221@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=ludo@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 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).