public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: GSettings-to-GConf problem
Date: Tue, 30 Apr 2013 21:02:04 -0700	[thread overview]
Message-ID: <CAN0CFw2ASPCU25xfXus+0X88qJ0zjsS2q3wRMS8-ns6=GP2hrg@mail.gmail.com> (raw)
In-Reply-To: <20130501023822.GA6357@waltdnes.org>

>> >> > shotwell keeps crashing when I import photos with "Copy Photos" as
>> >> > opposed to "Import in Place".  I've been over this thoroughly with the
>> >> > shotwell list and they've come to these conclusions:
>> >> >
>> >> > "There may be something about the configuration mapper on your machine
>> >> > that is just broken."
>> >> >
>> >> > "the problem occurred deep inside of the GSettings-to-GConf mapper
>> >> > (gconfsettingsbackend)"
>> >> >
>> >> > "ask the Gentoo packagers why they're using a GSettings-to-GConf
>> >> > mapper, because GSettings is designed as an evolution over GConf and
>> >> > should have no relation to it whatsoever"
>> >> >
>> >> > Can anyone shed any light on any of this?  Should I file a Gentoo bug?
>> >> >
>> >> > - Grant
>> >
>> >   I don't know if this is related or not, but GNOME seems to be in the
>> > middle of migrating away from Gconf to Gsettings.  In plain English,
>> > Gconf is being deprecated, and may not be supported in your case.
>>
>> That's exactly the problem.  Gentoo seems to be using a
>> GSettings-to-GConf mapper when they should be using GSettings
>> directly.  Does anyone know what is happening in this area of Gentoo?
>
>   I was going to file a bug for GNUMERIC.  But I decided to send an
> email to the Gentoo dev list.  There are already a similar bugs for
> other applications...
>
> https://bugs.gentoo.org/show_bug.cgi?id=327595
> https://bugs.gentoo.org/show_bug.cgi?id=327595
> https://bugs.gentoo.org/show_bug.cgi?id=363631
>
> ...and it looks like it'll affect virtually every GNOME-related app.
> This is going to have to be handled at a higher level than whack-a-mole
> bug reports.

I see your thread on gentoo-dev.  Many thanks for taking this to the
right place.  The solution seems to be keywording a bunch of ~arch
gnome stuff.

- Grant


  reply	other threads:[~2013-05-01  4:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 20:18 [gentoo-user] GSettings-to-GConf problem Grant
2013-04-29 22:58 ` [gentoo-user] " Grant
2013-04-30  9:46   ` Walter Dnes
2013-04-30 19:01     ` Grant
2013-05-01  2:38       ` Walter Dnes
2013-05-01  4:02         ` Grant [this message]
2013-05-02 21:56           ` Walter Dnes
2013-05-03 14:53             ` Fast Turtle
2013-05-03 19:56             ` Grant
2013-05-01  4:03       ` Walter Dnes

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='CAN0CFw2ASPCU25xfXus+0X88qJ0zjsS2q3wRMS8-ns6=GP2hrg@mail.gmail.com' \
    --to=emailgrant@gmail.com \
    --cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox