- Dillo-dev - lists.mailman3.com

youtube-dl

by corvid＠lavabit.com

robert wrote: > All I really want is a crisp way to get the alphanumeric file- > descriptor safely away from the youtube window and into a youtube-dl > call - cut and paste would be a significant improvement on copying it, > usually incorrectly, character by character I just tried it, copying and pasting the url from some youtube page, and youtube-dl was able to get the file from it with no problem. Why do you have to enter them character by character?

July 6, 2010

youtube-dl

by bobh＠n-cantrell.demon.co.uk

In article <20100704010103.GB2019(a)local.gobigwest.com>, corvid <corvid(a)lavabit.com> writes >Jeremy wrote: >> corvid wrote: >> > Maybe it would be nice to have the dpis able to register interest in >> > resources meeting certain criteria or something. Or maybe the trick >> > is to simply :) implement the NPAPI. >> >> ??? What is this "NPAPI" of which you speak, Earth being? :-) I >> guess I've not been keeping up. > >Sorry, I wrote more and then I guess I trimmed it down too much. >Netscape Plugin API Sounds interesting - but prone to be a long labour in the night... All I really want is a crisp way to get the alphanumeric file- descriptor safely away from the youtube window and into a youtube-dl call - cut and paste would be a significant improvement on copying it, usually incorrectly, character by character Bob -- robert w hall

July 6, 2010

Re: dillo mysteriously freezes

by jcid＠dillo.org

On Tue, Jul 06, 2010 at 03:19:57AM +0000, corvid wrote: > Dennis wrote: > > You're right. About everything :). The freezes don't happen with 2.0. I > > miss the good blazing-fast old days, sometimes. They also don't seem to > > happen after I downgraded my kernel from 2.6.35-rc3 to 2.6.34. > > (Although now I have other networking problems -- nfs/scp/etc > > stalls :S). > > I wonder whether there's any connection with > http://kerneltrap.org/mailarchive/linux-kernel/2010/6/14/4582843/thread Exact match! (I wonder how you found it) There's even a one-liner patch for the problem in the thread: http://lkml.org/lkml/2010/6/13/155 Have you tried it Dennis? -- Cheers Jorge.-

July 6, 2010

Re: dillo mysteriously freezes

by jcid＠dillo.org

On Mon, Jul 05, 2010 at 09:32:55PM -0400, Dennis Nezic wrote: > On Mon, 5 Jul 2010 08:47:29 -0400, Jorge Arellano Cid wrote: > > On Sun, Jul 04, 2010 at 10:46:50AM -0400, Dennis Nezic wrote: > > > On Sun, 27 Jun 2010 08:22:38 -0400, Dennis Nezic wrote: > > > > On Wed, 23 Jun 2010 09:19:10 -0400, Dennis Nezic wrote: > > > > > On Sun, 20 Jun 2010 10:02:50 -0400, Jorge Arellano Cid wrote: > > > > > > Hi, > > > > > > > > > > > > At this point, there seems to be something wrong with the > > > > > > way the OS is handling its sockets and making them > > > > > > available to the application (after all, the freezes happen > > > > > > within system calls). > > > > > > > > > > > > Please try dillo and don't use any dpis, this will use > > > > > > remote TCP sockets only. Just plain web browsing. If > > > > > > this doesn't freeze, then there's a problem with local > > > > > > sockets. > > > > > > > > > > Yea -- the freezes only occur with the dpis. (Either > > > > > cookie-websites or local file browsing, or bookmarks, etc) > > > > > > > > > > > > > > > > > If plain web browsing works, you can try letting a > > > > > > chance to the OS's defaults by commenting setsockopt in: > > > > > > > > > > > > IO/dpi.c // line 442 in repo > > > > > > dpid/dpid.c // line 525 in repo > > > > > > > > > > > > recompile > > > > > > stop dpid // `dpidc stop` > > > > > > reinstall // make install > > > > > > retry > > > > > > > > > > That actually helped! I hesitated to post, because I did get one > > > > > freeze a few days ago when trying to download a file (file.c), I > > > > > didn't strace it to find which call exactly caused it, but > > > > > otherwise that did seem to fix things! (Any ideas why the > > > > > TCP_NODELAY flag is causing problems? :P) > > > > > > > > I should have hesitated. The freezes are back, about as > > > > frequently as before. But I guess there's nothing dillo can do > > > > about it :\. > > > > > > > > socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 5 > > > > > > > > connect(5, {sa_family=AF_INET, sin_port=htons(5020), > > > > sin_addr=inet_addr ("127.0.0.1")}, 16 **~minute freeze**) = -1 > > > > ETIMEDOUT (Connection timed out) > > > > > > Blargh. I'm not sure how to debug further. Netstat shows that dpid's > > > sockets are in a LISTEN state during the freezes. Dillo's > > > connection to dpid, according to netstat, is SYN_SENT. Telnet'ing > > > to the dpid ports doesn't work during the freezes -- which sounds > > > like a problem with dpid? But these freezes aren't "hard" -- > > > sometimes they work -- once in a while it is able to unfreeze > > > itself, at least for a bit, and I am able to telnet into dpid. > > > Maybe dpid (or linux) is throttling socket connections or > > > something? :| > > > > I believe the problem is in the way your particular kernel > > interacts with dillo. No other GNU/Linux (nor BSD) that we know > > of has this problem. As I'm no kernel expert, it's hard for me to > > suggest a way to further debug the problem. > > > > You may try compiling a vanilla kernel from kernel.org or > > another kernel version from gentoo, or if you really want to find > > out where the freezes come from, asking a knowledgeable guy from > > the TCP sockets area in Linux. > > > > BTW, I'd bet it doesn't happen with Unix domain sockets, that's > > why I suggested trying dillo-2.0. Have you tried that? > > You're right. About everything :). Got a funny feeling here :) > The freezes don't happen with 2.0. I > miss the good blazing-fast old days, sometimes. Do you mean dillo-2.0 is much faster than current repo even with a good kernel (i.e. no loobpack bug)? Please explain. > They also don't seem to > happen after I downgraded my kernel from 2.6.35-rc3 to 2.6.34. > (Although now I have other networking problems -- nfs/scp/etc > stalls :S). > > Thanks for the help and tips! You're welcome. -- Cheers Jorge.-

