Hi guys! Did you test 0.7.3 as I suggested? The good/bad news (depends on being optimistic/pesimistic!) is that yesterday I found a bug. The newest CVS has a g_print that makes it evident. Valgrind says: ==983== Invalid memory access of size 1 ==983== at 0x4014861B: strcmp (in /usr/local/lib/valgrind/valgrind.so) ==983== by 0x403CABAD: g_str_equal (in /usr/lib/libglib-1.2.so.0.0.10) ==983== by 0x403BDB38: g_hash_table_lookup_extended (in /usr/lib/libglib-1.2 ==983== by 0x805B912: p_Dw_gtk_viewport_put_anchor (dw_gtk_viewport.c:770) ==983== Address 0x41054960 is 0 bytes inside a block of size 12 free'd ==983== at 0x40148050: free (in /usr/local/lib/valgrind/valgrind.so) ==983== by 0x403C1FE8: g_free (in /usr/lib/libglib-1.2.so.0.0.10) ==983== by 0x805D646: Dw_page_destroy (dw_page.c:338) ==983== by 0x402EB876: gtk_marshal_NONE__NONE (in /usr/lib/libgtk-1.2.so.0.9 Note the p_Dw_gtk_viewport_put_anchor where the g_print is. This may come from somewhere else, so let's hunt. It should be solved before making the release. Cheers Jorge.-