On Sat, Dec 28, 2013 at 08:32:32PM +0100, Julien Cristau wrote:
> On Fri, Dec 27, 2013 at 16:22:21 +0000, ael wrote:
>
> > Package: xserver-xorg-input-evdev
> > Version: 1:2.8.2-1
> > Severity: normal
> >
> > >From Xorg.0.log:
> >
> > (EE) evdev: PS2++ Logitech TrackMan: ioctl EVIOCGBIT for bitmask in
> > EvdevOpenMTDev failed: Inappropriate ioctl for device
> > [ 1052.675] (EE) PS2++ Logitech TrackMan: Couldn't open mtdev device
> >
> > The trackball is not multi-touch. I have a custom rule for these devices
> > under /etc/udev/rules.d/ which perhaps is no longer used?
> >
> > --------------------------------------------------------
> > # Logitech Marble Mice PN 804377-0000, PN 810-000767 or
> > # PN 804251-0000 connected via USB or PS/2
> > # Marble FX or Marble Mouse (ael)
> >
> > ACTION!="add|change", GOTO="xorg_marble_end"
> > KERNEL!="event*", GOTO="xorg_marble_end"
> >
> > #ENV{ID_PATH}!="platform-i8042-serio-1", GOTO="xorg_marble_end"
> > # Above for PS/2, misses USB. name below seems to be enough
> >
> > ATTRS{name}=="ImExPS/2 Logitech Explorer Mouse", GOTO="marbles"
> > ATTRS{name}=="Logitech USB Trackball", GOTO="marbles"
> > ATTRS{name}=="PS2++ Logitech Mouse", GOTO="marble_FX"
> > ATTRS{name}=="PS2++ Logitech TrackMan" , GOTO="marble_FX"
> > GOTO="xorg_marble_end"
> >
> > LABEL="marbles"
> >
> > ENV{x11_options.ButtonMapping}="1 9 3 4 5 6 7 8 2"
> >
> > LABEL="marble_FX"
> >
> > #ENV{x11_options.Protocol}="ExplorerPS/2"
> >
> > ENV{x11_options.EmulateWheel}="true"
> > ENV{x11_options.EmulateWheelButton}="8"
> > ENV{x11_options.YAxisMapping}="4 5"
> > ENV{x11_options.XAxisMapping}="6 7"
> > ENV{x11_options.ZAxisMapping}="4 5"
> > #ENV{x11_options.Emulate3Buttons}="0"
> >
> I don't think the above (X options in udev rules) can ever have worked.
They did for a while, but I suspect a long time ago.
But now I have the equivalent in xorg.conf as in the original bug
report. This has been working for several years, but after a recent
upgrade, is now failing with the EVIOCGBIT. Any help with that?
I guess that I should remove the udev rule just in case: I think that I
had just forgotten about it. I will remove that rule and report back
just in case it was somehow triggering the problem.
Thanks for the reply and any further help,
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
