Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
alter GNOME in such a way that it /does/ load a custom overrides file for a mode, presumably reading the modes/name.json file and using the contents of the 'overridesSchema' option.
Description of problem:
alter GNOME in such a way that it /does/ load a custom overrides file for a mode, presumably reading the modes/name.json file and using the contents of the 'overridesSchema' option.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Its related to
https://bugzilla.gnome.org/show_bug.cgi?id=751921https://git.gnome.org/browse/gnome-shell/commit/?id=dfc4cc4aafd1ca3dd5257341
(In reply to Ajinkya Patil from comment #0)
> Description of problem:
> alter GNOME in such a way that it /does/ load a custom overrides file for a
> mode, presumably reading the modes/name.json file and using the contents of
> the 'overridesSchema' option.
This was removed for a reason:
https://git.gnome.org//browse/gnome-shell/commit?id=ae2751a68b20ab281ca74affd61562fb8869b639
We really want to initialize the overrides before handling control over to the javascript code, or those issues will be back. It would be possible to have a small javascript hook to retrieve the setting, do the initialization in C, and then start the "real" javascript code, but that's quite horrible (we'd be starting the javascript engine, looking for session mode files in the filesystem, and loading and parsing them *twice* on startup).
A far less intrusive alternative would be to allow setting a custom overrides schema via an environment variable or command line switch.
(In reply to Florian Müllner from comment #2)
> A far less intrusive alternative would be to allow setting a custom
> overrides schema via an environment variable or command line switch.
That would be great - we're creating a new X session anyway, so we can set a variable or command line switch (which is already done to set the mode).
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:0770