Bug 373176

*** This bug has been marked as a duplicate of bug 370948 ***

This bug is not a duplicate of bug bug 370948.

The situation I reported in the initial comment is no longer up-to-date with the current FACTORY situation. Previously the TrackPoint Device was shown twice in SAX, but now SAX doesn't list that device any longer. So only my touchpad and my USB mouse are detected/listed in SAX.

Anyway, the TrackPoint is still working, it just can't be configured via SAX.

could you call

 
  init 3
  sax2

and send the file

 /var/log/SaX.log

thanks

Created attachment 209021 [details]
/var/log/SaX.log

Looking at the first few lines of this log file, it seems like SAX detects the TrackPoint device:

        Mouse2    =>  Protocol   : explorerps/2
	Mouse2    =>  Device     : /dev/input/mice
	Mouse2    =>  Buttons    : 5
	Mouse2    =>  Wheel      : 1
	Mouse2    =>  Emulate    : 0
	Mouse2    =>  Name       : TPPS/2 IBM TrackPoint
	Mouse2    =>  VendorID   : 0x0002
	Mouse2    =>  DeviceID   : 0x000a
	Mouse2    =>  Profile    : ibm-trackpoint
	Mouse2    =>  RealDevice : <undefined>
	Mouse2    =>  NutShell   : 1

This device just doesn't show up in the GUI.

the behavior is correct: sax2 detects all three devices:

	Mouse0    =>  Protocol   : explorerps/2
	Mouse0    =>  Device     : /dev/input/mice
	Mouse0    =>  Name       : Logitech USB Receiver
	Mouse0    =>  Profile    : <undefined>

	Mouse1    =>  Protocol   : explorerps/2
	Mouse1    =>  Device     : /dev/input/mice	
	Mouse1    =>  Name       : SynPS/2 Synaptics TouchPad
	Mouse1    =>  Profile    : synaptics
	
	Mouse2    =>  Protocol   : explorerps/2
	Mouse2    =>  Device     : /dev/input/mice
	Mouse2    =>  Name       : TPPS/2 IBM TrackPoint
	Mouse2    =>  Profile    : ibm-trackpoint

a) the Synaptics touchpad is turned into a single InputDevice section
   using the synaptics mouse driver

b) the other devices are _both_ handled by the multiplexer device
   /dev/input/mice and therefore _must_ be handled in only _one_
   additional InputDevice section

c) the IBM trackpoint normally would include EmulateWheel by the
   ibm-trackpoint profile BUT there is another normal mouse the
   Logitech USB Receiver which does not require the wheel emulation
   which means it is switched off because the external device has
   the higher priority

Created attachment 209405 [details]
/var/log/SaX.log

I was wrong, the original bug still exists. I did a fresh install of openSUSE 11.0 using the Beta1 DVD ISO today. I unplugged the 'Logitech USB Receiver' so there's only the Synaptics Touchpad and the IBM TrackPoint (Lenovo UltraNav) on my system available. Next I did the following:

# init 3
# rm /etc/X11/xorg.conf*
# sax2

I choose 'Change configuration' and now my TrackPoint is detected twice again. All clicks on the TrackPoint buttons are detected as double-clicks. Sax2 writes the following InputDevice sections to xorg.conf:

Section "InputDevice"
  Driver       "synaptics"
  Identifier   "Mouse[1]"
  Option       "Buttons" "5"
  Option       "Device" "/dev/input/mice"
  Option       "Emulate3Buttons" "on"
  Option       "HorizScrollDelta" "0"
  Option       "InputFashion" "Mouse"
  Option       "Name" "Synaptics;Touchpad"
  Option       "Protocol" "explorerps/2"
  Option       "SHMConfig" "on"
  Option       "Vendor" "Sysp"
  Option       "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
  Driver       "mouse"
  Identifier   "Mouse[3]"
  Option       "ButtonNumber" "5"
  Option       "Device" "/dev/input/mice"
  Option       "EmulateWheel" "on"
  Option       "EmulateWheelButton" "2"
  Option       "InputFashion" "Mouse"
  Option       "Name" "IBM;TPPS/2 TrackPoint"
  Option       "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
  Driver       "mouse"
  Identifier   "Mouse[5]"
  Option       "Buttons" "5"
  Option       "Device" "/dev/input/mice"
  Option       "Name" "TPPS/2 IBM TrackPoint"
  Option       "Protocol" "explorerps/2"
  Option       "Vendor" "Sysp"
  Option       "ZAxisMapping" "4 5"
EndSection

Also see the attached /var/log/SaX2.log file.

I could not reopen this bug with the last comment (because I added an attachment).

