Description of problem: on boot Version-Release number of selected component: colord-1.0.1-1.fc20 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/colord crash_function: cmsDictAddEntry executable: /usr/libexec/colord kernel: 3.10.0-0.rc5.git0.1.fc20.x86_64 runlevel: unknown uid: 996 var_log_messages: Fichier binaire /var/log/messages concordant Truncated backtrace: Thread no. 1 (10 frames) #4 cmsDictAddEntry at cmsnamed.c:868 #5 Type_Dictionary_Read at cmstypes.c:5092 #6 cmsReadTag at cmsio0.c:1424 #7 cd_icc_load at cd-icc.c:773 #8 cd_icc_load_data at cd-icc.c:873 #9 cd_icc_load_file at cd-icc.c:1488 #10 cd_profile_set_filename at cd-profile.c:1098 #11 cd_profile_store_add_profile at cd-profile-store.c:222 #12 cd_profile_store_search_path at cd-profile-store.c:338 #15 cd_profile_store_search at cd-profile-store.c:575
Created attachment 762348 [details] File: backtrace
Created attachment 762349 [details] File: cgroup
Created attachment 762350 [details] File: core_backtrace
Created attachment 762351 [details] File: dso_list
Created attachment 762352 [details] File: environ
Created attachment 762353 [details] File: limits
Created attachment 762354 [details] File: maps
Created attachment 762355 [details] File: open_fds
Created attachment 762356 [details] File: proc_pid_status
I reported this upstream a little while ago[1], but I think it's some kind of Gio bug as I can't reproduce it without using the Gio loader stuff. [1] http://www.mail-archive.com/lcms-user@lists.sourceforge.net/msg03648.html
Also, does this happen on every boot or it just happened the once?
It started happening on every boot lately. This is an old continuously updated system, so it is quite possible it's finding data saved by older software versions.
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
I'm pretty sure the last lcms2 update should have fixed this.