> This one shouldn't happen. Can you run it under gdb and see where > it's stuck? (in fact you may use kcachegrind). Pity no one experiencing the problem has done this, it is a good suggestion. Don.