Bug 917383 - [abrt] colord-0.1.28-1.fc18: standard_free: Process /usr/libexec/colord was killed by signal 6 (SIGABRT) [NEEDINFO]
Summary: [abrt] colord-0.1.28-1.fc18: standard_free: Process /usr/libexec/colord was k...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: colord
Version: 18
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:42072bddd730fbed737730fff58...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-03 20:03 UTC by Jorge Catumba
Modified: 2022-12-11 02:51 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-10-30 15:43:17 UTC
Type: ---
Embargoed:
rhughes: needinfo?

Attachments (Terms of Use)
File: backtrace (11.53 KB, text/plain)
2013-03-03 20:03 UTC, Jorge Catumba 		no flags Details
File: build_ids (1.36 KB, text/plain)
2013-03-03 20:03 UTC, Jorge Catumba 		no flags Details
File: cgroup (158 bytes, text/plain)
2013-03-03 20:03 UTC, Jorge Catumba 		no flags Details
File: dso_list (3.34 KB, text/plain)
2013-03-03 20:03 UTC, Jorge Catumba 		no flags Details
File: environ (184 bytes, text/plain)
2013-03-03 20:03 UTC, Jorge Catumba 		no flags Details
File: limits (1.29 KB, text/plain)
2013-03-03 20:03 UTC, Jorge Catumba 		no flags Details
File: maps (10.23 KB, text/plain)
2013-03-03 20:03 UTC, Jorge Catumba 		no flags Details
File: open_fds (1.42 KB, text/plain)
2013-03-03 20:03 UTC, Jorge Catumba 		no flags Details
File: proc_pid_status (773 bytes, text/plain)
2013-03-03 20:03 UTC, Jorge Catumba 		no flags Details
File: var_log_messages (11.09 KB, text/plain)
2013-03-03 20:03 UTC, Jorge Catumba 		no flags Details
View All

Description Jorge Catumba 2013-03-03 20:03:10 UTC 
Version-Release number of selected component:
colord-0.1.28-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/colord
core_backtrace: 
crash_function: standard_free
executable:     /usr/libexec/colord
kernel:         3.8.1-201.fc18.i686
uid:            997

Truncated backtrace:
Thread no. 1 (10 frames)
 #6 standard_free at gmem.c:98
 #8 cd_inhibit_item_free at cd-inhibit.c:96
 #9 g_ptr_array_remove_index at garray.c:1162
 #10 g_ptr_array_remove at garray.c:1290
 #11 cd_inhibit_remove at cd-inhibit.c:146
 #12 cd_inhibit_name_vanished_cb at cd-inhibit.c:171
 #13 actually_do_call at gdbusnamewatching.c:164
 #14 do_call at gdbusnamewatching.c:216
 #15 call_vanished_handler at gdbusnamewatching.c:242
 #17 on_name_owner_changed at gdbusnamewatching.c:307
Comment 1 Jorge Catumba 2013-03-03 20:03:12 UTC 
Created attachment 704614 [details]
File: backtrace
Comment 2 Jorge Catumba 2013-03-03 20:03:15 UTC 
Created attachment 704615 [details]
File: build_ids
Comment 3 Jorge Catumba 2013-03-03 20:03:17 UTC 
Created attachment 704616 [details]
File: cgroup
Comment 4 Jorge Catumba 2013-03-03 20:03:19 UTC 
Created attachment 704617 [details]
File: dso_list
Comment 5 Jorge Catumba 2013-03-03 20:03:21 UTC 
Created attachment 704618 [details]
File: environ
Comment 6 Jorge Catumba 2013-03-03 20:03:23 UTC 
Created attachment 704619 [details]
File: limits
Comment 7 Jorge Catumba 2013-03-03 20:03:25 UTC 
Created attachment 704620 [details]
File: maps
Comment 8 Jorge Catumba 2013-03-03 20:03:27 UTC 
Created attachment 704621 [details]
File: open_fds
Comment 9 Jorge Catumba 2013-03-03 20:03:29 UTC 
Created attachment 704622 [details]
File: proc_pid_status
Comment 10 Jorge Catumba 2013-03-03 20:03:31 UTC 
Created attachment 704623 [details]
File: var_log_messages
Comment 11 Richard Hughes 2013-04-24 10:40:07 UTC 
I can't see how this crash is possible. Has it ever happened before? Is the hardware that this bug was generated on been tested for possible RAM problems?
Note You need to log in before you can comment on or make changes to this bug.