Bug 917526

Summary: [abrt] colord-0.1.23-1.fc17: cd_main_create_profile: Process /usr/libexec/colord was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: daineka
Component: colordAssignee: Richard Hughes <rhughes>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: 6663bcdbe265d507c8d8cd7d8898d05c8d0c2a93, altbinspam, beckfr, bill-bugzilla.redhat.com, b.thielman, giudeluca88, hebert.soares, joe, rhughes, tecnosoluciones.gm, wisekaa03
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:785dcbaf76a8f5a6db9c86391e2ff821bdd3553d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 18:04:41 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: build_ids
none
File: cgroup
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: smolt_data
none
File: var_log_messages none

Description daineka 2013-03-04 09:34:30 UTC 
Version-Release number of selected component:
colord-0.1.23-1.fc17

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/colord
core_backtrace: 
crash_function: cd_main_create_profile
executable:     /usr/libexec/colord
kernel:         3.7.9-104.fc17.i686.PAE
uid:            996

Truncated backtrace:
Thread no. 1 (3 frames)
 #5 cd_main_create_profile at cd-main.c:205
 #6 cd_main_daemon_method_call at cd-main.c:1165
 #7 call_in_idle_cb at gdbusconnection.c:4687

Potential duplicate: bug 705005
Comment 1 daineka 2013-03-04 09:34:33 UTC 
Created attachment 704828 [details]
File: backtrace
Comment 2 daineka 2013-03-04 09:34:35 UTC 
Created attachment 704829 [details]
File: build_ids
Comment 3 daineka 2013-03-04 09:34:37 UTC 
Created attachment 704830 [details]
File: cgroup
Comment 4 daineka 2013-03-04 09:34:39 UTC 
Created attachment 704831 [details]
File: dso_list
Comment 5 daineka 2013-03-04 09:34:41 UTC 
Created attachment 704832 [details]
File: environ
Comment 6 daineka 2013-03-04 09:34:43 UTC 
Created attachment 704833 [details]
File: limits
Comment 7 daineka 2013-03-04 09:34:45 UTC 
Created attachment 704834 [details]
File: maps
Comment 8 daineka 2013-03-04 09:34:47 UTC 
Created attachment 704835 [details]
File: open_fds
Comment 9 daineka 2013-03-04 09:34:49 UTC 
Created attachment 704836 [details]
File: proc_pid_status
Comment 10 daineka 2013-03-04 09:34:51 UTC 
Created attachment 704837 [details]
File: smolt_data
Comment 11 daineka 2013-03-04 09:34:53 UTC 
Created attachment 704838 [details]
File: var_log_messages
Comment 12 Bill McGonigle 2013-03-14 19:22:10 UTC 
Attached new printer (Epson R22 via USB) and it crashed.

backtrace_rating: 4
Package: colord-0.1.23-1.fc17
Architecture: x86_64
OS Release: Fedora release 17 (Beefy Miracle)
Comment 13 Joe Zeff 2013-04-05 06:29:19 UTC 
I was adding my printer to CUPS after re-installing Fedora 17 when this happened.

backtrace_rating: 4
cmdline:        /usr/libexec/colord
core_backtrace: 
crash_function: cd_main_create_profile
executable:     /usr/libexec/colord
kernel:         3.8.4-102.fc17.i686.PAE
package:        colord-0.1.23-1.fc17
reason:         Process /usr/libexec/colord was killed by signal 6 (SIGABRT)
uid:            997
ureports_counter: 1
Comment 14 Hebert Silva 2013-04-13 20:56:37 UTC 
crashed while installing an epson printer driver

backtrace_rating: 4
cmdline:        /usr/libexec/colord
core_backtrace: 
crash_function: cd_main_create_profile
executable:     /usr/libexec/colord
kernel:         3.8.4-102.fc17.i686.PAE
package:        colord-0.1.23-1.fc17
reason:         Process /usr/libexec/colord was killed by signal 6 (SIGABRT)
uid:            995
ureports_counter: 1
Comment 15 Richard Hughes 2013-04-22 11:44:55 UTC 
Can anyone reproduce this on Fedora 18 or Fedora 19? I think the crash was fixed by:

commit b3f7557d27c2542006c6c6bc2d1b8175dd112b16
Author: Christopher James Halse Rogers <raof>
Date:   Fri Aug 31 13:23:32 2012 +1000

    Initialise global connection variable earlier.
    
    Under some circumstances the on_name_acquired handling is done on
    an idle callback, and it's always done asynchronously, after the
    dbus name has been acquired. Thus there is a race between another
    dbus client noticing colord has acquired its name and the
    on_name_acquired callback being fired. If a client makes a dbus
    request in this time, connection will be NULL, and colord will
    die with an assertion.
    
    Moving the setting of connection to on_bus_acquired removes this
    race because the dbus objects are only registered later in
    on_bus_acquired.
Comment 16 Sherman 2013-06-14 05:10:33 UTC 
the problem occur after install the last updates in my notebook

backtrace_rating: 4
cmdline:        /usr/libexec/colord
core_backtrace: 
crash_function: cd_main_create_profile
executable:     /usr/libexec/colord
kernel:         3.6.11-5.fc17.i686
package:        colord-0.1.23-1.fc17
reason:         Process /usr/libexec/colord was killed by signal 6 (SIGABRT)
reported_to:    uReport: BTHASH=db7193c656f306f112ca77634d30a9ce00ca67c6
runlevel:       unknown
uid:            998
ureports_counter: 1
Comment 17 Fedora End Of Life 2013-07-04 06:29:46 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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 18 Fedora End Of Life 2013-08-01 18:04:46 UTC 
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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