unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: raingloom <raingloom@riseup.net>
Cc: 42076@debbugs.gnu.org
Subject: bug#42076: SSL_CERT_* variables and GVFS (and probably more) are not initialized if you don't use GDM
Date: Wed, 13 Jul 2022 23:36:03 -0400	[thread overview]
Message-ID: <87sfn4xt5o.fsf@gmail.com> (raw)
In-Reply-To: <20200627221605.38116e75@riseup.net> (raingloom@riseup.net's message of "Sat, 27 Jun 2020 22:16:05 +0200")

Hi raingloom,

raingloom <raingloom@riseup.net> writes:

> On Sat, 27 Jun 2020 11:53:01 +0200
> Tobias Geerinckx-Rice <me@tobias.gr> wrote:
>
>> Hi!
>> 
>> Thanks for the bug report.  How are these two things related?  Did 
>> GVFS start working when you fixed your certs?  Is GVFS failing 
>> because of other unset search paths?  They should be tracked as 
>> separate bug #s otherwise.
>
> No idea, I don't know enough about GVFS to know how it's initalized.
> But this falls into the same category for me, ie.: a bunch of things
> are not initalized.
> But actually I've already made a bug report about it, it's just that
> nobody replied to it. See 41927.

I agree the user experience often suffers from the fact that:

1. it's not obvious that consumers applications are the ones typically
causing environment variables to be defined. 

2. the system and user profiles are not merged, which often lead to
surprises (I have this in my operating-system, and that in my user
profile, and they don't work together!).

1. would be (mostly?) addressed with #22138, and 2. with #20255.  If
you'd like to participate in fixing these, there are at least a patch to
try in 20255, I believe.

Given these issues are known and tracked already, I'll close this bug.

Thanks,

Maxim




      reply	other threads:[~2022-07-14  3:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-27  3:35 bug#42076: SSL_CERT_* variables and GVFS (and probably more) are not initialized if you don't use GDM raingloom
2020-06-27  9:53 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-06-27 20:16   ` raingloom
2022-07-14  3:36     ` Maxim Cournoyer [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=87sfn4xt5o.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=42076@debbugs.gnu.org \
    --cc=raingloom@riseup.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).