abrt 1.0.9 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: gcm-apply component: gnome-color-manager executable: /usr/bin/gcm-apply global_uuid: baced551f6d6d75f99fc3c51a1169a902edde84d kernel: 2.6.33.2-57.fc13.x86_64 package: gnome-color-manager-2.30.1-1.fc13 rating: 4 reason: Process /usr/bin/gcm-apply was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) How to reproduce ----- 1. Login to desktop on a fully up-to-date F13 system
Created attachment 409797 [details] File: backtrace
This may be related to bug 588295 perhaps?
I'm not sure if this plays into it, but what scanner type do you use?
(In reply to comment #3) > I'm not sure if this plays into it, but what scanner type do you use? I don't have a scanner, or attached printer.
(In reply to comment #4) > (In reply to comment #3) > > I'm not sure if this plays into it, but what scanner type do you use? > > I don't have a scanner, or attached printer. Now you're puzzling me... do you have any USB devices that aren't scanners but fall into the realm of "image acquisition"? Some SANE backend drivers access attached webcams, (gphoto-supported) digital cameras, ... Anyway: I've submitted a testing update for F-13 of the new upstream bugfix release 1.0.21, can you please check if the issue remains with this version? Thanks.
https://admin.fedoraproject.org/updates/system-config-users-1.2.97-1.fc13
(In reply to comment #5) > Now you're puzzling me... do you have any USB devices that aren't scanners but > fall into the realm of "image acquisition"? Some SANE backend drivers access > attached webcams, (gphoto-supported) digital cameras, ... I have a USB hub attached which connects to * a powered off USB drive * a USB mouse and USB keyboard * a USB extension cable with nothing plugged in Additional system information available at http://www.smolts.org/client/show/pub_823003ff-1b58-48ec-8b87-07fd9fea453e > Anyway: I've submitted a testing update for F-13 of the new upstream bugfix > release 1.0.21, can you please check if the issue remains with this version? Thanks! I'm using that update, and do not appear to be seeing the reported problem.
Argh, obviously: https://admin.fedoraproject.org/updates/sane-backends-1.0.21-1.fc13
sane-backends-1.0.21-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/sane-backends-1.0.21-1.fc13
sane-backends-1.0.21-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update sane-backends'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/sane-backends-1.0.21-1.fc13
sane-backends-1.0.21-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.