Hi, setting the option "SHMConfig" to "on" - as suggested by ksynaptics and wished as default value in bug #405714 - seems to "fix" the problem here (I guess the destructor somehow expects it to be set). Kevin