Bug 1314070
| Summary: | Segfault with basic use of libproxy-python | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | F Wolff <friedel> |
| Component: | libproxy | Assignee: | David King <amigadave> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | amigadave, danw, i, npmccallum |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-03-03 09:00:39 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This looks like https://code.google.com/archive/p/libproxy/issues/146 for which there is no fix (yet). Additionally, this is a duplicate of bug 1296817 (which also has a stack trace). *** This bug has been marked as a duplicate of bug 1296817 *** |
Description of problem: I'm testing a python application on Fedora 23 that uses libproxy-python. It has a segfault early when using libproxy. Version-Release number of selected component (if applicable): 0.4.11-12 Steps to Reproduce: Minimal example: python -c "import libproxy; print libproxy.ProxyFactory().getProxies('http://fedoraproject.org')" Actual results: Segmentation fault (core dumped) Expected results: ['direct://'] (or whatever the proxy configuration is) Additional info: $ rpm -qa|grep libproxy libproxy-0.4.11-12.fc23.x86_64 libproxy-gnome-0.4.11-12.fc23.x86_64 libproxy-bin-0.4.11-12.fc23.x86_64 libproxy-python-0.4.11-12.fc23.noarch The commandline tool from libproxy-bin ("proxy") works without crash: $ proxy http://fedoraproject.org direct://