On Sat, 2004-04-10 at 15:24 -0500, Chris Hawks wrote: > ---Reply to mail from Jack Spaar about help please with plucker-build traceback > If you can tell me what you had (that broke it) and what you changed > to fix it, maybe the parser can detect that and give the user a more > useful message.
OK, here's the channel's home.html that breaks plucker-build, if it's any help: <html> <body> <a href="http://slashdot.org/palm"; maxdepth="4" stayonhost bpp="0">Slashdot</a> <br><a href="http://linuxtoday.com/palm"; maxdepth="3" stayonhost bpp="1">Linux Today</a> <br><a href="http://www.wired.com/news_drop/palmpilot"; maxdepth="4" url_pattern="http://.*wired.com/news/.*"; bpp="1">Wired</a> </body> </html> On Sat, 2004-04-10 at 16:42 -0400, David A. Desrosiers wrote: > > I've been tinkering with this over the last couple of weeks (mostly > because some people have asked for custom Plucker Desktop installers), and > it seems to be related to the fact that Plucker Desktop really isn't using > threads, as it should, and somehow the event loop is blocking. Prodding the > wxWidgets folks produced some good feedback, and I'm going to be testing > some potential fixes over the next few weeks. > > Mostly we should be using threads, and not wxYield(), but it could > be deeper than that. wxWidgets hackers are welcome to help us fix it. Could be the same issue. I find that moving the mouse has no impact (the progress bar is already at 100%). I'm unable to click any buttons. strace shows the process blocked on a futex: futex(0x84d8598, FUTEX_WAIT, 2, NULL <unfinished ...> If you need a beta-tester feel free to email me... --Jack _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
