Bug 161017

Summary: SMB Shares are not creatable by gnome-config-printer
Product: [Fedora] Fedora Reporter: Matthew A. R. Sherian <mars>
Component: system-config-printerAssignee: Tim Waugh <twaugh>
Status: CLOSED WORKSFORME QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4   
Target Milestone: ---   
Target Release: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-07-04 08:02:41 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
CUPS manages the remote printer
none
Both printers configured with cups, produces the bug condition none

Description Matthew A. R. Sherian 2005-06-19 21:28:21 UTC 
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
Comment 1 Tim Waugh 2005-06-28 15:54:48 UTC 
Please attach the output of 'printconf-tui --Xexport' at that point, taking care
to replace any passwords it may contain with *s.
Comment 2 Matthew A. R. Sherian 2005-06-30 23:25:12 UTC 
Created attachment 116196 [details]
CUPS manages the remote printer

The config with CUPS having the LaserJet printer config, and printtool managing
a localprinter.
Comment 3 Matthew A. R. Sherian 2005-06-30 23:26:29 UTC 
Created attachment 116197 [details]
Both printers configured with cups, produces the bug condition

This is the configuration that produces the bug.
Comment 4 Tim Waugh 2005-07-01 08:17:25 UTC 
With the configuration from attachment #116197 [details], what does 'lpstat -s' say?
Comment 5 Matthew A. R. Sherian 2005-07-02 02:27:51 UTC 
[mars@mars-new ~]$ lpstat -s
system default destination: hp7350
device for hp7350: usb:/dev/usb/lp0
Comment 6 Tim Waugh 2005-07-03 09:32:07 UTC 
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?
Comment 7 Matthew A. R. Sherian 2005-07-04 04:09:54 UTC 
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.