Bug 1027334

Summary: [abrt] gnome-settings-daemon-3.10.1-2.fc20: g_hash_table_lookup_node: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Maël Lavault <mael.lavault>
Component: gnome-settings-daemonAssignee: Bastien Nocera <bnocera>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: avv.marengoni, bac_norman, bnocera, fmuellner, mkasik, ofourdan, rstrode, tiagomatos
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/1191fecb096d8d9b976e768ada053a00e473a560
Whiteboard: abrt_hash:b619e78641a9137ad2553db33006d2330a5d0a86
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 12:49:48 UTC Type: ---
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
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Maël Lavault 2013-11-06 15:18:44 UTC 
Version-Release number of selected component:
gnome-settings-daemon-3.10.1-2.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-settings-daemon
crash_function: g_hash_table_lookup_node
executable:     /usr/libexec/gnome-settings-daemon
kernel:         3.11.6-301.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_hash_table_lookup_node at ghash.c:382
 #1 g_hash_table_lookup at ghash.c:1076
 #2 g_dbus_interface_info_lookup_method at gdbusintrospection.c:1934
 #3 validate_and_maybe_schedule_method_call at gdbusconnection.c:4945
 #4 obj_message_func at gdbusconnection.c:5041
 #5 distribute_method_call at gdbusconnection.c:6830
 #6 on_worker_message_received at gdbusconnection.c:2374
 #7 _g_dbus_worker_emit_message_received at gdbusprivate.c:493
 #8 _g_dbus_worker_queue_or_deliver_received_message at gdbusprivate.c:521
 #9 _g_dbus_worker_do_read_cb at gdbusprivate.c:805
Comment 1 Maël Lavault 2013-11-06 15:18:56 UTC 
Created attachment 820467 [details]
File: backtrace
Comment 2 Maël Lavault 2013-11-06 15:19:00 UTC 
Created attachment 820468 [details]
File: cgroup
Comment 3 Maël Lavault 2013-11-06 15:19:05 UTC 
Created attachment 820469 [details]
File: core_backtrace
Comment 4 Maël Lavault 2013-11-06 15:19:09 UTC 
Created attachment 820470 [details]
File: dso_list
Comment 5 Maël Lavault 2013-11-06 15:19:13 UTC 
Created attachment 820471 [details]
File: environ
Comment 6 Maël Lavault 2013-11-06 15:19:19 UTC 
Created attachment 820472 [details]
File: exploitable
Comment 7 Maël Lavault 2013-11-06 15:19:24 UTC 
Created attachment 820473 [details]
File: limits
Comment 8 Maël Lavault 2013-11-06 15:19:30 UTC 
Created attachment 820474 [details]
File: maps
Comment 9 Maël Lavault 2013-11-06 15:19:34 UTC 
Created attachment 820475 [details]
File: open_fds
Comment 10 Maël Lavault 2013-11-06 15:19:39 UTC 
Created attachment 820476 [details]
File: proc_pid_status
Comment 11 Maël Lavault 2013-11-06 15:19:43 UTC 
Created attachment 820477 [details]
File: var_log_messages
Comment 12 Avvocato Andrea Marengoni 2014-10-28 11:25:19 UTC 
I am not sure that the problem is this, but I noticed that when starting appearance customizations in whole or in part are not loaded (that is, there is a hybrid between the default settings and the theme chosen for mutter-metacity and gnome shell). Restarting the shell with ALT and F2 the situation does not change. Congratulations anyway for the really excellent quality of Fedora and thanks for caring in releases (do well to wait until it is ready; the stability, not surprisingly, is very close to that of Debian, but with many more updates; good!!!).
Comment 13 Fedora End Of Life 2015-05-29 09:42:19 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 14 Fedora End Of Life 2015-06-29 12:49:48 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.