Bug 115370
Summary: | CUPS crashes during runtime | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jason Straw <bugs> |
Component: | cups | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 1 | CC: | david, marius.andreiana |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 1.1.23 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-08-20 07:59:46 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: |
Description
Jason Straw
2004-02-11 16:20:06 UTC
Apply the test updates for redhat-config-printer: http://www.redhat.com/archives/fedora-test-list/2004-February/msg00231.html Does the problem still occur after doing that? Same problem for me - random crashes which leave nothing in the logs. However this is with Red Hat 9. I'm compiling the Fedora RPM (without DBUS) to see if the problem goes away with this. David: if there is nothing in the logs, it is a *different* problem. Or do you see the 'Unable to bind socket' message? Sorry - you're right, different problem. It just dies, and logs nothing in /var/log/cups/* or /var/log/messages. No pattern to it as far as I can see. All clients are using CUPS or Adobe postscript drivers. I won't bother to file a new bug if the Fedora RPM works. The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there haven't been any updates to the report in quite a long time now after we've requested additional information, we're assuming the problem is either no longer present in our current OS release, or that there is no longer any interest in tracking the problem. Setting status to "CURRENTRELEASE", however if you still experience this problem after updating to our latest Fedora Core release and are still interested in Red Hat tracking the issue, and assisting in troubleshooting the problem, please feel free to provide the information requested above, and reopen the report. Thanks in advance. |