But we won't go there.
That's not me. On the field of life I'm infantry. It's ok, I've got lots of company.
So I just know that this 10.6 bug would have whacked me ...
... The problem seems to happen only when guest accounts were enabled for login under Leopard before updating to Snow Leopard...It's quite a bug. It's a bit like a personal version of the
Regarding the "Guest" account data loss issue, the symptoms sound very similar to those affecting Leopard users until the release of 10.5.5. Given the similarities, one might suspect the reuse of buggy code.
The 10.5 flaw actually had two facets - one is that the wrong home folder may be deleted. The other is that the same flaw permits login to non-Guest accounts without a password. See CVE-2008-3610 here:
About the security content of Mac OS X v10.5.5 and Security Update 2008-006
Description: A race condition exists in Login Window. To trigger this issue, the system must have the Guest account enabled or another account with no password. In a small proportion of attempts, an attempt to log in to such an account will not complete. The user list would then be presented again, and the person would be able to log in as any user without providing a password. If the original account were the Guest account, the contents of the new account will be deleted on logout. This update addresses the issue by properly clearing Login Window state when the login does not complete. This issue does not affect systems prior to Mac OS X v10.5.
Based on reports on the web, it appears that both aspects are present in Snow Leopard, and some users claim to have established the requirements for reproducibility. I don't have Snow Leopard so unfortunately can't test things for myself, but because of the implications, will refrain from posting a link to instructions. If confirmed, the key point would be that unlike Apple's assurances that it is something that occurs only in extremely rare cases, it may well be something that is guaranteed to be triggered based on a specific sequence of events, the likelihood of which may not be so "extremely rare" depending on an individual's habits.
Regardless, since the file deletion appears to be directly tied to the resetting feature of the "Guest" account, disabling GUI login for "Guest" should prevent that aspect from being triggered, and not having any passwordless accounts enabled (including "Guest") should take care of the other