#1636 Investigate the use of gconf and potentially remove it

Open
opened 7 months ago by wolfbeast · 6 comments
wolfbeast commented 7 months ago (Migrated from github.com)

There are some rumours on the grapevine that calls to gconf on Linux on later gnome would somehow “bust it”, if installed.

We need to:

  • Get more details to know if this is an issue
  • If so, we should remove the use of calls to gconf, and solely use gsettings instead.
    This involves
    • removal from shellservice
    • removal from system proxy
    • removal from accessibility
    • then removing the nsGConfservice altogether.

Preliminary research shows that gsettings should be available in all the versions of glib we support, and goes back as far as MATE and Cinnamon, so it should cover all sane environments and won’t result in loss of functionality on all reasonably-supported target OSes.
Ref BZ 1433685 and dependent bugs listed.

There are some rumours on the grapevine that calls to `gconf` on Linux on later gnome would somehow "bust it", if installed. We need to: - Get more details to know if this is an issue - If so, we should remove the use of calls to `gconf`, and solely use `gsettings` instead. This involves - removal from shellservice - removal from system proxy - removal from accessibility - then removing the `nsGConfservice` altogether. Preliminary research shows that `gsettings` should be available in all the versions of glib we support, and goes back as far as MATE and Cinnamon, so it should cover all sane environments and won't result in loss of functionality on all reasonably-supported target OSes. Ref [BZ 1433685](https://bugzilla.mozilla.org/show_bug.cgi?id=1433685) and dependent bugs listed.
mattatobin commented 7 months ago (Migrated from github.com)
Owner

MATE is excluded from shellservice because it’s settings are spread between gsettings and dconf and dconf is not gconf and we can’t address it.

Sorry for the earilier confusion of MATE being in the mix.

MATE is excluded from shellservice because it's settings are spread between gsettings and dconf and dconf is not gconf and we can't address it. Sorry for the earilier confusion of MATE being in the mix.
wolfbeast commented 7 months ago (Migrated from github.com)
Owner

Right, for MATE it wouldn’t make a difference then since it’s solely using gsettings already anyway as it is now (since we don’t call out to dconf).

Right, for MATE it wouldn't make a difference then since it's solely using gsettings already anyway as it is now (since we don't call out to dconf).
mattatobin commented 7 months ago (Migrated from github.com)
Owner

Well the wallpaper settings for MATE is in dconf so we can’t set it if we wanted to. Either past or future we aren’t gonna be able to accommodate MATE without dconf support and other accommodations so for now I am not considering it.

Well the wallpaper settings for MATE is in dconf so we can't set it if we wanted to. Either past or future we aren't gonna be able to accommodate MATE without dconf support and other accommodations so for now I am not considering it.
wolfbeast commented 7 months ago (Migrated from github.com)
Owner

Yes I already understood. I’m just looking at this from the potential change. Since MATE isn’t using this there won’t be an impact. catering to MATE for actually making that work would be out of scope for this issue.

Yes I already understood. I'm just looking at this from the potential change. Since MATE isn't using this there won't be an impact. catering to MATE for actually making that work would be out of scope for this issue.
wolfbeast commented 7 months ago (Migrated from github.com)
Owner

So do we have any information yet on if gconf usage actually busts anything? Or was it BS to push the removal?

So do we have any information yet on if `gconf` usage actually busts anything? Or was it BS to push the removal?
mattatobin commented 7 months ago (Migrated from github.com)
Owner

The Red Hat employee has not yet responded. A follow up message has been sent.

I am starting to seriously suspect this is coordinated bs to make older systems less useful. Gonna give it some more time, though.

However, Gnome env var checking does need to be broght up to date to use the xdg version but until we know more I intend to keep the check for the depercated gnome specific env var as fallback.

I’ll get around to it soonish for all allied applications.

The Red Hat employee has not yet responded. A follow up message has been sent. I am starting to seriously suspect this is coordinated bs to make older systems less useful. Gonna give it some more time, though. However, Gnome env var checking does need to be broght up to date to use the xdg version but until we know more I intend to keep the check for the depercated gnome specific env var as fallback. I'll get around to it soonish for all allied applications.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.