<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> <span class="fn">Peter Hutterer</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - Touchpad tap doesn't work on DELL XPS 15 9550"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96925">bug 96925</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>NOTABUG
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - Touchpad tap doesn't work on DELL XPS 15 9550"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96925#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - Touchpad tap doesn't work on DELL XPS 15 9550"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96925">bug 96925</a>
from <span class="vcard"><a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> <span class="fn">Peter Hutterer</span></a>
</span></b>
<pre>(In reply to Russell Stuart from <a href="show_bug.cgi?id=96925#c9">comment #9</a>)
<span class="quote">> Which brings me to another comment in that Debian bug:
>
> > Setting 291 and 294 looked enticing but I could not figure out the syntax xinput wanted.</span >
xinput is a developer tool. it merely sets key/value pairs, it has no knowledge
on what it actually set. it's like gsettings in that regard. the keys are the
device name and property name, the value is what the property requires, and
that's driver specific. xinput merely takes whatever you give it and passes it
on, it has no notion of what it's doing otherwise. it shouldn't be used for
permanent device configuration anyway, we have said that for years.
<span class="quote">> Translation: the xinput doco sucks in some places. I remembered when I
> tried to do this today:
>
> $ xinput set-prop "DLL06E4:01 06CB:7A13 Touchpad" "libinput Accel Speed"
> 1.5
> X Error of failed request: BadValue (integer parameter out of range for
> operation)</span >
BadValue is an X error code and similar to the errno EINVAL. the error message
is printed by Xlib. And float properties didn't appear until 20 years after
BadValue was implemented first... the properties API has not a lot of options
for error messages, BadValue, BadMatch and BadAccess are the only ones iirc.
Anyway, closing this bug as NOTABUG, cause was that tapping was enabled on the
wrong device and hence it didn't take effect. The wrong device because the i2c
driver exposes two device nodes (one mute) so it's easy to make that mistake.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>