Bug 722195 - System-config-printer fails to add a shared printer (via SMB) and gives a very cryptic error message
Summary: System-config-printer fails to add a shared printer (via SMB) and gives a ver...
Keywords:
Status: CLOSED DUPLICATE of bug 526081
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-printer
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-14 15:32 UTC by Tadej Janež
Modified: 2011-07-15 08:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-15 08:11:59 UTC
Type: ---


Attachments (Terms of Use)

Description Tadej Janež 2011-07-14 15:32:53 UTC
Description of problem:
Today I spent an hour trying to add a shared printer on a Windows machine to my F-15 laptop.

System-config-printer was giving me this cryptic error message:

"CUPS server error

There was an error during the CUPS operation: 'client-error-not-possible'."

Looking at the /var/log/cups/error_log file, it revealed more details:
"D [14/Jul/2011:17:07:13 +0200] CUPS-Add-Modify-Printer client-error-not-possible: Bad device-uri scheme "smb"!
E [14/Jul/2011:17:07:13 +0200] Returning IPP client-error-not-possible for CUPS-Add-Modify-Printer (ipp://localhost/printers/hp1010) from localhost"

But still, I didn't know what to do.

Finally, I read a tip somewhere and installed the samba-client rpm package and it everything worked!

I think system-config-printer should depend on samba-client or at least a more sensible error message that you have to install the samba-client rpm package.


Version-Release number of selected component (if applicable):
cups-1.4.7-3.fc15.x86_64
system-config-printer-1.3.3-1.fc15.x86_64

How reproducible:
Always.

Comment 1 Tim Waugh 2011-07-15 08:11:59 UTC

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


Note You need to log in before you can comment on or make changes to this bug.