Description of problem: I see this very often after login. Version-Release number of selected component: colord-1.1.2-1.fc20 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/libexec/colord crash_function: cd_icc_lcms2_error_cb executable: /usr/libexec/colord kernel: 3.11.2-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 996 Truncated backtrace: Thread no. 1 (10 frames) #0 cd_icc_lcms2_error_cb at cd-icc.c:171 #1 cmsSignalError at cmserr.c:411 #2 cmsCreateExtendedTransform at cmsxform.c:701 #3 cmsCreateMultiprofileTransformTHR at cmsxform.c:807 #4 cmsCreateTransformTHR at cmsxform.c:848 #5 cmsCreateTransform at cmsxform.c:858 #6 cd_profile_check_scum_dot at cd-icc.c:3685 #7 cd_icc_get_warnings at cd-icc.c:3987 #8 cd_profile_set_from_profile at cd-profile.c:915 #9 cd_profile_load_from_fd at cd-profile.c:1057
Created attachment 809136 [details] File: backtrace
Created attachment 809137 [details] File: cgroup
Created attachment 809138 [details] File: core_backtrace
Created attachment 809139 [details] File: dso_list
Created attachment 809140 [details] File: environ
Created attachment 809142 [details] File: exploitable
Created attachment 809143 [details] File: limits
Created attachment 809144 [details] File: maps
Created attachment 809145 [details] File: open_fds
Created attachment 809146 [details] File: proc_pid_status
Created attachment 809147 [details] File: var_log_messages
Proposing as Final blocker: "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop. " https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria#SELinux_and_crash_notifications
Does this still happen with colord >= 1.0.3?
Yes, I've just seen it with colord-1.1.3-1.fc20.
Discussed at 2013-11-13 blocker review meeting - http://meetbot.fedoraproject.org/fedora-blocker-review/2013-11-13/f20-final-blocker-review-1.2013-11-13-17.01.log.txt . Rejected as a blocker as it does not appear that this crash occurs during the stated periods (when running live, during live install, or immediately after install). Please re-propose if you can reliably reproduce it occurring during one of those times without unusual interaction.
commit 10060679ec9e1db116901e9e5462f7e371c7d795 Author: Richard Hughes <richard> Date: Thu Nov 14 14:28:36 2013 +0000 Use the threadsafe versions of the LCMS functions Fixes the other half of: https://bugzilla.redhat.com/show_bug.cgi?id=1016425 :100644 100644 1b634e5... 2c26182... M lib/colord/cd-icc-utils.c :100644 100644 73ecb4f... 6b18c8b... M lib/colord/cd-icc.c :100644 100644 1872d35... 01b9b7a... M lib/colord/cd-transform.c commit fe530b047e6cdfdce815e8c7258df321a60ffe06 Author: Richard Hughes <richard> Date: Thu Nov 14 14:20:18 2013 +0000 Reset the LCMS log handlers to default after use This ensures we don't call the function pointer and try to use a destroyed object. Fixes one half of https://bugzilla.redhat.com/show_bug.cgi?id=1016425 :100644 100644 1fe8ebf... 73ecb4f... M lib/colord/cd-icc.c :100644 100644 b4a2485... 1872d35... M lib/colord/cd-transform.c
colord-1.1.4-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/colord-1.1.4-1.fc20
Package colord-1.1.4-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing colord-1.1.4-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-21685/colord-1.1.4-1.fc20 then log in and leave karma (feedback).
colord-1.1.4-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.