Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 417633 - www-client/qupzilla-1.2.0 does not work with SOCKS5 proxy
Summary: www-client/qupzilla-1.2.0 does not work with SOCKS5 proxy
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Qt Bug Alias
URL:
Whiteboard:
Keywords:
Depends on: qt-4.8.2-stable
Blocks:
  Show dependency tree
 
Reported: 2012-05-26 12:20 UTC by Agostino Sarubbo
Modified: 2012-07-20 18:40 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2012-05-26 12:20:31 UTC
Qupzilla does not work with socks5 proxy.


I'm trying to do: 

ssh -D 1080 $host

and then set in qupzilla proxy socks5 on 127.0.0.1:1080


pesa confirms that does not work; feel free to ask other info about.
Comment 1 Ben de Groot (RETIRED) gentoo-dev 2012-05-26 14:08:23 UTC
Cannot confirm, works for me with localhost:443
Comment 2 Davide Pesavento (RETIRED) gentoo-dev 2012-05-26 15:02:32 UTC
Confirmed, it does not work for me.
Comment 3 Ben de Groot (RETIRED) gentoo-dev 2012-07-01 07:23:19 UTC
Please provide debugging output so we can report this upstream.
Comment 4 Davide Pesavento (RETIRED) gentoo-dev 2012-07-01 18:46:20 UTC
I tried again (using woodpecker as proxy) and it's working just fine now...

Agostino, does it still fail for you?
Comment 5 Ben de Groot (RETIRED) gentoo-dev 2012-07-02 06:34:52 UTC
part of log from upstream irc:

<nowrep> ago: which Qt version do you use with Qupzilla and with Arora? (both have the info in help->about qt)
<nowrep> ago: i found some similiar issue (http://bugs.quassel-irc.org/issues/1160) and it says that qt 4.8.2 fixes it ...
<nowrep> ago: oh yeah, that's true: with Qt 4.8.2 or 4.7.4 it works absolutely without problems .... so the issue is Qt 4.8.1

That might explain why I never had a problem, because I skipped 4.8.1 (I went from 4.8.0 straight to 4.8.2). If this is correct and 4.8.2 fixes this bug, then we need to proceed with stabilization of 4.8.2 ASAP.
Comment 6 Davide Pesavento (RETIRED) gentoo-dev 2012-07-02 17:44:49 UTC
(In reply to comment #5)
> That might explain why I never had a problem, because I skipped 4.8.1 (I
> went from 4.8.0 straight to 4.8.2). If this is correct and 4.8.2 fixes this
> bug, then we need to proceed with stabilization of 4.8.2 ASAP.

Yes, I think we can start with 4.8.2 stabilization, but some arches (at least x86 and ppc) must wait for bug 401615 to be solved before proceeding.
Comment 7 Michael Palimaka (kensington) gentoo-dev 2012-07-20 18:08:14 UTC
Since 4.8.2 is stable for all the archs of qupzilla, shall we consider this bug fixed or are we going to add a Qt version dependency to prevent users from running into this bug?
Comment 8 Davide Pesavento (RETIRED) gentoo-dev 2012-07-20 18:40:50 UTC
(In reply to comment #7)
> Since 4.8.2 is stable for all the archs of qupzilla, shall we consider this
> bug fixed or are we going to add a Qt version dependency to prevent users
> from running into this bug?

Not worth it IMO. We're going to prune 4.8.1 as soon as 4.8.2 is stable on alpha/ia64/sparc too.