Bug 109491
Summary: | users unable to print with configured printer until printconf-gui or tui run and printer edited after each boot | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andy Green <andy> |
Component: | redhat-config-printer | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-01-25 14:52:10 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
Andy Green
2003-11-08 14:48:18 UTC
Does 'printconf-backend' (as root) have the same effect as editing and applying changes? How about 'printconf-backend --force-rebuild'? No, running printconf-backend with or without the --force-rebuild switch does not improve the situation. However, I did this over ssh running the utils from the commandline, I noticed this: [root@nicecat root]# gnome-print-manager lpstat: Unable to connect to server: Connection refused This set me thinking, it seems that on this machine in some distant past time of struggle I disabled cupsd. I found that running cupsd from the commandline DOES have the same effect as the edit in printconf. Although this is clearly 'operator error', maybe if gnome-print-manager is prepared to spawn printconf-gui when there are no printers, one or the other should check to see if cupsd is running (wasn't there a change to cups in Fedora?) and prompt the operator/idiot who disabled it with a specific warning? Yes, maybe. |