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.
Cannot confirm, works for me with localhost:443
Confirmed, it does not work for me.
Please provide debugging output so we can report this upstream.
I tried again (using woodpecker as proxy) and it's working just fine now... Agostino, does it still fail for you?
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.
(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.
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?
(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.