Bug 213735

Summary:	System Config Printer can't connect to CUPS server at CUPS server error System Config Printer says There was an error during the CUPS operation: 'httpConnectionEncrypt failed'.
Product:	[Fedora] Fedora	Reporter:	Keith Holmes <keith.holmes>
Component:	cups	Assignee:	Tim Waugh <twaugh>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-11-06 10:38:31 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:
Bug Depends On:
Bug Blocks:	207681

Description Keith Holmes 2006-11-02 19:09:20 UTC

Description of problem:

System Config Printer says when you try to connect to the CUPS server 

There was an error during the CUPS operation: 'httpConnectionEncrypt failed'.


Version-Release number of selected component (if applicable):
 1:1.2.4-9 

How reproducible:


Steps to Reproduce:
1. Open System Config printer
2. Click connect to CUPS server
3.
  
Actual results:
Says There was an error as above...

Expected results:
See configured printers and use them!

Additional info:

Comment 1 Tim Waugh 2006-11-03 11:13:50 UTC

What does 'lpstat -s' say?

Comment 2 Keith Holmes 2006-11-03 16:45:56 UTC

lpstat: Unable to connect to server

Comment 3 Tim Waugh 2006-11-03 16:52:29 UTC

How about '/sbin/service cups status'?

Have you cancelled any print jobs quite recently?

Comment 4 Keith Holmes 2006-11-03 17:04:11 UTC

/sbin/service cups status

cupsd dead but pid file exists

No but upgraded from FC6 Pre to FC6

Comment 5 Tim Waugh 2006-11-03 17:20:34 UTC

Please try this test update:

https://www.redhat.com/archives/fedora-test-list/2006-November/msg00060.html

After installing, restart CUPS with '/sbin/service cups restart' as root (or
reboot).  Does that fix the problem?

Comment 6 Keith Holmes 2006-11-05 08:31:19 UTC

Yes!

Thanks very much.

Keith

Comment 7 Tim Waugh 2006-11-06 10:38:31 UTC


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