Re: 1) Lid Buttons 2) Stylus Input 3) Fingerprint Scanner

[Tobias Geerinckx-Rice <me@tobias.gr>]

[-- Attachment #1: Type: text/plain, Size: 3792 bytes --]

Raghav,

Mark H Weaver wrote:
> Raghav Gururajan <rvgn@disroot.org> writes:
>> What and how should I do to enable the following in my Thinkpad 
>> X200T (X200 Tablet)?

I just got an X230T so I'm very interested in getting the same 
things working.

>> 1) Buttons on the lid like screen rotation, lock screen etc.
>
> Those buttons act like special keys on your keyboard.  The 
> following web
> page lists their scancodes, and gives some advice on how to set 
> things
> up so that the buttons behave as expected:
>
>   https://www.thinkwiki.org/wiki/Tablet_Hardware_Buttons
>
> The page recommends using xbindkeys, which is provided by the 
> Guix
> "xbindkeys" package, but depending on which desktop environment 
> you use,
> there might be a more straightforward way to arrange for a 
> script to be
> run when you press a key.

Exactly.  I used ‘xev’ (available in Guix) to get the keycode for 
what I presume is the screen rotation button(? there are two, the 
pictograms are pretty vague, but only one generates classic key 
codes) and added

  bindsym XF86TaskPane    exec --no-startup-id 
  /home/nckx/.config/i3/rotate-screen.sh

to my ~/.config/i3/config.  rotate-screen.sh is a simple (well…) 
shell script that uses xrandr to query the current screen 
orientation and cycle to the next one (I use left/right/normal, 
never inverted):

  xrandr --output LVDS-foo --rotate normal|left|right|...

The only problem is that pressing the button once produces a 
deluge of press events.  Luckily the number is usually constant 
(so it's not just a ‘repeat’ without a ‘delay’) making the end 
result predictable.  In practice it means I'm cycling backwards 
through the orientations.

Good enough for now.  It's not like I can actually use i3 properly 
in tablet mode anyway.  Will this finally push me to GNOME?

Haha no.

>> 2) Input using stylus pen.
>
> The touch screen is apparently a Wacom device.  From GNOME, you 
> might be
> able to easily set it up from the "Wacom" section of GNOME 
> settings.  I
> don't know about other desktop environments off-hand.
>
> I will note, however, that the "xsetwacom" program, which 
> apparently can
> be used to enable the Wacom device within an Xorg session, 
> should be
> provided by our "xf86-input-wacom" package.  You might find 
> other useful
> information on 
> <https://wiki.archlinux.org/index.php/Wacom_tablet>,
> although note that "permanent configuration" will be much 
> different on a
> Guix system than on Arch.
>
> To set it up permanently, it *might* be sufficient to add 
> something like
> the following to your OS configuration, merging it with your 
> existing
> 'services' field if needed:
>
>     (services (append (list ;; other services go here
>                             (set-xorg-configuration
>                              (xorg-configuration
>                               (modules (cons xf86-input-wacom
>                                              %default-xorg-modules)))))
>                       %desktop-services))

I'm sure this works fine, but at least the X230T's (multi-)touch 
screen is fully supported by libinput as well:

  Section \"InputClass\"
   Identifier \"Touchscreens\"
   MatchIsTouchscreen \"on\"
   MatchDevicePath \"/dev/input/event*\"
   Driver \"libinput\"
  EndSection

So I don't think the Wacom driver (which I don't much like anyway) 
is mandatory.

>> 3) Fringerprint scanner for authentication.

I'm still stuck on ‘no value specified for service of type 
'fprintd'’ (see elsewhere in this thread) but admittedly I gave it 
all of 5 seconds before moving on to more important stuff.  It's a 
fun gimmick though :-)

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]