Bug#362078: xserver-xorg: dpkg-reconfigure doesn't work if the xorg.conf has been customized
Marc Wilson <msw@cox.net> wrote:
> On Wed, Apr 12, 2006 at 01:02:45AM -0400, David Nusinow wrote:
> > The dpkg-reconfigure script needs to write a new xorg.conf if the file has
> > been customized. A user in #debian reported that this failed on his system,
> > and it made it difficult for him to automagically adapt to the new paths
> > for modular. This will provide a manual easy way out of this dilemma,
> > easing future support.
>
> As long as it writes it somewhere OTHER than on top of /etc/X11/xorg.conf,
> please.
The standard thing to do is to observe dpkg's default behavior, which
depending on how you have configured dpkg is to save the new
configuration in xorg.conf.dpkg-new or the old one in xorg.conf.dpkg-old
See #374583.
Fathi Boudra <fboudra@free.fr> wrote:
> * if i remove my xorg.conf and run dpkg-reconfigure, no new file created
In addition to removing xorg.conf, in 1:7.0.22, you may have to also
perform the following:
sudo sh -c "readlink /etc/X11/X | md5sum > /var/lib/x11/X.md5sum"
See #374578.
You will probably also have to perform the following:
sudo vi /var/lib/dpkg/info/xserver-xorg.postinst
# Comment out the following line as well as matching else and endif.
# if [ -z "$UPGRADE" ] || dpkg --compare-versions "$2" le "1:7.0.14"; then
--
Bill Wohler <wohler@newt.com> http://www.newt.com/wohler/ GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E.
If you're passed on the right, you're in the wrong lane.
Reply to: