Bug 474190

Summary: No printing with my Samsung ML-1610
Product: [Fedora] Fedora Reporter: antonio montagnani <antonio.montagnani>
Component: cupsAssignee: Tim Waugh <twaugh>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: Printer error in rawhide
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-12-17 17:19:00 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:
Attachments:
Description Flags
log of Page-print-Test none

Description antonio montagnani 2008-12-02 18:02:14 UTC 
Description of problem:
I switched from F10 to rawhide and now I cannot print on my laser printer

Version-Release number of selected component (if applicable):
cups-1.4-0.b1.4.fc11.i386

How reproducible:
always

Steps to Reproduce:
1.print any document
2.
3.
  
Actual results:
no printing

Expected results:
it should print

Additional info:
I disinstalled and re-installed printer but I get an error also during page print Test : client-error-not-found during operation Cups
Comment 1 antonio montagnani 2008-12-03 08:41:29 UTC 
Created attachment 325499 [details]
log of Page-print-Test

this is the output of errors in cups when I carry a page print Test in system-config-printers
Comment 2 Tim Waugh 2008-12-03 11:09:53 UTC 
Please try the troubleshooter: Help->Troubleshoot from the menu.
Comment 3 antonio montagnani 2008-12-03 13:02:40 UTC 
I re-booted this morning and now I can print from applications and also fron networked boxes (even if OOcalc crashed, but I think that is a separate issue) but I get the error message on Page-Print-Test in System-config-printer.
Therefore I switched to low priority.
Comment 4 Tim Waugh 2008-12-17 17:19:00 UTC 

*** This bug has been marked as a duplicate of bug 476612 ***