Bug 105896

run xinput watch-props 'TPPS/2 IBM TrackPoint' please while plugging in the external mouse. Does the property change then?

Probabl not a libinput bug but either xf86-input-libinput or possibly GNOME overwriting the configuration. Please try xf86-input-libinput 0.27, it has a fix for erroneous property writes and that may just be the issue.

I'll also need your Xorg.log, just in case there's something interesting in there.

Dear Peter, 

 I am out of my office at the moment and won't be able to test until Wednesday.
However, I am already using xf86-input-libinput 0.27 and I am a KDE user, not a gnome user.  I typically dock the machine when it is sleeping and resume afterwards, but I can certainly have a look at what happens when I plug in the 
mouse by itself. 

Will get back to you in a couple of days.

Best
 J

Dear Peter, 

 I confirm that the change happens on docking the laptop. 

xinput watch-props 12
Device 'TPPS/2 IBM TrackPoint':
        Device Enabled (143):   1
        Coordinate Transformation Matrix (145): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
        libinput Natural Scrolling Enabled (311):       0
        libinput Natural Scrolling Enabled Default (312):       0
        libinput Scroll Methods Available (313):        0, 0, 1
        libinput Scroll Method Enabled (314):   0, 0, 1
        libinput Scroll Method Enabled Default (315):   0, 0, 1
        libinput Button Scrolling Button (316): 2
        libinput Button Scrolling Button Default (317): 2
        libinput Middle Emulation Enabled (318):        0
        libinput Middle Emulation Enabled Default (319):        0
        libinput Accel Speed (320):     1.000000
        libinput Accel Speed Default (321):     0.000000
        libinput Accel Profiles Available (322):        1, 1
        libinput Accel Profile Enabled (323):   0, 1
        libinput Accel Profile Enabled Default (324):   1, 0
        libinput Send Events Modes Available (327):     1, 0
        libinput Send Events Mode Enabled (328):        0, 0
        libinput Send Events Mode Enabled Default (329):        0, 0
        Device Node (264):      "/dev/input/event16"
        Device Product ID (263):        2, 10
        libinput Drag Lock Buttons (330):       <no items>
        libinput Horizontal Scroll Enabled (331):       1
----- Docking happens here ----
Property 'libinput Natural Scrolling Enabled' changed.
        libinput Natural Scrolling Enabled (311):       0
Property 'libinput Natural Scrolling Enabled' changed.
        libinput Natural Scrolling Enabled (311):       0
Property 'libinput Accel Profile Enabled' changed.
        libinput Accel Profile Enabled (323):   1, 0
Property 'libinput Accel Profile Enabled' changed.
        libinput Accel Profile Enabled (323):   1, 0

xorg.log is attached as it is too long to fit here.

Created attachment 138769 [details]
xorg.log

On Thursday, April 5, 2018 10:04:49 PM EDT you wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=105896
> 
> Peter Hutterer <peter.hutterer@who-t.net> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
> CC|                            |peter.hutterer@who-t.net Status|NEW        
>                 |NEEDINFO
> 
> --- Comment #1 from Peter Hutterer <peter.hutterer@who-t.net> ---
> run xinput watch-props 'TPPS/2 IBM TrackPoint' please while plugging in the
> external mouse. Does the property change then?
> 
> Probabl not a libinput bug but either xf86-input-libinput or possibly GNOME
> overwriting the configuration. Please try xf86-input-libinput 0.27, it has a
> fix for erroneous property writes and that may just be the issue.
> 
> I'll also need your Xorg.log, just in case there's something interesting in
> there.
> 
> --
> You are receiving this mail because:
> You reported the bug.

Some updates: I tried connecting the mouse directly to the laptop to clean up 
the xorg log.  Unfortunately it died on me. Plugging in the usb connector now 
sends the kernel to panic.  

I will try to test with another external device.

In the meantime please let me know if the logs that I gave are sufficient or if 
you need more information

Best
 J

This line here indicates that it is the property that changed:

  Property 'libinput Accel Profile Enabled' changed.
          libinput Accel Profile Enabled (323):   1, 0

which means it's not a libinput bug but either a bug in the xf86-input-libinput driver or a bug in the desktop environment. I don't know if KDE touches that property tbh. To narrow this down, install xterm and run a plain X session without KDE, just run xinit (note: you won't have a window manager running, keep it that way please). Once you see the xterm, run the same watch-props command, plug the mouse in and check the output. Same behaviour?

If so, this is a xf86-input-libinput driver bug, otherwise it's a KDE issue. Or whatever else could possibly touch that property.

That X server wills shut down once the xterm instance exits.

Created attachment 138771 [details]
email garbage

I was trying to do that and then the mouse died on me. Will try with another mouse as soon as I get it

On April 11, 2018 5:37:09 PM EDT, bugzilla-daemon@freedesktop.org wrote:
>https://bugs.freedesktop.org/show_bug.cgi?id=105896
>
>Peter Hutterer <peter.hutterer@who-t.net> changed:
>
>           What    |Removed                     |Added
>----------------------------------------------------------------------------
>            Product|Wayland                     |xorg
>         Assignee|wayland-bugs@lists.freedesk |peter.hutterer@who-t.net
>                   |top.org                     |
>         QA Contact|                            |xorg-team@lists.x.org
>          Component|libinput                    |Input/libinput
>
>--- Comment #6 from Peter Hutterer <peter.hutterer@who-t.net> ---
>This line here indicates that it is the property that changed:
>
>  Property 'libinput Accel Profile Enabled' changed.
>          libinput Accel Profile Enabled (323):   1, 0
>
>which means it's not a libinput bug but either a bug in the
>xf86-input-libinput
>driver or a bug in the desktop environment. I don't know if KDE touches
>that
>property tbh. To narrow this down, install xterm and run a plain X
>session
>without KDE, just run xinit (note: you won't have a window manager
>running,
>keep it that way please). Once you see the xterm, run the same
>watch-props
>command, plug the mouse in and check the output. Same behaviour?
>
>If so, this is a xf86-input-libinput driver bug, otherwise it's a KDE
>issue. Or
>whatever else could possibly touch that property.
>
>That X server wills shut down once the xterm instance exits.
>
>-- 
>You are receiving this mail because:
>You reported the bug.

please trim your emails, this bug is getting noise because of all the garbage added by the email replies.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/issues/12.