Bug 1251350

Summary: [abrt] gnome-settings-daemon: g_bit_lock(): gnome-settings-daemon killed by SIGSEGV
Product: [Fedora] Fedora Reporter: muteki <muteki_f>
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: 22CC: bnocera, fmuellner, klember, mkasik, ofourdan, oholy, rstrode, tiagomatos
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/df0540379da9824bebab6b16030c8e0569d16a73
Whiteboard: abrt_hash:5428874c8cb89a5c62790a6c4409f5c54521fc5a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 17:24:08 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: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status none

Description muteki 2015-08-07 05:06:00 UTC 
Description of problem:
run dnf update several times the last 2 weeks (without rebooting the system), finally reboot the system today and got into this crashing issue  (keep failing to completely login to gnome-shell).  Searching around the web and someone suggests uninstall gnome-contacts and that got the system working again.

Version-Release number of selected component:
gnome-settings-daemon-3.16.2-1.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-settings-daemon
crash_function: g_bit_lock
executable:     /usr/libexec/gnome-settings-daemon
global_pid:     5149
kernel:         4.1.3-201.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_bit_lock at /lib64/libglib-2.0.so.0
 #1 g_variant_fill_gvs at /lib64/libglib-2.0.so.0
 #2 g_variant_serialiser_needed_size at /lib64/libglib-2.0.so.0
 #3 g_variant_ensure_size at /lib64/libglib-2.0.so.0
 #4 g_variant_fill_gvs at /lib64/libglib-2.0.so.0
 #5 g_variant_serialiser_needed_size at /lib64/libglib-2.0.so.0
 #6 g_variant_ensure_size at /lib64/libglib-2.0.so.0
 #7 g_variant_fill_gvs at /lib64/libglib-2.0.so.0
 #8 g_variant_serialiser_needed_size at /lib64/libglib-2.0.so.0
 #9 g_variant_ensure_size at /lib64/libglib-2.0.so.0
Comment 1 muteki 2015-08-07 05:06:02 UTC 
Created attachment 1060163 [details]
File: backtrace
Comment 2 muteki 2015-08-07 05:06:03 UTC 
Created attachment 1060164 [details]
File: cgroup
Comment 3 muteki 2015-08-07 05:06:04 UTC 
Created attachment 1060165 [details]
File: core_backtrace
Comment 4 muteki 2015-08-07 05:06:04 UTC 
Created attachment 1060166 [details]
File: dso_list
Comment 5 muteki 2015-08-07 05:06:05 UTC 
Created attachment 1060167 [details]
File: environ
Comment 6 muteki 2015-08-07 05:06:06 UTC 
Created attachment 1060168 [details]
File: limits
Comment 7 muteki 2015-08-07 05:06:07 UTC 
Created attachment 1060169 [details]
File: maps
Comment 8 muteki 2015-08-07 05:06:08 UTC 
Created attachment 1060170 [details]
File: mountinfo
Comment 9 muteki 2015-08-07 05:06:08 UTC 
Created attachment 1060171 [details]
File: namespaces
Comment 10 muteki 2015-08-07 05:06:09 UTC 
Created attachment 1060172 [details]
File: open_fds
Comment 11 muteki 2015-08-07 05:06:10 UTC 
Created attachment 1060173 [details]
File: proc_pid_status
Comment 12 Fedora End Of Life 2016-07-19 17:24:08 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.