Bug 131573
| Summary: | cups-config-daemon refuses to start | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Daniel Malmgren <dm> |
| Component: | hal | Assignee: | John (J5) Palmieri <johnp> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | jkeck |
| 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: | 2004-09-03 17:28:34 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: | 123268 | ||
|
Description
Daniel Malmgren
2004-09-02 13:34:26 UTC
Fixed this one by changing some "deny" to "allow" in /etc/dbus-1/system.d/cups-config-daemon-dbus.conf. Guess something is wrong here by default. Should be 'hal-cups-utils', but there is no bugzilla component for it. Oh, so it's hal related. Wouldn't have been my first guess. I might note then that I'm running latest (0.2.97.cvs20040901-1) version of hal as well. This should not have any bearing on printing. It only configure cups when we can't auto-detect the printer and only on the first time it asks you to pick a driver. Every other time it will get your configuration from gconf. Since it does not have to wait fo a user to reply the daemon is not needed. So in other words the daemon is just used for first time configuration of printer models that are unknown to us. > This should not have any bearing on printing.
No, I find out there were other reasons why my printing didn't work.
btw, does this mean that this daemon only needs to be started when
installing new printers?
Since printers can be installed at any time (simply plug in a USB printer) we can't know when to start it so it needs to run. Eventually it will become a system policy daemon which will handle a number of similar session to system requests and only load modules when their signals come in over D-BUS. Fell free to have the service not load if you wish. It just means that for any new printer that our database can not configure you will have to plug it in, configure it, unplug it and plug it back in again. I would like to know why your service wasn't starting up though. Every machine I have tested on the policy rules have worked. Are you at the latest rawhide version? If not can you get the latest version of hal-cups-utils and then do (as root): service cups-config-daemon stop cups-config-daemon --daemon=no and tell me if you still get the same problem. I'm sorry, but I can't seem to reproduce it today. Don't know if it's today's update or what, but a simple "service cups-config-daemon start" works perfectly today. Guess I'll just mark it as WORKSFORME... |