Bug 1314070 - Segfault with basic use of libproxy-python
Summary: Segfault with basic use of libproxy-python
Keywords:
Status: CLOSED DUPLICATE of bug 1296817
Alias: None
Product: Fedora
Classification: Fedora
Component: libproxy
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David King
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-02 20:07 UTC by F Wolff
Modified: 2016-03-03 09:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-03 09:00:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description F Wolff 2016-03-02 20:07:27 UTC
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://

Comment 1 David King 2016-03-03 09:00:39 UTC
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 ***


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