Bug 713875
Summary: | GPF in libsane-qcam.so.1.0.22 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jerry James <loganjerry> |
Component: | abrt | Assignee: | abrt <abrt-devel-list> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | anton, dvlasenk, iprikryl, jmoskovc, kklic, mmilata, mtoman, npajkovs, nphilipp |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-05-17 12:42:06 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: | |||
Bug Depends On: | |||
Bug Blocks: | 744774 |
Description
Jerry James
2011-06-16 16:23:41 UTC
Changing component to abrt temporarily -- I need a backtrace to debug that. is colord run under user who is logging into the session or it's run under some system account (like gdm?) if the second case, then you need to run ABRT as user who was running the application to see the actual crash - if you run it as root, you should see all crashes. It's been long enough that my Rawhide machine has changed a lot. I don't see these messages about colord in the logs anymore. In any case, colord is run as root. But I don't think there's any possibility of figuring this out now, since there's no way to reproduce the problem. Does this still happen? I guess it was caused by unsigned packages in F16 while it was rawhide. No, as I said in comment 3, I cannot reproduce this behavior any more. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Seems like this one is fixed. Please re-open this ticket if you hit the problem again. |