This happened after upgrading from libnautilus 2.6.1 to libnautilus 2.6.2 When I downgrade to libnautilus 2.6.1 the proble disappears. So maybe this bug should be reported against libnautilus instead.