Created attachment 549162 [details] DMESG Description of problem: The problem happening in every boot colord[2432] general protection ip:7f8c9165e421 sp:7fffaa5b67b0 error:0 in libsane-qcam.so.1.0.22[7f8c91658000+b000] Version-Release number of selected component (if applicable): kernel-3.1.5-6.fc16.x86_64 (using Xen) colord-0.1.15-1.fc16.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I am seeing this error on my Fedora 16 systems, colord-0.1.15-2: [17354.568848] colord[31900] general protection ip:b59134f8 sp:bfdf9f70 error:0 in libsane-qcam.so.1.0.22[b590d000+b000] Here's the backtrace: Program received signal SIGSEGV, Segmentation fault. 0xb6b334f8 in ?? () from /usr/lib/sane/libsane-qcam.so.1 (gdb) bt #0 0xb6b334f8 in ?? () from /usr/lib/sane/libsane-qcam.so.1 #1 0xb6b338fd in sane_qcam_init () from /usr/lib/sane/libsane-qcam.so.1 #2 0x46b0a583 in ?? () from /usr/lib/libsane.so.1 #3 0x46b0af9f in sane_dll_get_devices () from /usr/lib/libsane.so.1 #4 0x46af7c44 in sane_get_devices () from /usr/lib/libsane.so.1 #5 0x08057b82 in cd_sane_client_refresh () #6 0x0805af6f in ?? () #7 0x468a6f49 in ?? () from /lib/libgio-2.0.so.0 #8 0x468a706d in ?? () from /lib/libgio-2.0.so.0 #9 0x468a75df in ?? () from /lib/libgio-2.0.so.0 #10 0x4684d39f in g_simple_async_result_complete () from /lib/libgio-2.0.so.0 #11 0x4689e338 in ?? () from /lib/libgio-2.0.so.0 #12 0x4684d39f in g_simple_async_result_complete () from /lib/libgio-2.0.so.0 #13 0x4684d4cc in ?? () from /lib/libgio-2.0.so.0 #14 0x4650d471 in ?? () from /lib/libglib-2.0.so.0 #15 0x4651162f in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #16 0x46511d70 in ?? () from /lib/libglib-2.0.so.0 #17 0x465123a7 in g_main_loop_run () from /lib/libglib-2.0.so.0 #18 0x0804de44 in main () Running it with "-v" (verbose), I see the following messages before the segfault: 08:09:56 CdProfileStore: parsed new profile '/usr/share/color/icc/bluish.icc' 08:09:56 CdProfileStore: emit added (and changed): /usr/share/color/icc/bluish.icc 08:09:56 CdMain: Adding profile /org/freedesktop/ColorManager/profiles/icc_c94bbf6ef50ccdbb5b29d75b7007e77e 08:09:56 CdMain: Emitting ProfileAdded(/org/freedesktop/ColorManager/profiles/icc_c94bbf6ef50ccdbb5b29d75b7007e77e) 08:09:56 CdProfileStore: failed to open: Error opening directory '/usr/local/share/color/icc': No such file or directory 08:09:56 CdProfileStore: failed to open: Error opening directory '/Library/ColorSync/Profiles/Displays': No such file or directory 08:09:56 CdDeviceDb: get devices
Created attachment 581506 [details] colord abrt data Just want to add a me to with some data. Happens on boot always. My environment is a Xen domU like OP.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.