-
-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check the existence of dconf-editor's schema #1447
Check the existence of dconf-editor's schema #1447
Conversation
We need to check the existence of dconf-editor's GSettings schema before using it, because the program will abort if dconf-editor is not installed on the system when it tries to access it.
1b0c558
to
d76b914
Compare
Not tested, but makes sense 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This builds and runs fine, and it does indeed let mate-panel run without dconf-editor installed. This removes a pesky unreported dependency, at least in Debian dconf-editor is NOT listed as a dependency but the panel without this change won't run without it.
The checking code is similar to what is used to look for the GNOME schemas read by wayland compositors in mate-control-center's appearance capplet and in wayland sessions load them if and only if present.
Anyone else want to review this before merging? This is a bugfix and in my opinion is another one worth cherrypicking to 1.28 and thankfully, this time around the issue this fixes didn't get introduced until 1.27 and never made it into 1.26 |
Any updates on this? This is something we really need to get done, as we have in 1.28 as it stands a new and unreported dependency on dconf-editor that could hand a lot of users an ugly surprise. Most won't know the reason their panel just keeps crashing is that they don't have dconf-editor installed. It seems ready to go though we haven't gotten any reviews. Should I go ahead and merge this or not? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I was just about to fix this in my own PR when I saw this.
Sorry, I've been away for months due to terrible illness.
No problem, thanks for reviewing and merging when you could. |
We have this Travis error that will probably block a new release of 1.28 carrying this fix from deploying. I do NOT know how to fix these Travis problems or know Ruby at all: $ if [[ "$TRAVIS_SECURE_ENV_VARS" == "true" && "$TRAVIS_PULL_REQUEST" != "false" &&
|
We need to check the existence of dconf-editor's GSettings schema before using it, because the program will abort if dconf-editor is not installed on the system when it tries to access it.
Cherrypicked to 1.28 |
We need someone to fix the Travis issue blocking deployments or show me how to do it so I or someone else can release 1.28.3 so distros can pick this up. Until then, I would advise distrops to apply this patch especially if they don't want to ship dconf-editor or want to use an older version of it that uses the original interface |
15de78f
|
Here's an attempt to fix the Travis error: #1454 |
1.28.4 is out, ready for distros |
You guys are amazing. About a year ago I opened an issue talking about this, and eventually wrote a patch to fix it, only to hear from you that you couldn't replicate the issue and that dconf-editor should be installed anyway. Although better late than never, my suggestion is: don't become what GNOME is. Listening to people and having good sense is always the best path. :) |
We need to check the existence of dconf-editor's GSettings schema before using it, because the program will abort if dconf-editor is not installed on the system when it tries to access it.