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.

Bug 1435410

Summary: My $HOME is littered with coredumps of gsettings-data-convert
Product: Red Hat Enterprise Linux 7 Reporter: Matěj Cepl <mcepl>
Component: gnome-settings-daemonAssignee: Rui Matos <rmatos>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: cgarnach, jkoten, mcepl, tpelka
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 3.22.2-5 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 22:38:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
backtrace (abrt fails to do anything for me) none

Description Matěj Cepl 2017-03-23 17:57:41 UTC
Created attachment 1265854 [details]
backtrace (abrt fails to do anything for me)

Description of problem:
I have no idea how it happens, but there is just plenty of coredumps (tens in days of using RHEL 7.4) of gsettings-data-convert.

Version-Release number of selected component (if applicable):
GConf2-3.2.6-8.el7.x86_64

How reproducible:
happens

Comment 1 Matěj Cepl 2017-03-24 10:04:08 UTC
And having totem-3.22.1-1.el7.x86_64 (if this is actually a duplicate of bug 1412335).

Comment 2 Marek Kašík 2017-03-24 10:12:19 UTC
This is an issue in gnome-settings-daemon according to the warning message "Settings schema 'org.gnome.settings-daemon.peripherals.mouse' does not contain a key named 'motion-acceleration'".
I'm reassigning this bug to gnome-settings-daemon then.

Comment 3 Bastien Nocera 2017-03-24 10:16:58 UTC
This is a problem upstream as well. The mouse and touchpad GSettings in g-s-d got obsoleted, but the convert files didn't get updated.

Comment 5 Carlos Garnacho 2017-06-08 19:38:03 UTC
Pushed a fix to the convert script, available in gnome-settings-daemon 3.22.2-5

Comment 10 Matěj Cepl 2017-06-15 14:28:42 UTC
After upgrading to the mentioned version of the package I don't see THESE coredumps anymore (just filed bug 1461878 :().

Comment 11 errata-xmlrpc 2017-08-01 22:38:29 UTC
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-2017:2096