Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 622877 - [abrt] setroubleshoot-server-2.2.91-2.fc14: base.py:957:request:AttributeError: HTTPSConnection instance has no attribute 'getreply'
[abrt] setroubleshoot-server-2.2.91-2.fc14: base.py:957:request:AttributeErro...
Status: CLOSED DUPLICATE of bug 619276
Product: Fedora
Classification: Fedora
Component: python-basemap (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Jef Spaleta
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-08-10 12:07 EDT by masami256
Modified: 2010-08-11 09:05 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-11 09:05:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (2.73 KB, text/plain)
2010-08-10 12:07 EDT, masami256
no flags Details

  None (edit)
Description masami256 2010-08-10 12:07:55 EDT
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

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 masami256 2010-08-10 12:07:57 EDT
Created attachment 437937 [details]
File: backtrace
Comment 2 Daniel Walsh 2010-08-11 09:05:28 EDT

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

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