Bug 228184
Summary: | Printing not working; hal failed | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Gantry York <gantrix> | ||||
Component: | hal-cups-utils | Assignee: | Tim Waugh <twaugh> | ||||
Status: | CLOSED WORKSFORME | QA Contact: | |||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 6 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2007-02-13 09:20:43 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
Gantry York
2007-02-11 04:43:55 UTC
Firstly, what does 'rpm -q hal-cups-utils cups' say?
Next, please do the following, as root:
Stop CUPS:
/sbin/service cups start
Edit /etc/cups/cupsd.conf and change the 'LogLevel' line to read:
LogLevel debug2
Clear out the error_log file:
>/var/log/cups/error_log
Start CUPS:
/sbin/service cups start
Now try to print something, and when it fails and you see the 'hal failed'
message, attach the /var/log/cups/error_log file here. Thanks.
Created attachment 147861 [details]
cups error_log as requested
[root@denali gantry]# rpm -q hal-cups-utils cups hal-cups-utils-0.6.5-1.fc6 cups-1.2.7-1.8.fc6 Sounds like the printer queue is disabled. When you run the config tool (System->Administration->Printing) and click on the queue name, does the 'Enabled' check-box have a check mark in it? If not, please click the box so the queue is enabled, and click 'Apply' to make that change. If you then wait for a moment and click the 'Refresh' button (near the top of the window), does the queue become disabled again? If so, I'd like you to attach the error_log file again. Thanks. Yes, you are correct. It now works. Is it possible that an updated changed my print queue configuration? Thanks for your help. You are welcome to close out this bug. I think this might have been a temporary hal problem (see bug #227444 for a similar report). |