July 6, 2010

Re: dillo mysteriously freezes

by rogerx＠sdf.org

On Mon, Jul 05, 2010 at 09:32:55PM -0400, Dennis Nezic wrote: >You're right. About everything :). The freezes don't happen with 2.0. I >miss the good blazing-fast old days, sometimes. They also don't seem to >happen after I downgraded my kernel from 2.6.35-rc3 to 2.6.34. >(Although now I have other networking problems -- nfs/scp/etc >stalls :S). This doesn't surprise me one bit. If I can recall correctly, when kernel-2.6.30 was released, somebody submitted a few firmware patches in for a specific network adapter (whose driver is in the kernel). The patches were accepted into the 2.6.30 version breaking the driver at first, then later wake on LAN functions. >From what I saw from the patches, they almost rewrote the entire driver -- but the author did state he should have caught the bugs. The bugs have long since been fixed, but it does bring up an issue concerning kernel stability. However, I also realize if they try improving the quality of the kernel drivers, you might not see the patch integration until 2.7 or 2.8! Might also want to check out remote GDB to debug the kernel. -- Roger http://rogerx.freeshell.org/

July 6, 2010

Re: dillo mysteriously freezes

by corvid＠lavabit.com

Dennis wrote: > You're right. About everything :). The freezes don't happen with 2.0. I > miss the good blazing-fast old days, sometimes. They also don't seem to > happen after I downgraded my kernel from 2.6.35-rc3 to 2.6.34. > (Although now I have other networking problems -- nfs/scp/etc > stalls :S). I wonder whether there's any connection with http://kerneltrap.org/mailarchive/linux-kernel/2010/6/14/4582843/thread

July 6, 2010

Re: dillo mysteriously freezes

by dennisn＠dennisn.dyndns.org

