Bug 859656

Summary: [abrt] colord-0.1.23-1.fc17: __opendirat: Process /usr/libexec/colord-sane was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Steve Tyler <stephent98>
Component: colordAssignee: Richard Hughes <hughsient>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: amurik, hughsient, martinsp.bz, neilsbb, rhughes, zenomorph.ebe
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:ce05f32a59d763d46df4963f824b5c3ed8fb957e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-24 10:34:20 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: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: maps
none
File: dso_list
none
File: var_log_messages
none
File: open_fds none

Description Steve Tyler 2012-09-22 21:35:06 UTC 
Description of problem:
This happens while rebooting.

Version-Release number of selected component:
colord-0.1.23-1.fc17

Additional info:
libreport version: 2.0.13
abrt_version:   2.0.12
backtrace_rating: 4
cmdline:        /usr/libexec/colord-sane
crash_function: __opendirat
kernel:         3.5.4-1.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 __opendirat at ../sysdeps/unix/opendir.c
: #1 __opendir at ../sysdeps/unix/opendir.c
: #2 usbfs_get_device_list at os/linux_usbfs.c
: #3 op_get_device_list at os/linux_usbfs.c
: #4 libusb_get_device_list at core.c
: #5 musb_probe_devices at io/hpmud/musb.c
: #6 hpmud_probe_devices at io/hpmud/hpmud.c
: #7 DevDiscovery at scan/sane/hpaio.c
: #8 sane_hpaio_get_devices at scan/sane/hpaio.c
: #9 sane_dll_get_devices at dll.c
Comment 1 Steve Tyler 2012-09-22 21:35:09 UTC 
Created attachment 615914 [details]
File: core_backtrace
Comment 2 Steve Tyler 2012-09-22 21:35:10 UTC 
Created attachment 615915 [details]
File: environ
Comment 3 Steve Tyler 2012-09-22 21:35:12 UTC 
Created attachment 615916 [details]
File: limits
Comment 4 Steve Tyler 2012-09-22 21:35:13 UTC 
Created attachment 615917 [details]
File: backtrace
Comment 5 Steve Tyler 2012-09-22 21:35:15 UTC 
Created attachment 615918 [details]
File: cgroup
Comment 6 Steve Tyler 2012-09-22 21:35:16 UTC 
Created attachment 615919 [details]
File: maps
Comment 7 Steve Tyler 2012-09-22 21:35:18 UTC 
Created attachment 615920 [details]
File: dso_list
Comment 8 Steve Tyler 2012-09-22 21:35:20 UTC 
Created attachment 615921 [details]
File: var_log_messages
Comment 9 Steve Tyler 2012-09-22 21:35:21 UTC 
Created attachment 615922 [details]
File: open_fds
Comment 10 Steve Tyler 2012-09-22 21:42:41 UTC 
This was in an F17 VM running on an F17 host.

$ qemu-kvm -m 1024 -hda f17-test-1.img

qemu-kvm-1.0.1-1.fc17.x86_64
Comment 11 Steve Tyler 2012-09-23 03:50:28 UTC 
This happens while rebooting.
Running in a VM.


backtrace_rating: 4
Package: colord-0.1.22-2.fc18
OS Release: Fedora release 18 (Spherical Cow)
Comment 12 Pedro Martins 2012-11-02 11:34:17 UTC 
After updating, got this error. I had it previously but since I do not use a scanner (related to sane?) it didn't bother me; but seems to be recurring.

backtrace_rating: 4
Package: colord-0.1.23-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)
Comment 13 Matthew 2013-04-01 16:39:17 UTC 
I just started the system and logged into it, then the bug just appeared.

This is Fedoara 17, 64 bit running as a virtual machine on ESXi 5.1

backtrace_rating: 4
cmdline:        /usr/libexec/colord-sane
crash_function: __opendirat
executable:     /usr/libexec/colord-sane
kernel:         3.7.3-101.fc17.x86_64
package:        colord-0.1.23-1.fc17
reason:         Process /usr/libexec/colord-sane was killed by signal 11 (SIGSEGV)
uid:            996
ureports_counter: 1
Comment 14 Richard Hughes 2013-04-24 10:34:20 UTC 

*** This bug has been marked as a duplicate of bug 858714 ***