On Thu, Mar 22, 2018 at 01:50:31PM +0800, Kai Hendry wrote:
> On Thu, 22 Mar 2018, at 12:15 PM, Peter Hutterer wrote:
> > right, sorry if that wasn't clear but changing the acceleration profile
> > won't change the drift you're seeing. Completely separate bug. What it does
> > change is the speed w
On Thu, 22 Mar 2018, at 12:15 PM, Peter Hutterer wrote:
> right, sorry if that wasn't clear but changing the acceleration profile
> won't change the drift you're seeing. Completely separate bug. What it does
> change is the speed which you labeled as "a bit too fast" in the first
> email.
Oh, so w
On Thu, Mar 22, 2018 at 12:04:12PM +0800, Kai Hendry wrote:
> On Thu, 22 Mar 2018, at 11:49 AM, Peter Hutterer wrote:
> > see the libinput documentation, it's a normalised value from -1.0 (slowest)
> > to
> > 1.0 (fastest) with 0 being the usually-default midpoint.
>
> [hendry@t480s ~]$ xinp
On Thu, 22 Mar 2018, at 11:49 AM, Peter Hutterer wrote:
> see the libinput documentation, it's a normalised value from -1.0 (slowest) to
> 1.0 (fastest) with 0 being the usually-default midpoint.
[hendry@t480s ~]$ xinput --set-prop 11 'libinput Accel Speed' -1
Has no impact to my drift probl
On Thu, Mar 22, 2018 at 11:36:55AM +0800, Kai Hendry wrote:
> Well I never installed gnome/kde to begin with.
>
> On Thu, 22 Mar 2018, at 11:24 AM, Peter Hutterer wrote:
> > don't get me wrong but - if you're capable of removing gnome/kde for
> > whatever reasons, you're capable of figuring out xi
Well I never installed gnome/kde to begin with.
On Thu, 22 Mar 2018, at 11:24 AM, Peter Hutterer wrote:
> don't get me wrong but - if you're capable of removing gnome/kde for
> whatever reasons, you're capable of figuring out xinput. there are plenty of
> guides on google, some of which are even a
On Thu, Mar 22, 2018 at 09:46:59AM +0800, Kai Hendry wrote:
> Thank you Peter for the pointers!
>
> On Wed, 21 Mar 2018, at 12:25 PM, Peter Hutterer wrote:
> > yeah, that's a built-in trackpoint feature that we don't have control over.
>
> drat
>
> > pieces with google. drift_time is probably th
Thank you Peter for the pointers!
On Wed, 21 Mar 2018, at 12:25 PM, Peter Hutterer wrote:
> yeah, that's a built-in trackpoint feature that we don't have control over.
drat
> pieces with google. drift_time is probably the key here, maybe resetafter or
> resync_time. At some point I had a pdf som
On Wed, Mar 21, 2018 at 11:14:28AM +0800, Kai Hendry wrote:
> On Tue, 20 Mar 2018, at 12:05 PM, Peter Hutterer wrote:
> > what exactly is drift in this context? it moves on its own to the edge of
> > the screen?
>
> It generally just moves diagonally south west for about a cm. Sometimes
> all the
On Tue, 20 Mar 2018, at 12:05 PM, Peter Hutterer wrote:
> what exactly is drift in this context? it moves on its own to the edge of
> the screen?
It generally just moves diagonally south west for about a cm. Sometimes all the
way to the bottom left. Initially I googled around and people said it w
On 20 March 2018 at 04:05, Peter Hutterer wrote:
> On Mon, Mar 19, 2018 at 04:28:20PM +0800, Kai Hendry wrote:
>> Hi there,
>>
>> I'm an Archlinux user who has a new T480s Thinkpad and unfortunately
>> the Trackpoint can (not always or reproducibly) "drift". I hope that
>> makes sense!
>
> what ex
On Mon, Mar 19, 2018 at 04:28:20PM +0800, Kai Hendry wrote:
> Hi there,
>
> I'm an Archlinux user who has a new T480s Thinkpad and unfortunately
> the Trackpoint can (not always or reproducibly) "drift". I hope that
> makes sense!
what exactly is drift in this context? it moves on its own to the
Hi there,
I'm an Archlinux user who has a new T480s Thinkpad and unfortunately
the Trackpoint can (not always or reproducibly) "drift". I hope that
makes sense!
https://bbs.archlinux.org/viewtopic.php?id=235400
The trouble is I can't seem to disable the Trackpoint pointer itself,
but still have
13 matches
Mail list logo