Created attachment 209422 [details]
3 screenshots of the TrackPoint detected twice

The attached screenshot shows the sax gui how it renders two separate tabs for the TrackPoint device. To take those screenshots I ran sax from within a running KDE4 session. I noticed some differences between running sax from the console in runlevel 3 and from within a running Xorg/KDE4 session:

- Screenshot 2: When I run sax2 from console in runlevel 3 the gui shows "Emulate wheel with mouse button 1". But as shown in the screenshot, from within a KDE4 session it is correctly assigned to mouse button 2.

- Screenshot 3: When I run sax2 from console in runlevel 3 the gui shows the device as enabled. But as shown in the screenshot, from within a KDE4 session the checkbox is not enabled.

When I run sax2 from console in runlevel 3 and do the "Mouse Test" single clicks on the TrackPoint buttons are detected as double-clicks. When I do the same with sax2 started from within a running KDE4 session, single clicks on the TrackPoint buttons are detected as normal single clicks and not as double clicks.

I'm sorry I can't reproduce this. could you call

init 3
cp /etc/X11/xorg.conf /etc/X11/xorg.conf.backup
sax2 -a

===> send the information which is printed on the console
===> send the /var/log/SaX.log file

thanks

*** This bug has been marked as a duplicate of bug 382036 ***

I can't see why this bug should be a duplicate of #382036. The following happens:

Case1)
- init 3
- rm /etc/X11/xorg.conf*
- sax2 -a
- result: 3 input (one duplicate) devices, but only two in ServerLayout.
- attached xorg.conf_1 to this bug

Case2)
- init 3
- rm /etc/X11/xorg.conf*
- sax2 -r -m 0=fglrx
- click "ok"
- result: 3 input (one duplicate) devices and all 3 are in ServerLayout section, which leads to a double click every time I use the trackpoint buttons.

Created attachment 210316 [details]
xorg.conf generated by "sax2 -a"

Created attachment 210318 [details]
xorg.conf generated by "sax2 -r -m 0=fglrx"

Created attachment 210321 [details]
Sax2.log generated by "sax2 -a"

Created attachment 210322 [details]
Sax2.log generated by "sax2 -r -m 0=fglrx"

all this sounds completely strange to me.

* I need such a system for testing since I can't reproduce any of
  the mentioned problems here. Stefan do you have such a system somewhere ?

* I need the output of sax2 -r -a which written to the _console_ window

thanks

*** Bug 368589 has been marked as a duplicate of this bug. ***

Unfortunately I don't have such a system, but it seems Christopher has one. As long as it is not his private laptop I think he will give you access to it.

Here's the console output of 'sax2 -r -a' on my ThinkPad T60p:

# sax2 -r -a
SaX: initializing please wait...
SaX: you current configuration will not be read in

SaX: no X-Server is running
SaX: will start own server if needed
ISaX: could not import file: /var/cache/sax/files/config at /usr/sbin/isax line 199.
ISaX: could not import file: /var/cache/sax/files/config at /usr/sbin/isax line 199.
ISaX: could not import file: /var/cache/sax/files/config at /usr/sbin/isax line 199.
ISaX: could not import file: /var/cache/sax/files/config at /usr/sbin/isax line 199.
ISaX: could not import file: /var/cache/sax/files/config at /usr/sbin/isax line 199.
ISaX: could not import file: /var/cache/sax/files/config at /usr/sbin/isax line 199.
ISaX: could not import file: /var/cache/sax/files/config at /usr/sbin/isax line 199.
SPP: prepare device [0] profile: Depth24
SPP: prepare device [0] profile: RadeonHD
SPP: calling device [0] profile script: RadeonHD
SPP: prepare device [1] profile: synaptics
SPP: calling device [1] profile script: synaptics
SPP: prepare device [3] profile: ibm-trackpoint
SPP: profile will add new section(s) -> moving: 3
SPP: including prepared profile(s)...

SaX: startup

SaX: creating config file please wait...
SaX: Automatic configuration is done


So there's nothing mentioned in the console output about device [5], which is the second TrackPoint entry in the written xorg.conf.
Also look at the names of the two devices:
Mouse[3] -> IBM;TPPS/2 Trackpoint
Mouse[5] -> TPPS/2 IBM Trackpoint

It's my private machine, but if you have time _now_ I could start openSUSE 11.0 and can give you access to the machine.

at the moment I'm working on #379027, could we do that next week ?

Yes, of course but I'm not in office on tuesday and wednesday.

found the bug and fixed it. The problem was the synaptics.pl profile
script. It does what has been fixed in sysp. According to this the same
check happens twice with wrong result :(