Had the same happen here. Lost a heavily customized XF86Config-4 for a multi-head workstation with unusual driver configuration. Several months of small timing adjustments and other tuning to get things just right now out the window. I kick myself for not backing up, but how the file was destroyed really kills me.
I've been searching back through the debian bug reports and see the same problem reported numerous times by people, usual right after the release of xserver-xfree86 upgrade or security update of the package. The reports go back at least as far as 2003. This bug is not new. The discussion in the threads I've found seem to conclude that it may be an issue with a debconf default setting, such as the misuse or misinterpretation of debconf options by the xserver-xfree86 package. A package upgrade should *never* silently overwrite your configuration. -- robh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
