Bug 1006920

Summary: [abrt] gnome-settings-daemon-3.9.91.1-1.fc20: gcm_session_client_connect_cb: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Martin <mholec>
Component: colordAssignee: Richard Hughes <rhughes>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: bnocera, marciosr10, mclasen, mkasik, mmarhefk, ofourdan, rhughes, rstrode, tiagomatos, tpelka
Target Milestone: ---Keywords: Reopened
Target Release: ---Flags: rhughes: needinfo? (mholec)
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:45e2a13a80d8ba79445cab1a96ae7a8fdcfef081
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 00:41:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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
gnome-settings-daemon stdout none

Description Martin 2013-09-11 13:54:07 UTC
Version-Release number of selected component:
gnome-settings-daemon-3.9.91.1-1.fc20

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-settings-daemon
crash_function: gcm_session_client_connect_cb
executable:     /usr/libexec/gnome-settings-daemon
kernel:         3.12.0-0.rc0.git16.2.fc21.x86_64
runlevel:       unknown
uid:            1000

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 gcm_session_client_connect_cb at gsd-color-profiles.c:85
 #1 g_simple_async_result_complete at gsimpleasyncresult.c:777
 #2 complete_in_idle_cb at gsimpleasyncresult.c:789
 #7 gtk_main at gtkmain.c:1157

Comment 1 Martin 2013-09-11 13:54:17 UTC
Created attachment 796386 [details]
File: backtrace

Comment 2 Martin 2013-09-11 13:54:21 UTC
Created attachment 796387 [details]
File: cgroup

Comment 3 Martin 2013-09-11 13:54:25 UTC
Created attachment 796388 [details]
File: core_backtrace

Comment 4 Martin 2013-09-11 13:54:29 UTC
Created attachment 796389 [details]
File: dso_list

Comment 5 Martin 2013-09-11 13:54:33 UTC
Created attachment 796390 [details]
File: environ

Comment 6 Martin 2013-09-11 13:54:37 UTC
Created attachment 796391 [details]
File: exploitable

Comment 7 Martin 2013-09-11 13:54:42 UTC
Created attachment 796392 [details]
File: limits

Comment 8 Martin 2013-09-11 13:54:48 UTC
Created attachment 796393 [details]
File: maps

Comment 9 Martin 2013-09-11 13:55:00 UTC
Created attachment 796395 [details]
File: open_fds

Comment 10 Martin 2013-09-11 13:55:05 UTC
Created attachment 796396 [details]
File: proc_pid_status

Comment 11 Martin 2013-09-11 13:55:09 UTC
Created attachment 796397 [details]
File: var_log_messages

Comment 12 Richard Hughes 2013-09-19 12:58:04 UTC
Okay, I've traced through all the code and can't see anything that looks wrong. Can you reproduce this? If so, can you get me a log of:

killall gnome-settings-daemon
killall gnome-settings-daemon
killall gnome-settings-daemon
/usr/libexec/gnome-settings-daemon --debug

Thanks!

Richard.

Comment 13 Matus Marhefka 2013-10-29 17:30:30 UTC
I reproduced the same problem on Fedora 20.

Package:
gnome-settings-daemon-3.10.1-2.fc20.x86_64


Stderr of /usr/libexec/gnome-settings-daemon returns:

$ /usr/libexec/gnome-settings-daemon --debug
(gnome-settings-daemon:3586): smartcard-plugin-WARNING **: smartcard event function failed.

(gnome-settings-daemon:3586): libcolord-CRITICAL **: cd_icc_load_data: assertion 'data_len != 0' failed
Segmentation fault (core dumped)

Comment 14 Matus Marhefka 2013-10-29 17:31:33 UTC
Created attachment 817146 [details]
gnome-settings-daemon stdout

Comment 15 Matus Marhefka 2013-10-29 17:32:21 UTC
gnome-settings-daemon stdout file contains stdout from command /usr/libexec/gnome-settings-daemon --debug

Comment 16 Matthias Clasen 2014-01-03 04:24:42 UTC
> gnome-settings-daemon:3586): libcolord-CRITICAL **: cd_icc_load_data: assertion 'data_len != 0' failed
> Segmentation fault (core dumped)

This should be fixed in colord with
https://github.com/hughsie/colord/commit/7946c7cfe5047beb252be73d98c34f29db85fad1
in 1.1.5

Which version of colord do you have ?

Comment 18 Fedora End Of Life 2015-05-29 09:23: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 19 Fedora End Of Life 2015-06-30 00:41:55 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.