Custom Query (29 matches)
Results (16 - 18 of 29)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1 | fixed | Importing into SVN | ||
Description |
Initial import of code in SVN |
|||
#23 | fixed | HP LaserJet Professional P1606dn and lpd | ||
Description |
Because HPLIP is not working with my printer (See ticket 15), I try foomatic from "cups-filters-1.0.61-os2-20141011.zip" with Cups 1.4.8 (eCS 2.2 beta 2). Driver: HP LaserJet? Pro P1606dn Foomatic/foo2zjs-z2 (recommended) (grayscale, 2-sided printing) Connection: lpd://192.168.2.101/lp1 If I send a testpage, the printer seems to get data (lights blinking), put no output comes. I think no other protocol (ipp / HP / Socket) works with my printer. Connected to the printer via Firefox: "SLP-config., LPD-Print and WS-Discovery" are all checked. Any idea, what to do? Any other protokoll I should try? If so, which syntax? |
|||
#14 | fixed | HP DeskJet 3052A | ||
Description |
Alex Taylor suggested I open a ticket on this problem. This is a USB Port device. Using the attached PPD file, its print quality would be characterized as Good or Very Good. The problem is that after the print job is completed CPU Usage spikes to 99.9%; during the print job there is no spike. Opening the CUPS Administration page in Firefox shows the following, under the respective tabs, after the print job: Jobs State "No %%BoundingBox?: comment in header!" Printers Status Processing - "Processing page x..." The page number mentioned is always the number 1 greater than the last page of the document. Ergo, it is what I would characterize as an imaginary page. Using the C-A-D utility after the spike starts, and then List shows CUPSD.EXE CUPSD.EXE USB.EXE Killing both instances of CUPSD.EXE does not eliminate the spike. Repeated attempts to kill USB.EXE always fails. Using the Run TOP tool of the C-A-D utility shows that it is USB.EXE that causes the spike. A reboot, after CUPSD.EXE is killed, solves the spike. If they are not killed, it is necessary to go to the CUPS Administration page and then Jobs to cancel the print job; otherwise the job will continue to print over-and-over until cancelled despite the reboots. I understand from Alex that Paul is trying to address the problem w/ USB printers. he also suggested the possibility of me trying to network the printer instead. I could try I suppose but it would be inconvenient because of the physical setup (the cable being in a walkway in that event), and still possibly presenting the same issue as the other computer would necessarily be connected to the printer by the USB Port. |