|
Bugzilla – Full Text Bug Listing |
| Summary: | Error while printing leaves queue in unusable state | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Michael Stather <kontakt> |
| Component: | Printing | Assignee: | Johannes Meixner <jsmeix> |
| Status: | RESOLVED WONTFIX | QA Contact: | Johannes Meixner <jsmeix> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | asklein, felix.rommel, jsmeix, vetter |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Deskjet 930C CUPS error log
Deskjet 930c messages |
||
|
Description
Michael Stather
2005-12-11 14:41:12 UTC
Same thing here with HP Deskjet 930c. But this error did not start with 10.0 but I think with 9.2. So this error is very old - please fix it. It is very annoying if I have always to remove my printer and reconfigure it! Have a look at Ubuntu - there you can open the program gnome-cups-manager and enable a disabled printer under the menu > "Printer" > "Resume printer..." without problems. I have attached the cups-error-log and messages. Created attachment 61766 [details]
Deskjet 930C CUPS error log
Created attachment 61767 [details]
Deskjet 930c messages
This is no bug. It works as it should. See the online "Administration Manual" or http://portal.suse.com/sdb/en/2004/05/jsmeix_print-cups-in-a-nutshell.html the section "The Backends" why works this way. For more details see http://www.easysw.com/cups/newsgroups.php?s5622+gcups.general+v5627 and http://www.easysw.com/cups/newsgroups.php?s5622+gcups.general+v5629 See the online "Administration Manual" or http://portal.suse.com/sdb/en/2003/09/jsmeix_print-einrichten-90.html what to do to set up a printer admin in CUPS. If you have only one USB printer, see http://www.cups.org/str.php?L1267 how to work around the problem. Thanks for the information. Is the fix only for USB printers or for all printers. If not you should add another way to re-enable the printer. Or do you think every user wants to read through the links you posted to me? IMHO this isn´t suitable for new users. Next major CUPS version (1.2.x) will solve it for all backends. If you have only one USB printer, see http://www.cups.org/str.php?L1267 how you can work around the problem now. By the way: For new users it is sufficient to read the "Disabled Queues" section in the administration manual. "By the way: For new users it is sufficient to read the "Disabled Queues" section in the administration manual." I haven't installed the handbook and can't find it in YaST software installer at the moment, but: There should be an easy way for reactivating disabled printers - and the problem is that it does not work in an easy way. Why does it work in Ubuntu Breezy and not in SUSE? In Ubuntu you can enable a disabled printer with 2 clicks - one on the printer icon in systray and the other click on the menu point. I think they use about the same CUPS version as SUSE!? "If you have only one USB printer, see http://www.cups.org/str.php?L1267 how you can work around the problem now." No, not the user should fix such problems but the software provider. OK, SUSE can be downloaded for free - what is superb - but there are people who pay for a boxed SUSE version and they want SW which does it's job without "work around" the problem. I enabled a disabled printer with running kcmshell printmgr as ROOT! So why can't you manage it to let people activate their printer with this KDE control center module without getting root and calling it on command line? See comment #6 Feel free to file an enhancement request to let KDE or Gnome run "/usr/bin/enable" as setuid root and it will be immediately rejected because in business environment you won't allow any user to re-enable queues which have been disabled intentionally by the administrator. Have in mind that Suse Linux and related products do not only run in trusted stand-alone single-user environments but also in business networks where different security conditions must be fulfilled. CUPS 1.2 is released, which should solve the problem. http://www.cups.org/str.php?L1267 Will there be an update for SL10.1/SLES10? CUPS 1.2 has several incompatibilities to CUPS 1.1.x so that there will be no update for Suse Linux 10.1. I don't know what might happen for SLES10 in the future. mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED. In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;( |