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.

Description of problem:
1. yum remove  gnome-classic-session 
2. gnome-tweak-tool 
(gnome-tweak-tool:29876): GLib-GIO-ERROR **: Settings schema 'org.gnome.shell.extensions.classic-overrides' is not installed
Trace/breakpoint trap (core dumped)

Version-Release number of selected component:
gnome-tweak-tool-3.14.3-1.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/bin/python /usr/bin/gnome-tweak-tool
crash_function: g_settings_set_property
executable:     /usr/bin/python2.7
kernel:         3.10.0-306.0.1.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_settings_set_property at /lib64/libgio-2.0.so.0
 #3 g_object_new_internal at /lib64/libgobject-2.0.so.0
 #5 pygobject_constructv at /usr/lib64/python2.7/site-packages/gi/_gi.so
 #6 pygobject_init at /usr/lib64/python2.7/site-packages/gi/_gi.so
 #7 wrap_init at /lib64/libpython2.7.so.1.0
 #8 PyObject_Call at /lib64/libpython2.7.so.1.0
 #9 PyEval_CallObjectWithKeywords at /lib64/libpython2.7.so.1.0
 #10 wrapperdescr_call at /lib64/libpython2.7.so.1.0
 #11 PyObject_Call at /lib64/libpython2.7.so.1.0
 #12 PyEval_EvalFrameEx at /lib64/libpython2.7.so.1.0

Created attachment 1066758 [details]
File: backtrace

Created attachment 1066759 [details]
File: cgroup

Created attachment 1066760 [details]
File: core_backtrace

Created attachment 1066761 [details]
File: dso_list

Created attachment 1066762 [details]
File: environ

Created attachment 1066763 [details]
File: limits

Created attachment 1066764 [details]
File: machineid

Created attachment 1066765 [details]
File: maps

Created attachment 1066766 [details]
File: open_fds

Created attachment 1066767 [details]
File: proc_pid_status

Do you have the package gnome-classic-session installed?

Crashed only when gnome-classic-session is uninstalled. 
I remove the rpm during attempt to remove a broken extension - see bug 1256647

Still this is a bug - crash is incorrect behaviour - shouldn't be the gnome-classic-session a dependency of gnome-tweak-tool in RHEL7?

(In reply to Ondrej Hudlicky from comment #13)
> Still this is a bug - crash is incorrect behaviour - shouldn't be the
> gnome-classic-session a dependency of gnome-tweak-tool in RHEL7?

g-t-t would have to depend on almost all desktop rpms, so no. But we can avoid the crash, sure.

Will need the QA ack

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://rhn.redhat.com/errata/RHBA-2015-2215.html