Bug 622877

Summary: [abrt] setroubleshoot-server-2.2.91-2.fc14: base.py:957:request:AttributeError: HTTPSConnection instance has no attribute 'getreply'
Product: [Fedora] Fedora Reporter: Masami Ichikawa <masami256>
Component: python-basemapAssignee: Jef Spaleta <jspaleta>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: dwalsh, gwync, jspaleta, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:3572f49e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-11 13:05:28 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
File: backtrace none

Description Masami Ichikawa 2010-08-10 16:07:55 UTC 
abrt version: 1.1.10
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python -Es /usr/bin/sealert -s
component: setroubleshoot
executable: /usr/bin/sealert
kernel: 2.6.35-3.fc14.i686.PAE
package: setroubleshoot-server-2.2.91-2.fc14
reason: base.py:957:request:AttributeError: HTTPSConnection instance has no attribute 'getreply'
release: Fedora release 14 (Branched)
time: 1281455982
uid: 500

comment
-----
When I got a warning message which said that "SELinux prevented yum from writing fedora-debuginfo." ,  I wanted to report it via sealert.
so I did test steps to report it.  When I click the "OK" button to send report ABRT noticed sealert was crashed.

How to reproduce
-----
1.Run SELinux Troubleshooter from "Application.
2.Click the "Report this Bug..." button.
3.Click the "Submit Report" button.
4.Select "bugzilla.redhat.com".
5.Enter your ID and Password.
6.Check "Save password in key ring".
7.Click "OK"
Comment 1 Masami Ichikawa 2010-08-10 16:07:57 UTC 
Created attachment 437937 [details]
File: backtrace
Comment 2 Daniel Walsh 2010-08-11 13:05:28 UTC 

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