Bug#259080: xserver-xfree86: Please special case mouse setup for GNU/Hurd
reassign 259080 xserver-xorg
severity 259080 important
thanks
On Wed, Jul 14, 2004 at 12:31:06PM -0500, Branden Robinson wrote:
> On Tue, Jul 13, 2004 at 12:55:25AM +0200, Michael Banck wrote:
> > The configuration for GNU/Linux and GNU/Hurd is mostly identical,
> > however, there is a difference in how the mouse is setup.
> >
> > Basically, on hurd-i386, the Device should always be "/dev/mouse" and
> > the Protocol be "osmouse". ZAxisMapping should not be set,
> > Emulate3Buttons can be, depending on debconf.
> >
> > Unfortunately, I'm no debconf wizard, so I hope the changes are not
> > overly complex and could be done relatively easily.
>
> Yes, this is one of the simpler parts of the problem space.
Since moving to xserver-xorg, dpkg-reconfigure (even at low priority)
does not work anymore, since the debconf values for
inputdevice/mouse/port and inputdevice/mouse/protocol are empty, leading
to an error message and a 0 size xorg.conf, from
/var/cache/debconf/config.dat:
Name: xserver-xorg/config/inputdevice/mouse/port
Template: xserver-xorg/config/inputdevice/mouse/port
Value:
Owners: xserver-xorg
Flags: seen
Variables:
choices =
Name: xserver-xorg/config/inputdevice/mouse/protocol
Template: xserver-xorg/config/inputdevice/mouse/protocol
Value:
Owners: xserver-xorg
Flags: seen
Variables:
choices =
I tried to set them manually in there, but to no avail (not being a
debconf guru). Thus upgrading this bug report to important, as it
renders the package useless on a non-releasing architecture.
Anyway, the right values for hurd-i386 are "/dev/mouse" for port and
"osmouse" for protocol, could this made default?
This is what dpkg-architecture outputs, if it helps:
DEB_BUILD_ARCH=hurd-i386
DEB_BUILD_ARCH_OS=hurd
DEB_BUILD_ARCH_CPU=i386
DEB_BUILD_GNU_CPU=i486
DEB_BUILD_GNU_SYSTEM=gnu
DEB_BUILD_GNU_TYPE=i486-gnu
DEB_HOST_ARCH=hurd-i386
DEB_HOST_ARCH_OS=hurd
DEB_HOST_ARCH_CPU=i386
DEB_HOST_GNU_CPU=i486
DEB_HOST_GNU_SYSTEM=gnu
DEB_HOST_GNU_TYPE=i486-gnu
Should I find somebody who whips up a patch for this?
cheers,
Michael
--
Michael Banck
Debian Developer
mbanck@debian.org
http://www.advogato.org/person/mbanck/diary.html
Reply to: