|
Bugzilla – Full Text Bug Listing |
| Summary: | CUPS hp backend + hplip service versus SANE hpoj backend | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Johannes Meixner <jsmeix> |
| Component: | Printing | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED FIXED | QA Contact: | Johannes Meixner <jsmeix> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | jsmeix |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Johannes Meixner
2005-09-08 15:12:30 UTC
move to later reopened 1 - I think just information will be enought at the end. hplip service will be run only when hp:// backend is using. There can be warrning or information when hp backend is selecting (#175323) Already fixed 2 - please be more verbose or open another bug for this. I couldn't provide installation today, cups is stopped when hp:// is using or everytime? 1 - What I mean is that the user has the possibility to decide that the hplip services are not started. Therefore it is o.k. when there is a information when the user selected the hp backend (bug #175323) so that the user can go back and select another backend if he doesn't want the hplip services. 2 - I talked about what happened during installation. If I remember correctly the following happened: Near the end of the installation after the hardware setup, the cupsd was stopped. I don't know why it was stopped or what it stopped (perhaps YaST2-printer?). If I remeber correctly the cupsd was re-started at the very end of the installation when the runlevel 5 (or 3) is reached. The problem which I described happens only when the the YaST scanner config is started (via YaST control center) after the cupsd was stopped but before it was re-started again. For me it makes no sense to stop and re-start it. Therefore I suggest to simply keep it running (except the user has explicitely selected in YaST2-printer during hardware setup that it should be stopped - e.g. for a "client-only" setup). 1 - fixed 2 - I will check this, but make separate report, please 2 is seperated bug 203207. thanks |