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:
I turned on my virtual machine and after few minutes I saw "Oh no! Something has gone wrong." message.

Version-Release number of selected component:
gnome-settings-daemon-3.8.1-1.el7

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-settings-daemon
crash_function: g_variant_valist_new_nnp
executable:     /usr/libexec/gnome-settings-daemon
kernel:         3.7.0-0.36.el7.x86_64
runlevel:       unknown
uid:            42

Truncated backtrace:
Thread no. 1 (9 frames)
 #2 g_variant_valist_new_nnp at gvariant.c:4155
 #3 g_variant_valist_new_leaf at gvariant.c:4311
 #4 g_variant_valist_new at gvariant.c:4493
 #6 g_variant_new_va at gvariant.c:4702
 #7 g_variant_new at gvariant.c:4641
 #8 shell_key_grabber_call_grab_accelerators at shell-key-grabber.c:684
 #9 grab_media_keys at gsd-media-keys-manager.c:506
 #10 retry_grabs at gsd-media-keys-manager.c:451
 #16 gtk_main at /lib64/libgtk-3.so.0

Created attachment 746144 [details]
File: backtrace

Created attachment 746145 [details]
File: cgroup

Created attachment 746146 [details]
File: core_backtrace

Created attachment 746147 [details]
File: dso_list

Created attachment 746148 [details]
File: environ

Created attachment 746149 [details]
File: limits

Created attachment 746150 [details]
File: maps

Created attachment 746151 [details]
File: open_fds

Created attachment 746152 [details]
File: proc_pid_status

Created attachment 746153 [details]
File: var_log_messages

This bug seems to be fixed after updating the system.