Your message dated Sun, 14 Jan 2007 01:53:37 +0100 with message-id <45A97F11.8090002@ens-lyon.org> and subject line Bug#200022: xserver-xfree86: (erroneous) automatic update of XF86Config-4 without user consultation has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: xserver-xfree86: (erroneous) automatic update of XF86Config-4 without user consultation
- From: Christian Schoenebeck <christian.schoenebeck@epost.de>
- Date: Fri, 4 Jul 2003 14:49:13 +0200
- Message-id: <200307041449.13541.christian.schoenebeck@epost.de>
Package: xserver-xfree86 Version: 4.2.1-9 Hi! When the package is updated, XF86Config-4 will also automatically be updated without user consultation. Unfortunately this process is very erroneous and leaves my configuration always in an unusable status, thus the xserver won't start without correcting XF86Config-4 by hand. I would appreciate to see the common dialog while the package is updated to ask if XF86Config-4 should be overwritten or not in case the user adjusted the config file on his own. Best regards, Christian
--- End Message ---
--- Begin Message ---
- To: 200022-done@bugs.debian.org
- Subject: Bug#200022: xserver-xfree86: (erroneous) automatic update of XF86Config-4 without user consultation
- From: Brice Goglin <Brice.Goglin@ens-lyon.org>
- Date: Sun, 14 Jan 2007 01:53:37 +0100
- Message-id: <45A97F11.8090002@ens-lyon.org>
- In-reply-to: <[🔎] 20070114000632.GG22968@prunille.vinc17.org>
- References: <[🔎] 45A96C42.7010403@ens-lyon.org> <[🔎] 20070114000632.GG22968@prunille.vinc17.org>
Closing since the submitter's address is invalid while people that confirmed the bug didn't reproduce it with Xorg. Brice
--- End Message ---