unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jascha Geerds" <jascha@geerds.org>
To: 58221@debbugs.gnu.org
Cc: sughosha@proton.me
Subject: bug#58221: nautilus: Crashes loading KgxNautilus plugin twice (problems with NAUTILUS_EXTENSION_PATH)
Date: Thu, 06 Oct 2022 09:50:12 +0200	[thread overview]
Message-ID: <fa90f02e-e5e7-4e7a-bafe-0bae375763f8@app.fastmail.com> (raw)
In-Reply-To: <40D3195B-B55D-4AEF-AFF8-AA6A14EFC97B@tobias.gr>

Am Sa, 1. Okt 2022, um 20:14, schrieb Tobias Geerinckx-Rice via Bug reports for GNU Guix:
> So it *still* fails to find tracker3 before segfaulting?  Possible.  
> Could be a missing substitution, or it falling back to some other 
> (search) path...

It seems like this issue is due to commit 103d8229cbbd3baefe1f3b02bc2edff9c816b0bf where "gnome-terminal" is replaced by "gnome-console". There is some nautilus extension path stuff in the gnome-console derivation which I do not fully understand (cb2d5063a0353a3aa93d513979c8a7fc80db1460).




  reply	other threads:[~2022-10-08 12:47 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 [this message]
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
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=fa90f02e-e5e7-4e7a-bafe-0bae375763f8@app.fastmail.com \
    --to=jascha@geerds.org \
    --cc=58221@debbugs.gnu.org \
    --cc=sughosha@proton.me \
    /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).