Please see https://wayland.freedesktop.org/libinput/doc/latest/faqs.html
#what-causes-the-timer-offset-negative-warning, this is almost never a
libinput bug.
fwiw, libinput has moved to gitlab, any future issues should be filed at
https://gitlab.freedesktop.org/libinput/libinput
--
You received
(In reply to main.haarp from comment #17)
> Configurable acceleration on the input device driver level would solve this
> nicely. You could have fast scrolling when you need it, and even still
> retain slow but precise scrolling when you don't.
I feel this is solving the wrong problem. If the docu
(In reply to main.haarp from comment #21)
> If acceleration depends on the toolkit/application, I fear it'll remain a
> toy for select applications on modern distros only.
it's a thin line between adding these features for legacy applications
and screwing things up for new applications that could
Adam: I'm really hesitant to put it into libinput because I'm not sure
the problem scope is well understood (at least by me) and what the
actual point of it is. So far it's been a "would be nice" but - at least
these days :) - we require a bit more information about use-cases and
precise behaviours
i guess the only update is a WONTFIX, given that this has been
languishing for 6 years now. input stuff like this is moving to libinput
anyway, and I don't think I'll implement mouse wheel acceleration there
either.
--
You received this bug notification because you are a member of Desktop
Package
*** Bug 98998 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/313514
Title:
MASTER: evdev driver ignores keycodes > 255
Status in X
"The Trackpad Hotkey continues to be recognized however the same
'Trackpad deactivated' graphic pops-up every time Fn+F5 hotkey is
depressed. This is somehow not linked to the Enable/Disable Trackpad
functionality in Gnome Control Center/Settings (i.e. does nothing)."
It's most likely some issue w
This is a mass change of bugs. Bugs assigned to me that haven't been
updated in the last 3 years are closed as WONTFIX, because, well, let's
at least be honest about it.
Please do not re-open unless you have a really good reason to do so
(e.g. you're fixing it yourself). If it hasn't been fixed in
The VertResolution/HorizResolution options shouldn't be needed on newer
touchpads anyway if the kernel provides it. So you can ignore those.
and yes, this is the same bug.
the problem is caused by the server needing to support true absolute
devices in relative mode (e.g. graphics tablets). If you
The VertResolution/HorizResolution options shouldn't be needed on newer
touchpads anyway if the kernel provides it. So you can ignore those.
and yes, this is the same bug.
the problem is caused by the server needing to support true absolute
devices in relative mode (e.g. graphics tablets). If you
closing this again, was pushed as outlined in comment #27 and that
behaviour has been unchanged for 6 years now. if you still want the
extra finger counting please open a new bug but I should point out that
it's unlikely to be implement for synaptics. libinput has that feature
already, probably bet
This ended up being a GTK3 bug, not an xorg bug, see
https://bugzilla.redhat.com/show_bug.cgi?id=1245247. Closing again
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/925785
Title:
commit 6f28388187cffae9e5bc9bfc9425acff4f478b59
Author: Peter Hutterer
Date: Sat Feb 11 01:29:26 2012 +1000
dix: reset last.scroll when resetting the valuator (#45611)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server
you're right, it had a regression, it's still not fixed. looks like the
only fix doable is to drop abs events from the driver and make the
touchpad relative only. This requires re-adjusting the pointer
acceleration though.
--
You received this bug notification because you are a member of Desktop
you're right, it had a regression, it's still not fixed. looks like the
only fix doable is to drop abs events from the driver and make the
touchpad relative only. This requires re-adjusting the pointer
acceleration though.
--
You received this bug notification because you are a member of Desktop
Status update:
The kernel patches are now in Dmitry's branch and queued for 4.0
https://git.kernel.org/cgit/linux/kernel/git/dtor/input.git/commit/?h=for-linus&id=6067fe5e0bf29f525561c8281d01011cfc9ebbd4
There will _not_ be a patch to the synaptics driver (or libinput). The kernel
patches re-rout
more than 2 years in NEEDINFO, closing
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/416516
Title:
Touchpad isn't sensitive enough on MacBook 5,2
Status in Mact
the hwdb doesn't have effect on the synaptics driver bits, but if the
files aren't installed correctly that's a fedora bug, please file it
there and assign it to me.
Note you also need to udevadm control --reload-rules to make the hwdb
work (and drop the matching 70-touchpad.rules file in place to
synaptics fixed in master:
http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/commit/?id=064445364b4775b25ba49c2250b22b169f291147
libinput fixed in master (and 0.9.0):
http://cgit.freedesktop.org/wayland/libinput/commit/?id=428614bb242a85a0b46f1a60bc822dbb47327b31
--
You received this
Kernel patches proposed:
http://www.spinics.net/lists/linux-input/msg36219.html
udev hwdb addition to mark devices like this:
http://cgit.freedesktop.org/systemd/systemd/commit/hwdb/70-touchpad.hwdb?id=001a247324b44c0e0b8fdba41a6fc66e7465b8b6
libinput patches proposed:
http://lists.freedeskto
*** This bug has been marked as a duplicate of bug 70780 ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1383157
Title:
[Lenovo T440p] New Trackpad: middle but
Fixes for that are in synaptics 1.8 and 1.7.6. It was caused by missing
SYN_DROPPED handling.
You'll need libevdev 1.2 or later, iirc to get rid of the bug in
synaptics 1.8.
Otherwise, the commit on the 1.7 branch was:
http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/commit/?h=synapt
Fixes for that are in synaptics 1.8 and 1.7.6. It was caused by missing
SYN_DROPPED handling.
You'll need libevdev 1.2 or later, iirc to get rid of the bug in
synaptics 1.8.
Otherwise, the commit on the 1.7 branch was:
http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/commit/?h=synapt
The device wasn't supported by the kernel before the patch, so it was
running in mouse emulation mode. That is usually a firmware feature, we
often see this on new touchpads before we add support and switch them to
raw mode. To userspace (i.e. X.Org) it looked like a mouse device, the
gesture suppo
Christopher: please don't request that users file bugs for xf86-input-
evdev when it's a kernel bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/998546
Title:
0408:3003 [Packar
yeah, it's an issue that affects any clickpad, and it's caused by
synaptics still primarily handling touchpads as single-touch devices. a
few additions allowed for some MT stuff, but the driver needs
significant changes to be true multitouch capable - and that's out of
scope.
Changing bug title to
probably not going to happen. synaptics needs a rewrite to track the
fingers separately to tell that one finger is in the button area. This
isn't really feasable, we're concentrating on libinput atm that will
allow us to do that.
--
You received this bug notification because you are a member of D
wayland uses 32 bit keycodes, so it doesn't have the same limitation.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/313514
Title:
MASTER: evdev driver ignores keycodes > 255
Sta
Created attachment 99376
0001-mi-don-t-process-events-from-disabled-devices-77884.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1208473
Title:
Xorg crashed with SIGABRT in
commit 98924719d524bf87cdf301063cd744d1271c33ff
Author: Peter Hutterer
Date: Wed Apr 2 13:55:10 2014 +1000
Revert "xkb: ProcesssPointerEvent must work on the VCP if it gets
the VCP"
--
You received this bug notification because you are a member of Desktop
Packages, which is sub
http://patchwork.freedesktop.org/patch/23451/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1245662
Title:
Sticky Keys not released after mouse action.
Status in X.Org X server:
whoah, that one flew under the radar. sorry for the silence. it's been
two years, I'm gonna close this now as fixed (latest master has a bunch
of fixes here), please open a new bug if this persists.
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
we currently have no plans of fixing this, sorry.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/795920
Title:
Can't disable touchpad
Status in xf86-input-synapt
Please see the follow-up post here:
http://lists.x.org/archives/xorg-devel/2013-December/039346.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1184159
Title:
[saucy] scrollin
Please see the follow-up post here:
http://lists.x.org/archives/xorg-devel/2013-December/039346.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1240957
Title:
Scrolling behavi
Please see the follow-up post here:
http://lists.x.org/archives/xorg-devel/2013-December/039346.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1200829
Title:
Regression: Enab
Please see the follow-up post here:
http://lists.x.org/archives/xorg-devel/2013-December/039346.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1171342
Title:
mouse scroll whe
Do you have a test case for this? I knocked up a simple one with two XI2
clients, one creating a window with enter/leave on a window, one with
enter/leave on the button grab on the root window. Neither client gets
an event and a printf in the server shows nothing is written onto the
wire either (on
Do you have a test case for this? I knocked up a simple one with two XI2
clients, one creating a window with enter/leave on a window, one with
enter/leave on the button grab on the root window. Neither client gets
an event and a printf in the server shows nothing is written onto the
wire either (on
Do you have a test case for this? I knocked up a simple one with two XI2
clients, one creating a window with enter/leave on a window, one with
enter/leave on the button grab on the root window. Neither client gets
an event and a printf in the server shows nothing is written onto the
wire either (on
Do you have a test case for this? I knocked up a simple one with two XI2
clients, one creating a window with enter/leave on a window, one with
enter/leave on the button grab on the root window. Neither client gets
an event and a printf in the server shows nothing is written onto the
wire either (on
Thanks for testing. I'm going to close this one as fixed since we
definitely fixed quite a few bugs in this patch set. If there's
something left please file a new bug so we can narrow down the new (old?
:) issues.
--
You received this bug notification because you are a member of Desktop
Packages,
Thanks for testing. I'm going to close this one as fixed since we
definitely fixed quite a few bugs in this patch set. If there's
something left please file a new bug so we can narrow down the new (old?
:) issues.
--
You received this bug notification because you are a member of Desktop
Packages,
(In reply to comment #101)
> Nope, and I noticed a BUG on !pGrab in FreeGrab, I'll try it a bit more on
> monday.
merged as 0e3be0b25fcfeff386bad132526352c2e45f1932 yesterday.
as for the rest, I really need something that's reproducible.
--
You received this bug notification because you are a
(In reply to comment #101)
> Nope, and I noticed a BUG on !pGrab in FreeGrab, I'll try it a bit more on
> monday.
merged as 0e3be0b25fcfeff386bad132526352c2e45f1932 yesterday.
as for the rest, I really need something that's reproducible.
--
You received this bug notification because you are a
fwiw, the latest branch got merged into master. It's still buggy but an
improvement over the previous state.
commit c76a1b343d6a56aa9529e87f0eda8d61355d562b
Merge: 891123c 9a5ad65
Author: Keith Packard
Date: Thu May 23 19:58:36 2013 -0600
Merge remote-tracking branch 'whot/touch-grab-race-
fwiw, the latest branch got merged into master. It's still buggy but an
improvement over the previous state.
commit c76a1b343d6a56aa9529e87f0eda8d61355d562b
Merge: 891123c 9a5ad65
Author: Keith Packard
Date: Thu May 23 19:58:36 2013 -0600
Merge remote-tracking branch 'whot/touch-grab-race-
sorry guys, please take the compilation errors to the list. This bug is
confusing enough with >90 comments and I'd like to keep off-topic stuff
to a minimum.
pushed a new version of the branch after fixing a cursor refcounting
issue that crashed my server when dragging and email in thunderbird. ne
(In reply to comment #85)
> Is make check failing for anyone else with v3?
caused by a patch merged into master (and thus picked up on v3), fix is here:
http://patchwork.freedesktop.org/patch/13687/
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
sorry guys, please take the compilation errors to the list. This bug is
confusing enough with >90 comments and I'd like to keep off-topic stuff
to a minimum.
pushed a new version of the branch after fixing a cursor refcounting
issue that crashed my server when dragging and email in thunderbird. ne
(In reply to comment #85)
> Is make check failing for anyone else with v3?
caused by a patch merged into master (and thus picked up on v3), fix is here:
http://patchwork.freedesktop.org/patch/13687/
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
oh, right. sorry, I forgot to mention this - it is indeed a ABI break so
you have to recompile the drivers (or add the now-unused field back in).
Maarten, this could also be the reason for your bug?
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
Pushed the branch with a fix to keep the ABI, please test
de12ce91d8e44ab9398e730b457e5abc8d1acbe6
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1068994
Title:
button1 gets stuck
right, that was the one and it hasn't been reverted, it just got
integrated into upstream 1.13.1 so we don't need the patch anymore. back
to the drawing board.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics i
There are suggestions that http://lists.x.org/archives/xorg-
devel/2012-October/034149.html helps with this issue, but unconfirmed so
far.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bug
Pushed the branch with a fix to keep the ABI, please test
de12ce91d8e44ab9398e730b457e5abc8d1acbe6
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1015183
Title:
Inconsistent mouse
oh, right. sorry, I forgot to mention this - it is indeed a ABI break so
you have to recompile the drivers (or add the now-unused field back in).
Maarten, this could also be the reason for your bug?
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
daniel - xev behaves normally for me in the last branch. is it still
misbehaving for you?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1015183
Title:
Inconsistent mouse events f
> ==3663== 16,384 bytes in 4 blocks are still reachable in loss record 245 of
> 246
> ==3663==at 0x482D4B8: calloc (vg_replace_malloc.c:593)
> ==3663==by 0x216F23: WriteToClient (io.c:1017)
> ==3663==by 0x142667: WriteEventsToClient (events.c:5982)
> ==3663==by 0x142747: TryClientEv
tried to bisect this, but I can't see any difference in the xev output
before or after that commit. Tested several revisions after (and
3e15158985) and xev works as expected.
fwiw, my test box here is Ubuntu 12.10 with the server branch above,
rest as-is. mouse used is a trackpoint, which for all
> ==3663== 16,384 bytes in 4 blocks are still reachable in loss record 245 of
> 246
> ==3663==at 0x482D4B8: calloc (vg_replace_malloc.c:593)
> ==3663==by 0x216F23: WriteToClient (io.c:1017)
> ==3663==by 0x142667: WriteEventsToClient (events.c:5982)
> ==3663==by 0x142747: TryClientEv
tried to bisect this, but I can't see any difference in the xev output
before or after that commit. Tested several revisions after (and
3e15158985) and xev works as expected.
fwiw, my test box here is Ubuntu 12.10 with the server branch above,
rest as-is. mouse used is a trackpoint, which for all
daniel - xev behaves normally for me in the last branch. is it still
misbehaving for you?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1068994
Title:
button1 gets stuck after a
the libreoffice hint helped a lot tracking this down. New branch posted (top
commit b8a2de82e36dd922843618f15703113dd556b164 dix: fix cursor refcounting
). Please give this a test. looks like my test box here is happy and valgrind
doesn't see any leaks (yet)
--
You received this bug notificatio
the libreoffice hint helped a lot tracking this down. New branch posted (top
commit b8a2de82e36dd922843618f15703113dd556b164 dix: fix cursor refcounting
). Please give this a test. looks like my test box here is happy and valgrind
doesn't see any leaks (yet)
--
You received this bug notificatio
Till, can you run this under valgrind please to make sure I didn't
introduce any memory leaks?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1068994
Title:
button1 gets stuck aft
XI2 already sends 32-bit keycodes, it's the XKB layer and thus the
ability to interpret this that doesn't handle them.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/313514
Title:
Till, can you run this under valgrind please to make sure I didn't
introduce any memory leaks?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1015183
Title:
Inconsistent mouse eve
Please have a test of this branch here:
http://cgit.freedesktop.org/~whot/xserver/log/?h=touch-grab-race-condition-56578-v2
I'm not 100% sure yet if there's a memleak introduced - haven't done the
required checks yet. but it fixes the crasher caused by the invalid
memory dereference.
--
You rece
ok, I'll be honest. this is a giant mess where we potentially access
dangling pointers and sorting this out is nasty. my attempts to do so
today have failed badly. fix will come, but not too soon I'm afraid
--
You received this bug notification because you are a member of Desktop
Packages, which
ok, thanks to Maarten's debugging we've found the issue. listener->grab
is not copied but rather referenced, leaving the grab stale once it was
deleted. Reproducible test case is simply:
XGrabButton()
pointer-emulating touch down
XUngrabButton()
trigger touch update/end
This doesn't necessarily c
Please have a test of this branch here:
http://cgit.freedesktop.org/~whot/xserver/log/?h=touch-grab-race-condition-56578-v2
I'm not 100% sure yet if there's a memleak introduced - haven't done the
required checks yet. but it fixes the crasher caused by the invalid
memory dereference.
--
You rece
ok, I'll be honest. this is a giant mess where we potentially access
dangling pointers and sorting this out is nasty. my attempts to do so
today have failed badly. fix will come, but not too soon I'm afraid
--
You received this bug notification because you are a member of Desktop
Packages, which
commit 61a99aff9d33728a0b67920254d2d4d79f80cf39
Author: Peter Hutterer
Date: Fri Jan 11 14:22:07 2013 +1000
dix: pre-scale relative events from abs devices to desktop ratio
(#31636)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
commit 61a99aff9d33728a0b67920254d2d4d79f80cf39
Author: Peter Hutterer
Date: Fri Jan 11 14:22:07 2013 +1000
dix: pre-scale relative events from abs devices to desktop ratio
(#31636)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
(In reply to comment #3)
> The patch we added to Ubuntu for that bug is attached. It was confirmed to
> fix the issue by that user, but would be helpful if others could test it as
> well.
it doesn't fix the issue, it merely papers over the crash. would be
useful to find a reproducible test case f
http://patchwork.freedesktop.org/patch/12839/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/621432
Title:
Touchpad speed asymetrical (horizontal faster than vert
Claiming this is closed since I haven't seen this in a while. Please
reopen if it's still here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/566375
Title:
log spam when detachin
Pad Resolution is currently readonly on purpose - your pad is unlikely
to change resolutions at runtime. I admit it would make testing it
easier but right now you need to add an xorg.conf(.d) option for it.
synclient appears to be lacking it altogether, that should be fixed
(patches appreciated)
http://patchwork.freedesktop.org/patch/12839/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/726832
Title:
Touchpad speed scales with multimonitor size per axis
Hard to read the backtrace without symbols, but please try to find a
reproducible test-case. The number of fingers on the touchpad at suspend
time vs at resume time is almost certainly the trigger for this, but I
haven't found a reliable trigger yet.
--
You received this bug notification because
syndaemon currently uses a synaptics-only property to disable the
touchpad. this property disables the touchpad in-driver. a similar
property exists on all devices but that would disable the device
completely, potentially interfering with the desktop environment. this
would require testing to ensur
commit e7cd5cce740e653000fb1192b600268dcf77dde2
Author: Peter Hutterer
Date: Thu Oct 18 15:11:31 2012 +1000
dix: fix zaphod screen scrossing (#54654)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https
commit 5b7384a3154a95a805b040e1910e276b52aada96
Author: Alexey Ten (Lynn)
Date: Tue Oct 23 12:32:31 2012 +0400
Apply partial matches for option (#25873)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https:
Pad Resolution is currently readonly on purpose - your pad is unlikely
to change resolutions at runtime. I admit it would make testing it
easier but right now you need to add an xorg.conf(.d) option for it.
synclient appears to be lacking it altogether, that should be fixed
(patches appreciated)
Alexey, please sign-off your patch. ACK otherwise, I'll merge it as soon
as I have your Signed-off-by.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1070214
Title:
misc:typo rule
86 matches
Mail list logo
