Hi there, I just commited the code that cleanups the bookmarks server. It works like this: <q> /* * If this is our first run, kill the (old) bookmarks server, * and create the '~/.dillo/.072' file to flag what we did. */ static void Dillo_check_bm_srv12(char *dir) [...] </q> Yes, it uses the "[b]m_srv12" trick and some other precautions. Please test it: the whole point is that when installing the new version of dillo (072), the old bookmarks server may keep running and survive the updated. The new code detects the first dillo-072 run and issues a kill command to "bm_srv12". Onto another topic: A last minute leak fix (iterators) left dillo a bit unstable. We knew the iterators had a leak and it's great to have found it. Now it will take some extra time to try to fix the problem and, after that, stress-test the Copy&Paste code again. We haven't got an accurate procedure to reproduce the crash (yet). This explanation may help: <q> I think I have found a relatively new segfault bug : You need some sort of thumbtags like the screenshots on http://www.incagold.com/products/Speed/speedthief.php Now you have to move down the mouse and at the same time click on one image (i.e. click while still aiming for the image). If the button-push occures outside the image and the button-release inside the image, chances are high to get a segfault. This is a bit hard to reproduce, but I couldn't get an older version with selection to behave like that. It also happened a few times to me last night (after the last 'cvs up') but never before. </q> We'll be working on it. Cheers Jorge.-