Bug#869785: libinput10: Can't set base velocity and acceleration to match Logitech Trackball M570
Hello, 2018-07-16 19:33 GMT+02:00 Alf : > Am 16.07.2018 um 16:26 schrieb Hector Oron: > >> >> Could you please test version 1.11.2-1 and report back? >> >> Best regards >> > No change so far, tested with libinput10 1.11.2-1 in Buster. > > Please tell me a way how I can set base speed and accelleration profile for > a Trackball. Mice work fine with default settings - but a TRACKBALL needs > different settings as explained above for Velocity and Acceleration: >> Base Speed ist too high, acceleration is too high. It does not consider >> that with just a thumb you cannot position as exactly as with a mouse. >> Movements over greater distance just needs a small kick to let the ball >> spin, which does not apply to mice. Can you please have a look to https://bugzilla.redhat.com/show_bug.cgi?id=1217881#c8 If that does not work, please open an issue upstream and let me know bug reference for tracking. https://bugs.freedesktop.org/enter_bug.cgi?component=Input%2Flibinput=xorg Regards > I had to revert to evdev again and current settings are: > > $ xinput --list-props 10 > > Device 'Logitech M570': > Device Enabled (136): 1 > Coordinate Transformation Matrix (138): 1.00, 0.00, > 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 > Device Accel Profile (264): 0 > Device Accel Constant Deceleration (265): 1.00 > Device Accel Adaptive Deceleration (266): 1.00 > Device Accel Velocity Scaling (267):10.00 > Device Product ID (259):1133, 4136 > Device Node (260): "/dev/input/event2" > Evdev Axis Inversion (268): 0, 0 > Evdev Axes Swap (270): 0 > Axis Labels (271): "Rel X" (146), "Rel Y" (147), "Rel Horiz > Wheel" (292), "Rel Vert Wheel" (263) > Button Labels (272):"Button Left" (139), "Button Middle" (140), > "Button Right" (141), "Button Wheel Up" (142), "Button Wheel Down" (143), > "Button Horiz Wheel Left" (144), "Button Horiz Wheel Right" (145), "Button > Side" (287), "Button Extra" (288), "Button Forward" (289), "Button Back" > (290), "Button Task" (291), "Button Unknown" (262), "Button Unknown" (262), > "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), > "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), > "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), > "Button Unknown" (262) > Evdev Scrolling Distance (273): 1, 1, 1 > Evdev Middle Button Emulation (274):0 > Evdev Middle Button Timeout (275): 50 > Evdev Middle Button Button (276): 2 > Evdev Third Button Emulation (277): 0 > Evdev Third Button Emulation Timeout (278): 1000 > Evdev Third Button Emulation Button (279): 3 > Evdev Third Button Emulation Threshold (280): 20 > Evdev Wheel Emulation (281):0 > Evdev Wheel Emulation Axes (282): 0, 0, 4, 5 > Evdev Wheel Emulation Inertia (283):10 > Evdev Wheel Emulation Timeout (284):200 > Evdev Wheel Emulation Button (285): 4 > Evdev Drag Lock Buttons (286): 0 -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.
Bug#903929: libglx-mesa0: please add Breaks: glx-diversions (<< 0.8.4~)
Package: libglx-mesa0 Version: 18.1.4-1 Severity: normal Hi, please add a Breaks: glx-diversions (<< 0.8.4~) to libglx-mesa0. The older versions did not handle libGLX_indirect.so.0 which could lead to the nvidia driver removing the libGLX_indirect.so.0 symlink. Thanks Andreas
problem with radeon since mesa > 18.0.5-1
After login on a x11 gnome gdm3 sesssion, display hangs, crash, becomes black, and occasionally freeze the computer. Which is an imac 27" 2011. But - i'm not sure it's a mesa bug, maybe a linux kernel bug triggered by the mesa update - i think it's appearing only on large displays like 2560x1440. - i don't know how to get logs from previous boots with journalctl I remember something about "cs ring radeon", etc.. Please help because it's a real bug ! Jérémy
Bug#869785: libinput10: Can't set base velocity and acceleration to match Logitech Trackball M570
Am 16.07.2018 um 16:26 schrieb Hector Oron: > > Could you please test version 1.11.2-1 and report back? > > Best regards > No change so far, tested with libinput10 1.11.2-1 in Buster. Please tell me a way how I can set base speed and accelleration profile for a Trackball. Mice work fine with default settings - but a TRACKBALL needs different settings as explained above for Velocity and Acceleration: > Base Speed ist too high, acceleration is too high. It does not consider > that with just a thumb you cannot position as exactly as with a mouse. > Movements over greater distance just needs a small kick to let the ball > spin, which does not apply to mice. I had to revert to evdev again and current settings are: $ xinput --list-props 10 Device 'Logitech M570': Device Enabled (136): 1 Coordinate Transformation Matrix (138): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (264): 0 Device Accel Constant Deceleration (265): 1.00 Device Accel Adaptive Deceleration (266): 1.00 Device Accel Velocity Scaling (267):10.00 Device Product ID (259):1133, 4136 Device Node (260): "/dev/input/event2" Evdev Axis Inversion (268): 0, 0 Evdev Axes Swap (270): 0 Axis Labels (271): "Rel X" (146), "Rel Y" (147), "Rel Horiz Wheel" (292), "Rel Vert Wheel" (263) Button Labels (272): "Button Left" (139), "Button Middle" (140), "Button Right" (141), "Button Wheel Up" (142), "Button Wheel Down" (143), "Button Horiz Wheel Left" (144), "Button Horiz Wheel Right" (145), "Button Side" (287), "Button Extra" (288), "Button Forward" (289), "Button Back" (290), "Button Task" (291), "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262) Evdev Scrolling Distance (273): 1, 1, 1 Evdev Middle Button Emulation (274):0 Evdev Middle Button Timeout (275): 50 Evdev Middle Button Button (276): 2 Evdev Third Button Emulation (277): 0 Evdev Third Button Emulation Timeout (278): 1000 Evdev Third Button Emulation Button (279): 3 Evdev Third Button Emulation Threshold (280): 20 Evdev Wheel Emulation (281):0 Evdev Wheel Emulation Axes (282): 0, 0, 4, 5 Evdev Wheel Emulation Inertia (283):10 Evdev Wheel Emulation Timeout (284):200 Evdev Wheel Emulation Button (285): 4 Evdev Drag Lock Buttons (286): 0
Bug#882997: marked as done (libinput-bin: Laptop keyboard no longer working after upgrading to 1.9.2-1)
Your message dated Mon, 16 Jul 2018 16:23:19 +0200 with message-id <20180716142319.GA30111@polynomio> and subject line Re: Bug#882997: libinput-bin: Laptop keyboard no longer working after upgrading to 1.9.2-1 has caused the Debian Bug report #882997, regarding libinput-bin: Laptop keyboard no longer working after upgrading to 1.9.2-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 882997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libinput-bin Version: 1.9.2-1 Severity: normal Dear Maintainer, When upgrading from 1.8.3-1 to 1.9.2-1, and after restarting X, my laptop's keyboard no longer worked properly on X. My usb keyboard was working properly, so was the keyboard when outside of X. I tried creating a xorg.conf with an explicit keyboard configuration but this did not help (I am no system guru though). Reverting libinput-bin to 1.8.3-1 fixed the issue. My laptop is an HP EliteBook Folio 9470m. I don't know what information you need if you want to investigate but I would be happy to provide them. Thank you very much. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (200, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libinput-bin depends on: iu libc6 2.25-2 ii libudev1 235-3 ii libwacom2 0.26-1 libinput-bin recommends no packages. libinput-bin suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- On Tue, Nov 28, 2017 at 08:57:12PM +0100, Michel Dänzer wrote: > On 2017-11-28 05:18 PM, Thomas Blanc wrote: > > Le 28/11/2017 à 16:47, Michel Dänzer a écrit : > >> On 2017-11-28 04:34 PM, Thomas Blanc wrote: > >>> Package: libinput-bin > >>> Version: 1.9.2-1 > >>> Severity: normal > >>> > >>> Dear Maintainer, > >>> > >>> When upgrading from 1.8.3-1 to 1.9.2-1, and after restarting X, my > >>> laptop's keyboard no longer worked properly on X. > >>> My usb keyboard was working properly, so was the keyboard when outside > >>> of X. > >>> > >>> I tried creating a xorg.conf with an explicit keyboard configuration but > >>> this did not help (I am no system guru though). > >>> > >>> Reverting libinput-bin to 1.8.3-1 fixed the issue. > >>> > >>> My laptop is an HP EliteBook Folio 9470m. I don't know what information > >>> you need if you want to investigate but I would be happy to provide > >>> them. > >> Assuming this only happens while the laptop is docked, it's a kernel bug > >> fixed by > >> > >> https://marc.info/?l=linux-kernel=151188228819123=2 > >> > >> > > This indeed only happens if the laptop is docked. I guess I'll patch my > > kernel. > > > > > > Thank you very much for the excellent support. > > I just happened to run and look into the same issue. :) > > In the meantime, it's been brought to my attention that there's already > a fix for this in 4.15-rc1: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9968e12a291e639dd51d1218b694d440b22a917f Closing bug, since it appears to be kernel related issue already fixed upstream. Regards > > > -- > Earthling Michel Dänzer | http://www.amd.com > Libre software enthusiast | Mesa and X developer -- signature.asc Description: PGP signature --- End Message ---
Bug#832594: libinput10: Thinkpad middle mouse not functioning properly, appears to be libinput10 issue
On Wed, Jul 27, 2016 at 05:47:08AM -0500, Karsten M. Self wrote: > Package: libinput10 > Version: 1.3.3-1 > Severity: normal > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? >* What outcome did you expect instead? > > *** End of the template - remove these template lines *** > > See also Bug #823147 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823147 > > As of a couple of months ago (system's been infrequently used), middle > mouse behavior on a Thinkpad T520i changed. When using the TrackPoint > mouse and buttons, the middle button behavior changed. It's not > possible to move the pointer while the middle button is depressed, > several programs and tools don't respond (though Xorg clipboard paste > appears to work). I believe this affects *both* console and Xorg > sessions. > > xev _doesn't_ report either BottonPress or ButtonRelease events for the > 2nd (middle) mouse button. Contrast (button 2 was pressed and released > several times in this capture): > > > ButtonPress event, serial 36, synthetic NO, window 0x561, > root 0xc4, subw 0x562, time 9625078, (36,51), root:(37,452), > state 0x0, button 1, same_screen YES > > EnterNotify event, serial 36, synthetic NO, window 0x561, > root 0xc4, subw 0x0, time 9625078, (36,51), root:(37,452), > mode NotifyGrab, detail NotifyInferior, same_screen YES, > focus YES, state 256 > > KeymapNotify event, serial 36, synthetic NO, window 0x0, > keys: 4294967236 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 >0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > > ButtonRelease event, serial 36, synthetic NO, window 0x561, > root 0xc4, subw 0x562, time 9625217, (36,51), root:(37,452), > state 0x100, button 1, same_screen YES > > LeaveNotify event, serial 36, synthetic NO, window 0x561, > root 0xc4, subw 0x0, time 9625217, (36,51), root:(37,452), > mode NotifyUngrab, detail NotifyInferior, same_screen YES, > focus YES, state 0 > > ButtonPress event, serial 36, synthetic NO, window 0x561, > root 0xc4, subw 0x562, time 9626514, (36,51), root:(37,452), > state 0x0, button 2, same_screen YES > > EnterNotify event, serial 36, synthetic NO, window 0x561, > root 0xc4, subw 0x0, time 9626514, (36,51), root:(37,452), > mode NotifyGrab, detail NotifyInferior, same_screen YES, > focus YES, state 512 > > KeymapNotify event, serial 36, synthetic NO, window 0x0, > keys: 4294967236 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 >0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > > ButtonRelease event, serial 36, synthetic NO, window 0x561, > root 0xc4, subw 0x562, time 9626514, (36,51), root:(37,452), > state 0x200, button 2, same_screen YES > > > > xinput shows: > > $ xinput list > ⎡ Virtual core pointerid=2[master pointer (3)] > ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer > (2)] > ⎜ ↳ TPPS/2 IBM TrackPoint id=11 [slave pointer > (2)] > ⎣ Virtual core keyboard id=3[master keyboard (2)] > ↳ Virtual core XTEST keyboard id=5[slave > keyboard (3)] > ↳ Power Buttonid=6[slave > keyboard (3)] > ↳ Video Bus id=7[slave > keyboard (3)] > ↳ Sleep Buttonid=8[slave > keyboard (3)] > ↳ Integrated Camera id=9[slave > keyboard (3)] > ↳ AT Translated Set 2 keyboardid=10 [slave > keyboard (3)] > ↳ ThinkPad Extra Buttons id=12 [slave > keyboard (3)] > > $ xinput get-button-map 11 > 1 2 3 4 5 6 7 > > $ xinput list-props 11 > Device 'TPPS/2 IBM TrackPoint': > Device Enabled (139): 1 > Coordinate Transformation Matrix (141): 1.00, 0.00, 0.00, > 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 > libinput Accel Speed (275): 0.00 > libinput Accel Speed Default (276): 0.00 > libinput Accel Profiles Available (277):1, 1 > libinput Accel Profile Enabled (278): 1, 0 > libinput Accel Profile Enabled Default (279): 1, 0 > libinput Natural Scrolling Enabled (280): 0 > libinput Natural Scrolling Enabled Default (281): 0 >
Bug#869785: libinput10: Can't set base velocity and acceleration to match Logitech Trackball M570
On Wed, Jul 26, 2017 at 02:18:45PM +0200, Alf wrote: > Package: libinput10 > Version: 1.6.3-1 > Severity: normal > >* What led up to the situation? > Sweitching from Jessie to Stretch makes the Trackball hardly usable. > Base Speed ist too high, acceleration is too high. It does not consider > that with just a thumb you cannot position as exactly as with a mouse. > Movements over greater distance just needs a small kick to let the ball > spin, which does not apply to mice. > >* What exactly did you do (or not do) that was effective (or > ineffective)? > Tried to adjust the parameters with "xinput" and the XFCE-settings > without success (settings are not respected). > Tried to cheat the DPI-values as given in /lib/udev/hwdb.d/70-mouse.hwdb > for MOUSE_DPI= without success. > Btw: the polling frequeny ist not 167Hz as hwdb suggests, but 125Hz as > reported by solaar: > Wireless Trackball M570 > Codename : M570 > Kind : mouse > Wireless PID : 1028 > Protocol : HID++ 1.0 > Polling rate : 8 ms (=125Hz) > Serial number: BD48472C > Firmware: 26.00.B0003 > Bootloader: 02.06 > Other: 00.01 >* What was the outcome of this action? > None of the known adjustments are respected by libinput - no changes. > > For now I had to revert to xserver-xorg-input-evdev which allows > detailled adjustments to operate the trackball a comfortable way. > To obtain a "clean Xorg.log" I also had to set libinput to ignore all > mice and keyboars. All works like a charm with evdev! > > Remak: xserver-xorg-input-evdev sets a Velocity Scaling (267): > 10.00, while libinput sets it fixed to 15.00. Could you please test version 1.11.2-1 and report back? Best regards > > -- System Information: > Debian Release: 9.1 > APT prefers stable > APT policy: (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) > Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), > LANGUAGE=de_DE.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages libinput10 depends on: > ii libc6 2.24-11+deb9u1 > ii libevdev2 1.5.6+dfsg-1 > ii libinput-bin 1.6.3-1 > ii libmtdev1 1.1.5-1+b1 > ii libudev1 232-25+deb9u1 > ii libwacom2 0.22-1+b1 > > libinput10 recommends no packages. > > libinput10 suggests no packages. > > -- no debconf information -- signature.asc Description: PGP signature
Bug#883036: disable-while-typing not working?
Hello Marco,
On Tue, Nov 28, 2017 at 08:30:10PM -0500, Marco Villegas wrote:
>
> Package: libinput10
> Version: 1.6.3-1
> Severity: normal
>
> Dear Mantainer,
>
> It seems like disable-while-typing[1] feature is not working correctly,
> even if it is enabled, it does not honor the timeouts in the code.
Could you please test version 1.11.2-1 in unstable and report back?
> This feature has been in there for a while, but I guess I notice it in
> Debian because libinput driver superseded synaptic Xorg driver in
> stretch. disable-while-typing was possible with synaptic with
> syndaemon/synclient, but libinput method seems to be more efficient[2].
>
> At first, I thought the feature was simply not enabled.
> GNOME seems to not have an UI for it until 3.24[3][4], but after
> installing xinput I see it is enabled.
>
> $ xinput | grep Touchpad
> ⎜ ↳ 1A586753:00 06CB:8323 Touchpad id=15 [slave
> pointer (2)]
> $ xinput list-props 15| grep Typing
> libinput Disable While Typing Enabled (309):1
> libinput Disable While Typing Enabled Default (310):1
>
> To test this:
> a. I start typing some sentence in a text editor,
> b. then use the touchpad,
> c. and the original application where I was typing is not in focus
> anymore.
>
> What I expected would be to the text editor to keep focus even if the
> touchpad is pressed when the time between the last key pressed and the
> touchpad is less than the established timeout, which in current
> packaged version 1.6.3 is 500ms[5].
>
> This setting sounds like a good candidate for a configuration option,
> e.g. then it can be set with xinput; but I see in upstream similar
> requests closed during issue triagging[6], but that is probably a new
> upstream request altogether.
>
> I may be not understanding the feature or stack correctly, so I would
> really appreciate if you can point me in the right direction.
If the issue persists, could you please ask in the upstream bug tracker and let
us know the bug reference to be able to track the issue?
Best regards
> 1:
> https://wayland.freedesktop.org/libinput/doc/latest/palm_detection.html#disable-while-typing
> 2:
> https://who-t.blogspot.pe/2016/08/libinput-and-disable-while-typing.html
> 3: https://bugzilla.gnome.org/show_bug.cgi?id=764852 4:
> https://git.gnome.org/browse/gsettings-desktop-schemas/commit/?id=4c5b1c1df399d6afaaccb237e299ccd1d5d29ddd
> 5:
> https://anonscm.debian.org/cgit/pkg-xorg/lib/libinput.git/tree/src/evdev-mt-touchpad.c?h=libinput-1.6.3-1#n35
> 6: https://bugs.freedesktop.org/show_bug.cgi?id=88353
>
> -- System Information:
> Debian Release: 9.1
> Architecture: amd64 (x86_64)
> Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
>
> $ dpkg-query --show -f='${binary:Package}\t${Version}\n' libinput*
> libc6 libudev1 libwacom2 libevdev2 libmtdev1 libc6:amd64
> 2.24-11+deb9u1 libevdev2:amd641.5.6+dfsg-1
> libinput-bin 1.6.3-1
> libinput10:amd64 1.6.3-1
> libmtdev1:amd64 1.1.5-1+b1
> libudev1:amd64232-25+deb9u1
> libwacom2:amd64 0.22-1+b1
> -- no debconf information
>
>
> Best,
>
> -Marco
--
signature.asc
Description: PGP signature
Bug#885032: upgrading libinput10 from 1.8.3-1 to 1.9.3-1 breaks ps2 keyboard
Hello, On Fri, Dec 22, 2017 at 08:28:56PM -0600, Brent S Elmer wrote: > Package: libinput10 > Version: 1.9.3-1 > Severity: normal > > When I upgrade libinput10 from 1.8.3-1 to 1.9.3-1 my ps2 keyboard no longer > works on my hp desktop. It appears to be caused by libinput10 and not > libinput-bin. When I revert libinput10 to 1.8.3-1 my ps2 keyboard works again > even if libinput-bin is still at 1.9.3-1. I see a similar bug report for > libinput-bin but it is for a laptop in a docking station. The problem is > definitely in libinput10 for me. USB keyboards will still work with > libinput10 > 1.9.3-1. Could you please retry with 1.11.2-1 version in unstable and report back? TIA Regards > > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.4.0-1-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages libinput10 depends on: > ii libc6 2.24-17 > ii libevdev2 1.5.7+dfsg-1 > ii libinput-bin 1.9.3-1 > ii libmtdev1 1.1.5-1+b1 > ii libudev1 235-3 > ii libwacom2 0.26-1 > > libinput10 recommends no packages. > > libinput10 suggests no packages. > > -- no debconf information -- signature.asc Description: PGP signature
Bug#891858: offset negative related ( i think )
Hello, On Sun, Mar 18, 2018 at 08:46:18PM +, Sergy Pylypchuk wrote: > Mar 18 21:07:33 xps9550 org.gnome.Shell.desktop[1124]: libinput error: client > bug: timer event18 gestures: offset negative (-111ms) > Mar 18 21:08:04 xps9550 org.gnome.Shell.desktop[1124]: libinput error: client > bug: timer event18 tap: offset negative (-455ms) > > But in my case it's correlates to very annoying behavior: > I move cursor with touchpad and after random period (20 - 120 sec) cursor > freezes for a moment, this error appears, then cursor jumps further. > > Laptop: Dell XPS 9550 > libinput10 version: 1.10.2-1 > Debian version: Buster Could you please test version 1.11.2-1 and report back? Thanks > Attached file if part of apt/history.log I do not see libinput in the upgraded list of packages. Regards signature.asc Description: PGP signature
Processed: notfixed 855465 in 1.11.2-1
Processing commands for cont...@bugs.debian.org:
> notfixed 855465 1.11.2-1
Bug #855465 {Done: Hector Oron } [libinput10] taps
intermittently missed on AlpsPS/2 ALPS GlidePoint touchpad
No longer marked as fixed in versions libinput/1.11.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
855465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#895756: libinput bug: invalid tap event TAP_EVENT_PALM in state TAP_STATE_TAPPED related
On Sun, Apr 15, 2018 at 10:30:27PM +0530, Jeffrin Thalakkottoor wrote: > Package: libinput10 > Version: 1.10.4-1 > > > hello , > > I found the following in syslog > > Apr 15 19:41:54 debian org.gnome.Shell.desktop[1356]: libinput error: > event1 - SynPS/2 Synaptics TouchPad: libinput bug: invalid tap event > TAP_EVENT_PALM in state TAP_STATE_TAPPED Could you please try with 1.11.2-1 version in unstable and report back with more information? Regards > -- > software engineer > rajagiri school of engineering and technology -- signature.asc Description: PGP signature
Bug#855465: marked as done (taps intermittently missed on AlpsPS/2 ALPS GlidePoint touchpad)
Your message dated Mon, 16 Jul 2018 15:56:30 +0200 with message-id <20180716135630.GA28246@polynomio> and subject line Re: Bug#855465: taps intermittently missed on AlpsPS/2 ALPS GlidePoint touchpad has caused the Debian Bug report #855465, regarding taps intermittently missed on AlpsPS/2 ALPS GlidePoint touchpad to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 855465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libinput10 Version: 1.6.0-1 On my AlpsPS/2 ALPS GlidePoint touchpad with tap-to-click enabled, taps sometimes register as clicks and sometimes don't. On running sudo libinput-debug-events --enable-tap --device /dev/input/event2 sometimes taps produce events like event2 POINTER_BUTTON +21.93sBTN_LEFT (272) pressed, seat count: 1 event2 POINTER_BUTTON +22.20sBTN_LEFT (272) released, seat count: 0 but sometimes they produce nothing at all and there is no clear pattern of when a tap succeeds. On the other hand with libinput built from the current git (6b561d45) things work as expected and sudo ./event-debug --enable-tap --device /dev/input/event2 consistently generates events for taps. Jyotirmoy Bhattacharya --- End Message --- --- Begin Message --- On Sat, Feb 18, 2017 at 11:44:45PM +0530, Jyotirmoy Bhattacharya wrote: > Package: libinput10 > Version: 1.6.0-1 > > On my AlpsPS/2 ALPS GlidePoint touchpad with tap-to-click enabled, taps > sometimes register as clicks and sometimes don't. > > On running > > sudo libinput-debug-events --enable-tap --device /dev/input/event2 > > sometimes taps produce events like > > event2 POINTER_BUTTON +21.93sBTN_LEFT (272) pressed, seat count: 1 > event2 POINTER_BUTTON +22.20sBTN_LEFT (272) released, seat count: 0 > > but sometimes they produce nothing at all and there is no clear pattern of > when a tap succeeds. > > On the other hand with libinput built from the current git (6b561d45) > things work as expected and > > sudo ./event-debug --enable-tap --device /dev/input/event2 > > consistently generates events for taps. > > Jyotirmoy Bhattacharya I am closing this bug, since there is no input to Andreas question and looks like it might be fixed in later version. Could you please reopen if the issue persists? signature.asc Description: PGP signature --- End Message ---
Processed: fixed 855465 in 1.11.2-1
Processing commands for cont...@bugs.debian.org: > fixed 855465 1.11.2-1 Bug #855465 [libinput10] taps intermittently missed on AlpsPS/2 ALPS GlidePoint touchpad Marked as fixed in versions libinput/1.11.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 855465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
libinput_1.11.2-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 16 Jul 2018 12:20:45 +0200 Source: libinput Binary: libinput10 libinput-bin libinput10-udeb libinput-dev libinput-tools Architecture: source Version: 1.11.2-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Héctor Orón Martínez Description: libinput-bin - input device management and event handling library - udev quirks libinput-dev - input device management and event handling library - development libinput-tools - input device management and event handling library - command line libinput10 - input device management and event handling library - shared libra libinput10-udeb - input device management and event handling library - shared libra (udeb) Changes: libinput (1.11.2-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: ec3560752b0049badbddc73e43a8d4f0501e679c 2633 libinput_1.11.2-1.dsc 79820c8d08ac19f60d336a74ac5afb1cc78f07d4 485600 libinput_1.11.2.orig.tar.xz 6cb90c86cc125fc75fbb040ef409a0de5c12bb6a 195 libinput_1.11.2.orig.tar.xz.asc ac2c894f9484ebaa6c76509c30444e8b1d9cfc87 8832 libinput_1.11.2-1.debian.tar.xz 6ae05afc22239fb88d016849070b5347093958a8 6316 libinput_1.11.2-1_source.buildinfo Checksums-Sha256: bcea668d3ee3e879ce91b217f654b389a39b944a7af6e1085075ab3dbc72b876 2633 libinput_1.11.2-1.dsc 6b36e1163d306c292ec8359b35aa65431cd29d0a5254923775e8019ff5018107 485600 libinput_1.11.2.orig.tar.xz cc921b6ead67303b38221f012da776bc4d27e8c11481febb1ddc9626a1396d67 195 libinput_1.11.2.orig.tar.xz.asc f02ada528127513502593532d9a570b68f4249420c66f2660efc44d0d8ef9e0d 8832 libinput_1.11.2-1.debian.tar.xz 9446fecbe25a13ff86cddaa7ccba17f2427aafe50848a825a64026330313db42 6316 libinput_1.11.2-1_source.buildinfo Files: 1cd6790332e8a196dc203ab449e758df 2633 libs optional libinput_1.11.2-1.dsc d179b5afbf414b34ce36ffe6ea8a401d 485600 libs optional libinput_1.11.2.orig.tar.xz 0c5b60ad1a5009ae914cd961c2d1db14 195 libs optional libinput_1.11.2.orig.tar.xz.asc 5ea63f0bdfccfd11aea37b47632fdb30 8832 libs optional libinput_1.11.2-1.debian.tar.xz d96c71ae1377959ee18fdc78615f998c 6316 libs optional libinput_1.11.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6Q8IiVReeMgqnedOryKDqnbirHsFAltMcb4ACgkQryKDqnbi rHsYkA//dHiwUzGvEsJHn/DchOJt9KNp85MdB1hErcmXDbjXB2Ij1w3ghUTAIQCi TwWknJvjt1atAcr3K4dTAZFD1GK53JlplZaNuwyHAtTlGfNuyPbUWjmefG8qD3s2 G4JvJZMSa9Fg9T6PPjwsgmrGq1++Qn3nmzNskUdtpmS9te10iA8xKD4+hDJ1ZDsp Ebl4eXasGlLSN7+fRYRloffBXquN3epkd7HQ0U0QIb8ry7GVYnzLxt0a8wIwia/f rMZ0HQqaxHkQio/AO5hU8pZsdmTPF+tahTNDQiJl+aYSPeIFdXt2X7lB2/H8Iqqn ljmvcAqei1rPA6/q3KOyQkED4LBA8PC1nIlnVO3hFEwf//LDPmAGXPGM9yfrEfwx HZJsT4Kgc3iSUJbAmZUH5Da0uXfG2s9gNthtKKC8kGKsaYGgpFtxfwJB3BegtN43 LDHMU+88a3hjisz+kYDExizAihOD/MxJm4YljtGERb7x6bW93jryEJXN78cfQ5BG +B8d4fZOsjqGOdj1psgioONjYC6WQC8CdGMxN9apd2MtvuwThFxZ7bYLTU/Ilgm2 hMxvq+SU6qb0R2h/yqHJutM3LEnDmxpT1kgmL4h7ho9ZY/7ojPC65Bvkb8Ei2JxY J/WnbrzTFL7Y6shqOpIcw+xjtLPvDohLo/3eiCoT+HyJqnQQ0pc= =9Dbo -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of libinput_1.11.2-1_source.changes
libinput_1.11.2-1_source.changes uploaded successfully to localhost along with the files: libinput_1.11.2-1.dsc libinput_1.11.2.orig.tar.xz libinput_1.11.2.orig.tar.xz.asc libinput_1.11.2-1.debian.tar.xz libinput_1.11.2-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
[Git][xorg-team/lib/libinput] Pushed new tag libinput-1.11.2-1
Héctor Orón Martínez pushed new tag libinput-1.11.2-1 at X Strike Force / lib / libinput -- View it on GitLab: https://salsa.debian.org/xorg-team/lib/libinput/tree/libinput-1.11.2-1 You're receiving this email because of your account on salsa.debian.org.
