Bug#353255: upgrading kernel to 2.6.16 resolves the bug

[pibou at club.fr]

I've just upgraded my 2.6.12 debian-build kernel to 2.6.16-1-686, and 
the bug no longer occurs. I now understand why my other computer, 
working under Debian Etch with a 2.6.15 kernel wasn't experiencing the 
bug... Seems to be a 2.6.12 only bug, at least it is corrected under 
2.6.15 and 2.6.16.

Maybe linux-image > 2.6.12 should be recommended or suggested with 
nautilus, or a warning should appear.

Thanks