On Mon, 5 Jul 2010 08:47:29 -0400, Jorge Arellano Cid wrote: > On Sun, Jul 04, 2010 at 10:46:50AM -0400, Dennis Nezic wrote: > > On Sun, 27 Jun 2010 08:22:38 -0400, Dennis Nezic wrote: > > > On Wed, 23 Jun 2010 09:19:10 -0400, Dennis Nezic wrote: > > > > On Sun, 20 Jun 2010 10:02:50 -0400, Jorge Arellano Cid wrote: > > > > > Hi, > > > > > > > > > > At this point, there seems to be something wrong with the > > > > > way the OS is handling its sockets and making them > > > > > available to the application (after all, the freezes happen > > > > > within system calls). > > > > > > > > > > Please try dillo and don't use any dpis, this will use > > > > > remote TCP sockets only. Just plain web browsing. If > > > > > this doesn't freeze, then there's a problem with local > > > > > sockets. > > > > > > > > Yea -- the freezes only occur with the dpis. (Either > > > > cookie-websites or local file browsing, or bookmarks, etc) > > > > > > > > > > > > > > If plain web browsing works, you can try letting a > > > > > chance to the OS's defaults by commenting setsockopt in: > > > > > > > > > > IO/dpi.c // line 442 in repo > > > > > dpid/dpid.c // line 525 in repo > > > > > > > > > > recompile > > > > > stop dpid // `dpidc stop` > > > > > reinstall // make install > > > > > retry > > > > > > > > That actually helped! I hesitated to post, because I did get one > > > > freeze a few days ago when trying to download a file (file.c), I > > > > didn't strace it to find which call exactly caused it, but > > > > otherwise that did seem to fix things! (Any ideas why the > > > > TCP_NODELAY flag is causing problems? :P) > > > > > > I should have hesitated. The freezes are back, about as > > > frequently as before. But I guess there's nothing dillo can do > > > about it :\. > > > > > > socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 5 > > > > > > connect(5, {sa_family=AF_INET, sin_port=htons(5020), > > > sin_addr=inet_addr ("127.0.0.1")}, 16 **~minute freeze**) = -1 > > > ETIMEDOUT (Connection timed out) > > > > Blargh. I'm not sure how to debug further. Netstat shows that dpid's > > sockets are in a LISTEN state during the freezes. Dillo's > > connection to dpid, according to netstat, is SYN_SENT. Telnet'ing > > to the dpid ports doesn't work during the freezes -- which sounds > > like a problem with dpid? But these freezes aren't "hard" -- > > sometimes they work -- once in a while it is able to unfreeze > > itself, at least for a bit, and I am able to telnet into dpid. > > Maybe dpid (or linux) is throttling socket connections or > > something? :| > > I believe the problem is in the way your particular kernel > interacts with dillo. No other GNU/Linux (nor BSD) that we know > of has this problem. As I'm no kernel expert, it's hard for me to > suggest a way to further debug the problem. > > You may try compiling a vanilla kernel from kernel.org or > another kernel version from gentoo, or if you really want to find > out where the freezes come from, asking a knowledgeable guy from > the TCP sockets area in Linux. > > BTW, I'd bet it doesn't happen with Unix domain sockets, that's > why I suggested trying dillo-2.0. Have you tried that? You're right. About everything :). The freezes don't happen with 2.0. I miss the good blazing-fast old days, sometimes. They also don't seem to happen after I downgraded my kernel from 2.6.35-rc3 to 2.6.34. (Although now I have other networking problems -- nfs/scp/etc stalls :S). Thanks for the help and tips!

July 6, 2010

Re: dillo mysteriously freezes

by jcid＠dillo.org

On Sun, Jul 04, 2010 at 10:46:50AM -0400, Dennis Nezic wrote: > On Sun, 27 Jun 2010 08:22:38 -0400, Dennis Nezic wrote: > > On Wed, 23 Jun 2010 09:19:10 -0400, Dennis Nezic wrote: > > > On Sun, 20 Jun 2010 10:02:50 -0400, Jorge Arellano Cid wrote: > > > > Hi, > > > > > > > > At this point, there seems to be something wrong with the way > > > > the OS is handling its sockets and making them available to the > > > > application (after all, the freezes happen within system calls). > > > > > > > > Please try dillo and don't use any dpis, this will use remote > > > > TCP sockets only. Just plain web browsing. If this doesn't > > > > freeze, then there's a problem with local sockets. > > > > > > Yea -- the freezes only occur with the dpis. (Either cookie-websites > > > or local file browsing, or bookmarks, etc) > > > > > > > > > > > If plain web browsing works, you can try letting a chance to > > > > the OS's defaults by commenting setsockopt in: > > > > > > > > IO/dpi.c // line 442 in repo > > > > dpid/dpid.c // line 525 in repo > > > > > > > > recompile > > > > stop dpid // `dpidc stop` > > > > reinstall // make install > > > > retry > > > > > > That actually helped! I hesitated to post, because I did get one > > > freeze a few days ago when trying to download a file (file.c), I > > > didn't strace it to find which call exactly caused it, but otherwise > > > that did seem to fix things! (Any ideas why the TCP_NODELAY flag is > > > causing problems? :P) > > > > I should have hesitated. The freezes are back, about as frequently as > > before. But I guess there's nothing dillo can do about it :\. > > > > socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 5 > > > > connect(5, {sa_family=AF_INET, sin_port=htons(5020), > > sin_addr=inet_addr ("127.0.0.1")}, 16 **~minute freeze**) = -1 > > ETIMEDOUT (Connection timed out) > > Blargh. I'm not sure how to debug further. Netstat shows that dpid's > sockets are in a LISTEN state during the freezes. Dillo's connection to > dpid, according to netstat, is SYN_SENT. Telnet'ing to the dpid ports > doesn't work during the freezes -- which sounds like a problem with > dpid? But these freezes aren't "hard" -- sometimes they work -- once in > a while it is able to unfreeze itself, at least for a bit, and I am > able to telnet into dpid. Maybe dpid (or linux) is throttling socket > connections or something? :| I believe the problem is in the way your particular kernel interacts with dillo. No other GNU/Linux (nor BSD) that we know of has this problem. As I'm no kernel expert, it's hard for me to suggest a way to further debug the problem. You may try compiling a vanilla kernel from kernel.org or another kernel version from gentoo, or if you really want to find out where the freezes come from, asking a knowledgeable guy from the TCP sockets area in Linux. BTW, I'd bet it doesn't happen with Unix domain sockets, that's why I suggested trying dillo-2.0. Have you tried that? -- Cheers Jorge.-

