From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Maya Tomasek <maya.tomasek@disroot.org>, 61103@debbugs.gnu.org
Subject: [bug#61103] No Subject
Date: Sat, 04 Feb 2023 00:04:00 +0100 [thread overview]
Message-ID: <a1ed636e2c45ff0bd368e08ede888a7436ae57e0.camel@gmail.com> (raw)
In-Reply-To: <7730eb7a4bbe3bde3de772349901ba21.maya.tomasek@disroot.org>
Hi,
Am Freitag, dem 27.01.2023 um 20:36 +0100 schrieb Maya Tomasek:
> From: Maya Tomasek <maya.tomasek@disroot.org>
> Date: Fri, 27 Jan 2023 20:26:11 +0100
> Subject: [PATCH] gnu: Move dconf-editor native-input glib:bin to
> propagated-inputs
>
> dconf-editor crashes with "No GSettings schemas are installed on the
> system", this provides the expected schemas.
> ---
> Hi,
>
> I have noticed that dconf-editor by default crashes as it has no
> schemas. This is probably undesired, as most users install dconf-
> editor to edit settings on gnome. But there is no indication that the
> actual error is missing glib:bin. The issue isn't fixed by moving
> glib:bin to inputs. It has to be in propagated inputs.
>
> Kind regards,
> Maya
I am fairly certain that by default, dconf-editor does not crash when
using gnome-desktop-service-type (i.e. the "default" configuration).
Now fair enough, it might still break in the way you described *outside
of gnome*, but in any case, propagating inputs is no solution and in
this case, you're breaking cross-compilation to rely on a side effect.
The package you do want is most likely gsettings-desktop-schemas, and I
think it ought to be possible to fix dconf-editor without propagating
it.
Cheers
next prev parent reply other threads:[~2023-02-03 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 19:36 [bug#61103] (no subject) Maya Tomasek via Guix-patches via
2023-02-03 23:04 ` Liliana Marie Prikler [this message]
2023-02-04 10:50 ` [bug#61103] No Subject guix-patches--- via
2023-02-04 17:26 ` Liliana Marie Prikler
2023-02-11 14:14 ` guix-patches--- via
2023-03-22 2:01 ` bug#61103: (no subject) Maxim Cournoyer
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=a1ed636e2c45ff0bd368e08ede888a7436ae57e0.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=61103@debbugs.gnu.org \
--cc=maya.tomasek@disroot.org \
/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).