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.

Version-Release number of selected component:
dconf-editor-0.16.0-6.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        dconf-editor
crash_function: composite_aligned_boxes
executable:     /usr/bin/dconf-editor
kernel:         3.10.0-123.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 composite_aligned_boxes at cairo-traps-compositor.c:1276
 #1 clip_and_composite_boxes at cairo-traps-compositor.c:1766
 #2 _cairo_traps_compositor_fill at cairo-traps-compositor.c:2215
 #3 _cairo_compositor_fill at cairo-compositor.c:203
 #4 _cairo_xlib_surface_fill at cairo-xlib-surface.c:1645
 #5 _cairo_surface_fill at cairo-surface.c:2238
 #6 _cairo_surface_offset_fill at cairo-surface-offset.c:239
 #7 _cairo_surface_subsurface_fill at cairo-surface-subsurface.c:165
 #8 _cairo_surface_fill at cairo-surface.c:2238
 #9 _cairo_gstate_fill at cairo-gstate.c:1308

Created attachment 910548 [details]
File: backtrace

Created attachment 910549 [details]
File: cgroup

Created attachment 910550 [details]
File: core_backtrace

Created attachment 910551 [details]
File: dso_list

Created attachment 910552 [details]
File: environ

Created attachment 910553 [details]
File: limits

Created attachment 910554 [details]
File: maps

Created attachment 910555 [details]
File: open_fds

Created attachment 910556 [details]
File: proc_pid_status

Created attachment 910557 [details]
File: var_log_messages

The problem here is that keys with long string values can cause problems with allocation of memory for the Gtk.CellRendererText which shows the values in dconf-editor.
I've observed the reported crash on virtual machines (it is probably related to amount of video memory).
I've prepared a patch which ellipsizes the text renderer so that the widget doesn't need to allocate the big amount of memory. I'll wait for upstream's decision before giving this devel_ack+.

Marek

This is fixed by the gtk3 rebase which removed the problematic linear gradient (see https://bugzilla.gnome.org/show_bug.cgi?id=732737#c6 for details).

No, I don't.

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-2116.html