On Mon, Sep 29, 2003 at 08:46:21PM -0700, Andre Lehovich wrote: > On Sat, 27 Sep 2003, Branden Robinson wrote: > > What version did you upgrade from? > > The version that was previously in Testing. (I did a > dist-upgrade last week when AJ pushed glibc in.) Poking > around on snapshot.debian.net makes me think it was 4.2.1-6, > but I'm not positive. Sorry I can't be more specific.
Well, that was the version previously in testing, and had been for
weeks, so that was probably it, yes.
> > Do you the stuff talked about in
> > /usr/share/doc/xfree86-common/NEWS.Debian.gz might have
> > had something to do with this?
>
> I think no, but I'm not sure. (Was that file supposed to
> display during the upgrade? I didn't see it until your
> email, though I did skim the debian.Changelog.gz before
> upgrading.)
If you install apt-listchanges and don't configure it to ignore
NEWS.Debian files, it will show you these on upgrades when you use
apt-get, yes.
> To clarify my customization:
>
> I've never followed the recommended procedure for
> customizing the file, but just added in the xfstt line by
> hand. It always got clobbered by upgrades, but fixing it by
> hand was easy so I never put the energy into learning the
> right way. (And I see now since the checksum doesn't match
> with my customization it won't get clobbered in the future,
> which is nice.)
Yes; when designing the debconf-based conffile management system a few
years ago, I underestimated how many users like yourself there are.
Over the past year, particularly, there has been growing consensus
within Debian that the "manage config file with debconf?" and "debconf
markers in config files" approach just isn't the right one.
Glad to hear you prefer the new method. Except where it's buggy. :(
> I do now have a /etc/X11/XF86Config-4.dpkg-old file.
>
> Is there any other information I can give you?
Well, I see from the debconf data in your initial report that your mouse
is in fact configured to use protocol "PS/2". Did you change that in
the debconf database (e.g., by running dpkg-reconfigure) before filing
the report?
If you did, this problem might be difficult to track down.
If not, there may be a bug in dexconf, which is the program that
actually generates the config file. To verify this, ensure that your
debconf data still reports your protocol as PS/2. Here's how I'd do it:
$ debconf-show xserver-xfree86 | grep protocol
debconf: DbDriver "passwords" warning: could not open
/var/cache/debconf/passwords.dat: Permission denied
xserver-xfree86/config/inputdevice/mouse/protocol: ImPS/2
If it does, tell dexconf to create a new configuration file in a safe
place:
[EMAIL PROTECTED]:~$ dexconf -o /tmp/foo
debconf: DbDriver "passwords" warning: could not open
/var/cache/debconf/passwords.dat: Permission denied
Then check to see what protocol actually got written to the file:
[EMAIL PROTECTED]:~$ grep -5i protocol /tmp/foo
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection
Section "Device"
Notes on the above:
* The debconf DbDriver warning is harmless and only happens because I
am accessing the debconf database as a mere mortal user, not root.
* My system is configured differently from yours, so ImPS/2 may not be
correct for you. :)
Please reply to this bug and let me know what you learn.
--
G. Branden Robinson |
Debian GNU/Linux | // // // / /
[EMAIL PROTECTED] | EI 'AANIIGOO 'AHOOT'E
http://people.debian.org/~branden/ |
signature.asc
Description: Digital signature