July 5, 2010

Re: dillo mysteriously freezes

by dennisn＠dennisn.dyndns.org

On Sun, 27 Jun 2010 08:22:38 -0400, Dennis Nezic wrote: > On Wed, 23 Jun 2010 09:19:10 -0400, Dennis Nezic wrote: > > On Sun, 20 Jun 2010 10:02:50 -0400, Jorge Arellano Cid wrote: > > > Hi, > > > > > > At this point, there seems to be something wrong with the way > > > the OS is handling its sockets and making them available to the > > > application (after all, the freezes happen within system calls). > > > > > > Please try dillo and don't use any dpis, this will use remote > > > TCP sockets only. Just plain web browsing. If this doesn't > > > freeze, then there's a problem with local sockets. > > > > Yea -- the freezes only occur with the dpis. (Either cookie-websites > > or local file browsing, or bookmarks, etc) > > > > > > > > If plain web browsing works, you can try letting a chance to > > > the OS's defaults by commenting setsockopt in: > > > > > > IO/dpi.c // line 442 in repo > > > dpid/dpid.c // line 525 in repo > > > > > > recompile > > > stop dpid // `dpidc stop` > > > reinstall // make install > > > retry > > > > That actually helped! I hesitated to post, because I did get one > > freeze a few days ago when trying to download a file (file.c), I > > didn't strace it to find which call exactly caused it, but otherwise > > that did seem to fix things! (Any ideas why the TCP_NODELAY flag is > > causing problems? :P) > > I should have hesitated. The freezes are back, about as frequently as > before. But I guess there's nothing dillo can do about it :\. > > socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 5 > > connect(5, {sa_family=AF_INET, sin_port=htons(5020), > sin_addr=inet_addr ("127.0.0.1")}, 16 **~minute freeze**) = -1 > ETIMEDOUT (Connection timed out) I have also noticed that, after 11 tries, ... Dpi_blocking_start_dpid: try 11 Dpi_check_dpid_ids: Connection timed out dpid seems to respawn itself, with a new mksecret (updated dpid_comm_keys). Why is it respawning itself without stopping it's earlier instances?

July 4, 2010

Re: dillo mysteriously freezes

by dennisn＠dennisn.dyndns.org

On Sun, 27 Jun 2010 08:22:38 -0400, Dennis Nezic wrote: > On Wed, 23 Jun 2010 09:19:10 -0400, Dennis Nezic wrote: > > On Sun, 20 Jun 2010 10:02:50 -0400, Jorge Arellano Cid wrote: > > > Hi, > > > > > > At this point, there seems to be something wrong with the way > > > the OS is handling its sockets and making them available to the > > > application (after all, the freezes happen within system calls). > > > > > > Please try dillo and don't use any dpis, this will use remote > > > TCP sockets only. Just plain web browsing. If this doesn't > > > freeze, then there's a problem with local sockets. > > > > Yea -- the freezes only occur with the dpis. (Either cookie-websites > > or local file browsing, or bookmarks, etc) > > > > > > > > If plain web browsing works, you can try letting a chance to > > > the OS's defaults by commenting setsockopt in: > > > > > > IO/dpi.c // line 442 in repo > > > dpid/dpid.c // line 525 in repo > > > > > > recompile > > > stop dpid // `dpidc stop` > > > reinstall // make install > > > retry > > > > That actually helped! I hesitated to post, because I did get one > > freeze a few days ago when trying to download a file (file.c), I > > didn't strace it to find which call exactly caused it, but otherwise > > that did seem to fix things! (Any ideas why the TCP_NODELAY flag is > > causing problems? :P) > > I should have hesitated. The freezes are back, about as frequently as > before. But I guess there's nothing dillo can do about it :\. > > socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 5 > > connect(5, {sa_family=AF_INET, sin_port=htons(5020), > sin_addr=inet_addr ("127.0.0.1")}, 16 **~minute freeze**) = -1 > ETIMEDOUT (Connection timed out) Blargh. I'm not sure how to debug further. Netstat shows that dpid's sockets are in a LISTEN state during the freezes. Dillo's connection to dpid, according to netstat, is SYN_SENT. Telnet'ing to the dpid ports doesn't work during the freezes -- which sounds like a problem with dpid? But these freezes aren't "hard" -- sometimes they work -- once in a while it is able to unfreeze itself, at least for a bit, and I am able to telnet into dpid. Maybe dpid (or linux) is throttling socket connections or something? :|

July 4, 2010