Description of problem: If the end user creates a printer that is accessed VIA SMB, the printer is in accessible. Version-Release number of selected component (if applicable): cups-1.1.23-15 system-config-printer-0.6.131-1 How reproducible: Unknown, could be unique to one system. Steps to Reproduce: 1. Click Desktop->System Settings->Printing 2. Select New 3. Enter the printer name; Next! 4. Select SMB 5. Specify the Connection information 6. Attempt to print a test page. Actual results: There was a problem sending CUPS test page to 'Laserjet1150' queue: lpr: error - unable to print file: client-error-not-found Expected results: Additional info: If one adds the printer via http://localhost:631/ [Cups Web admin] it is successful
Please attach the output of 'printconf-tui --Xexport' at that point, taking care to replace any passwords it may contain with *s.
Created attachment 116196 [details] CUPS manages the remote printer The config with CUPS having the LaserJet printer config, and printtool managing a localprinter.
Created attachment 116197 [details] Both printers configured with cups, produces the bug condition This is the configuration that produces the bug.
With the configuration from attachment #116197 [details], what does 'lpstat -s' say?
[mars@mars-new ~]$ lpstat -s system default destination: hp7350 device for hp7350: usb:/dev/usb/lp0
Still keeping the same configuration, what about when you run '/usr/sbin/printconf-backend --force-rebuild' and then 'service cups restart' -- is the 'lpstat -s' output the same?
the printconf-backend force rebuild was performed, but I had the printer configured via cups. I then went and removed the printer from cups, reran the printconf-backend fore rebuild command, then added the printer via the gui, and it was successful. The printer now shows up in CUPS config, and in the GNOME Print configurator.